Issue 93 in innotop: MarriaDB 10.0 InnoDB Row Ops Error

[inn...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 93 by deno...@gmail.com: MarriaDB 10.0 InnoDB Row Ops Error
http://code.google.com/p/innotop/issues/detail?id=93

What steps will reproduce the problem?
1. Connect to database MariaDB 10.0 (./innotop -h host -u user -p'password')
2. Try to view 'InnoDB Row Ops' (Shift+R)
3. Receive error message

Error massage: "Use of uninitialized value $text in pattern match (m//)
at ./innotop line 619."


What version of the product are you using? On what operating system?
The error persist on version innotop:
innotop-1.7.2
innotop-1.9.1
Ubuntu 12.04.3 LTS

Please provide any additional information below.
The error occurs only if connect to the database MariaDB 10.0
https://blog.mariadb.org/mariadb-10-0-beta-launched-an-important-milestone/

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[inn...@googlecode.com]

Comment #1 on issue 93 by mbot...@gmail.com: MarriaDB 10.0 InnoDB Row Ops
Error
http://code.google.com/p/innotop/issues/detail?id=93

I'm not much a perl programmer, but I think I fixed/worked around this bug:
it has to do with date & time parsing being different in MariaDB 10.0.
Here's my hacked version that seems to work.


Mark Botner

Attachments:
innotop 437 KB

[inn...@googlecode.com]

Comment #2 on issue 93 by crew...@gmail.com: MarriaDB 10.0 InnoDB Row Ops
Error
http://code.google.com/p/innotop/issues/detail?id=93

Seems to work :) Thanks!

[inn...@googlecode.com]

Comment #3 on issue 93 by quanah.g...@gmail.com: MarriaDB 10.0 InnoDB Row
Ops Error
http://code.google.com/p/innotop/issues/detail?id=93

Correct process is generally to supply a diff in unified diff format. I'll
attach that now. It also fixed the issue for me with MariaDB 10, thank you!

Attachments:
inno.patch 1.5 KB

[inn...@googlecode.com]

Comment #4 on issue 93 by quanah.g...@gmail.com: MarriaDB 10.0 InnoDB Row
Ops Error
http://code.google.com/p/innotop/issues/detail?id=93

However, this is still broken for starting innotop in a specific mode:

for example

innotop -m B

Use of uninitialized value $mysqlversion in pattern match (m//) at
/opt/zimbra/libexec/innotop line 473.

[inn...@googlecode.com]

Comment #5 on issue 93 by quanah.g...@gmail.com: MarriaDB 10.0 InnoDB Row
Ops Error
http://code.google.com/p/innotop/issues/detail?id=93

Here is an updated patch that fixes the problem with the mode startup as
well.

Attachments:
inno.patch 2.9 KB

[inn...@googlecode.com]

Comment #6 on issue 93 by jcoul...@hc1.com: MarriaDB 10.0 InnoDB Row Ops
Error
http://code.google.com/p/innotop/issues/detail?id=93

Has this patched been merged into the core innotop branch? It would be
nice for this to be fixed everywhere as Mariadb becomes more and more
popular.

[inn...@googlecode.com]

Comment #7 on issue 93 by quanah.g...@gmail.com: MarriaDB 10.0 InnoDB Row
Ops Error
http://code.google.com/p/innotop/issues/detail?id=93

Given there hasn't been an update to the code since 2013, it seems like
this project is dead

[inn...@googlecode.com]

Comment #8 on issue 93 by jcoul...@hc1.com: MarriaDB 10.0 InnoDB Row Ops
Error
http://code.google.com/p/innotop/issues/detail?id=93

If somebody wants to add me as a contributor to the project I'll gladly
merge the needed fixes in and release. Otherwise I'm going to fork off to
github (where this sort of workflow is easier) @
https://github.com/ledjon/innotop

[inn...@googlecode.com]

Updates:
Status: Fixed
Owner: lefred.d...@gmail.com

Comment #9 on issue 93 by lefred.d...@gmail.com: MarriaDB 10.0 InnoDB Row
Ops Error
https://code.google.com/p/innotop/issues/detail?id=93

Change committed in trunk.

Thank you for your contribution.