[
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024610#comment-16024610
]
Sergey Kalashnikov commented on IGNITE-5204:
--------------------------------------------
[~wal...@sohu.com],
Have you really tried to run these queries via proper Ignite SQL API?
Why do you use H2 Debug console to run queries?
I made an automatic test using your description of the issue. The test uses
Ignite cache query API.
With this automatic test, I have not managed to reproduce the problem.
I was only able to reproduce the first issue manually with the help of H2 debug
console connected to the Ignite client node.
The root cause of the issue is that for client node some internals of index are
not initialized (intentionally).
This can only be a problem if you use H2 Debug console to run queries.
In fact, for the query to be run properly, it must go through Ignite query API.
> The Unicode character in the value of a field which are included in an
> un-unique index will cause "stack overhead" exception
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-5204
> URL: https://issues.apache.org/jira/browse/IGNITE-5204
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
> Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
> Reporter: Chris Wang
> Assignee: Sergey Kalashnikov
> Priority: Critical
> Fix For: 2.1
>
>
> When put "草DX009090" as the value of BillId, which is a field of entity
> Bill. If I define a index includes the BillId, and execute the query like
> "select * from Bill where BillId=’草DX009090‘ in the H2 debug console, there
> throws an exception by the H2 with a code 5000.
> another scenario is, I have two entities, "Bill" and "Detail", both have
> field "BillId". If either of them have value like "草DX009090" and execute the
> query like "select bill.* from bill left join detail on
> bill.billid=detail.billid", the whole ignite cache node will halt ( suppose
> there should be an stack overhead exception, dead loop).
> ======================
> I think the issue should relate to hash computing on the unicode character.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
