Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 10.0.10-galera
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
We are using InnoDB as the remote DB server which stores the physical data ( With Galera Cluster)
And in front of that , there is another cluster of servers which is built with Spider Engine table. We found that while using 'where' and 'order by' together in select, the returned resultsets are always null(for varchar column) or 0 (int/float/timestamp column) if the column is not mentioned in where and order by. For example, a statement like
select name,createUserId,updateUserId,fabId.price,createTime from product where price>0 and fabId=1 order by createTime
The value of 'name'/'createUserId'/'updateUserId' will be null/0 but others will have its original value.
We have no idea if this is bug of Spider engine or anything related to mariaDB. The origin of database (the remote DB server) will not have this problem if the statement is executed there.
Please help on this issue or let us know if this problem is not about mariaDB. Thanks!
Attached is the snap shot of version information.
If any information insufficient, please let us know and we will provide ASAP.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Fixed in 10.0.12.
revno: 4236 revision-id: kentokushiba@gmail.com-20140608105211-gkkkon05dni2c3in parent: psergey@askmonty.org-20140607214505-8y182z967i8jp7vw committer: Kentoku SHIBA <kentokushiba@gmail.com> branch nick: spider timestamp: Sun 2014-06-08 19:52:11 +0900 message: merge Spider 3.2.4
Ｗe just found a temp solution and somehow the 'root cause' of this issue.
There is a column which is varchar(250) , once we modify the column length<227. Then the query works (or just skip selecting this column can make the result correct )
So is it related to cache size in Spider or ? any parameter we can tune for this? Thanks a lot !