[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-07-11 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081961#comment-16081961
 ] 

ASF GitHub Bot commented on IGNITE-5204:


Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2115


> 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
>
> Attachments: IgniteSqlIssue5204Test.java
>
>
> 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.4.14#64029)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-07-07 Thread Vladimir Ozerov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078005#comment-16078005
 ] 

Vladimir Ozerov commented on IGNITE-5204:
-

Is it fine that UTF8 convering method may return null?

> 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
>
> Attachments: IgniteSqlIssue5204Test.java
>
>
> 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.4.14#64029)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-07-07 Thread Vladimir Ozerov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078004#comment-16078004
 ] 

Vladimir Ozerov commented on IGNITE-5204:
-

[~agoncharuk], could you please take a look at the patch?

> 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
>
> Attachments: IgniteSqlIssue5204Test.java
>
>
> 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.4.14#64029)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-06-09 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1601#comment-1601
 ] 

ASF GitHub Bot commented on IGNITE-5204:


GitHub user skalashnikov opened a pull request:

https://github.com/apache/ignite/pull/2115

IGNITE-5204: Fixed NPE on certain data with index inlining



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5204

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2115.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2115


commit 62aa323162ee7d195574b771c47dfb8bbc5ed58d
Author: skalashnikov 
Date:   2017-06-09T13:31:48Z

IGNITE-5204: Fixed NPE on certain data with index inlining




> 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
>
> Attachments: IgniteSqlIssue5204Test.java
>
>
> 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)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-06-08 Thread Denis Magda (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042917#comment-16042917
 ] 

Denis Magda commented on IGNITE-5204:
-

[~sergi.vladykin], [~vozerov], [~al.psc], please have a look.

> 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)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-06-08 Thread Chris Wang (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042509#comment-16042509
 ] 

Chris Wang commented on IGNITE-5204:


Dear,
I found the things that might reproduce the problem. in the class 
"org.apache.ignite.internal.processors.query.h2.database.InlineIndexHelper" 
line 444:
"size = (short)(s.length | 0x8000);"
when the "s" is null, the logic will cause exception (NullReferenceException) 
cause problem when querying on the cache.
case Value.STRING_IGNORECASE: {
short size;

byte[] s = val.getString().getBytes(CHARSET);
if (s.length + 3 <= maxSize)
size = (short)s.length;
else {
s = trimUTF8(s, maxSize - 3);
size = (short)(s.length | 0x8000);
}

if (s == null) {
// Can't fit anything to
PageUtils.putByte(pageAddr, off, (byte)Value.UNKNOWN);
return 0;
}
else {
PageUtils.putByte(pageAddr, off, (byte)val.getType());
PageUtils.putShort(pageAddr, off + 1, size);
PageUtils.putBytes(pageAddr, off + 3, s);
return s.length + 3;
}
}

> 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)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-05-26 Thread Sergey Kalashnikov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026325#comment-16026325
 ] 

Sergey Kalashnikov commented on IGNITE-5204:


[~wal...@sohu.com],
Thank you. This is valueable info. I did not know you use .NET API.
I rewrote my test for .NET. However, the issue is not reproduced for me. 
Some configuration details might be missing then.
Is it possible that you share your cache configuration?

Here is my .NET test (I have modified one of .NET examples for that purpose)
{code}
/*
 * Licensed to the Apache Software Foundation (ASF) under one or more
 * contributor license agreements.  See the NOTICE file distributed with
 * this work for additional information regarding copyright ownership.
 * The ASF licenses this file to You under the Apache License, Version 2.0
 * (the "License"); you may not use this file except in compliance with
 * the License.  You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

namespace Apache.Ignite.Examples.Datagrid
{
using System;
using System.Text;
using Apache.Ignite.Core;
using Apache.Ignite.Core.Cache;
using Apache.Ignite.Core.Cache.Configuration;
using Apache.Ignite.Core.Cache.Query;
using Apache.Ignite.ExamplesDll.Binary;

/// 
/// This example showcases DML capabilities of Ignite's SQL engine.
/// 
/// 1) Build the project Apache.Ignite.ExamplesDll (select it -> 
right-click -> Build).
///Apache.Ignite.ExamplesDll.dll must appear in 
%IGNITE_HOME%/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/bin/${Platform]/${Configuration}
 folder.
/// 2) Set this class as startup object (Apache.Ignite.Examples project -> 
right-click -> Properties ->
/// Application -> Startup object);
/// 3) Start example (F5 or Ctrl+F5).
/// 
/// This example can be run with standalone Apache Ignite.NET node:
/// 1) Run %IGNITE_HOME%/platforms/dotnet/bin/Apache.Ignite.exe:
/// Apache.Ignite.exe 
-configFileName=platforms\dotnet\examples\apache.ignite.examples\app.config 
-assembly=[path_to_Apache.Ignite.ExamplesDll.dll]
/// 2) Start example.
/// 
public class Ignite5204Example
{
private const string BillCacheName = "bill_cache";

public class Bill
{
[QuerySqlField(IsIndexed = true)]
public string BillId { get; set; }
}

public class Detail
{
[QuerySqlField(IsIndexed = true)]
public string BillId { get; set; }
}

[STAThread]
public static void Main()
{
using (var ignite = Ignition.StartFromApplicationConfiguration())
{
Console.WriteLine();
Console.WriteLine(">>> Example started.");

var billCache = ignite.GetOrCreateCache(
new CacheConfiguration(BillCacheName, 
new QueryEntity(typeof(string), typeof(Bill)),
new QueryEntity(typeof(string), typeof(Detail)) ));

billCache.Clear();

Insert(billCache);
Select(billCache, "Test");

Console.WriteLine();
}

Console.WriteLine();
Console.WriteLine(">>> Example finished, press any key to exit 
...");
Console.ReadKey();
}

private static void Select(ICache billCache, string 
message)
{
Console.WriteLine("\n>>> {0}", message);

var qry = new SqlFieldsQuery("select * from Bill where BillId = 
'草DX009090'");

using (var cursor = billCache.QueryFields(qry))
{
foreach (var row in cursor)
{
Console.WriteLine(">>> {0}", row[0]);
}
}

qry = new SqlFieldsQuery("select bill.*from bill left join detail 
on bill.billid = detail.billid");

using (var cursor = billCache.QueryFields(qry))
{
foreach (var row in cursor)
{
Console.WriteLine(">>> {0}", row[0]);
}
}
}

private static void Insert(ICache billCache)
{
var qry = new SqlFieldsQuery("insert into Bill (_key, BillId) 
values (?, ?)");

qry.Arguments = new object[] {"Bill_1", "DX000"};
billCache.QueryFields(qry);

qry.Arguments = new object[] {"Bill_2",

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-05-25 Thread Chris Wang (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025807#comment-16025807
 ] 

Chris Wang commented on IGNITE-5204:


I do execute the SQL query via the SqlFieldQuery provided in .NET ignite api 
and it is continuously hanging when indexed field have Chinese character in its 
value. Did your automatically testing is based on .net api? or is there any 
possibility that the .net api have same behavior like H2 debug console?


> 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)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-05-25 Thread Sergey Kalashnikov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-05-24 Thread Vladimir Ozerov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022734#comment-16022734
 ] 

Vladimir Ozerov commented on IGNITE-5204:
-

[~wal...@sohu.com], we will look at the problem in the nearest time.

> 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
>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)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-05-21 Thread Chris Wang (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019111#comment-16019111
 ] 

Chris Wang commented on IGNITE-5204:


Dears,
Would you have any plan on the issue IGNITE-5204? so far it present us from 
upgrading the current 1.9 to 2.0 in prod.

Thanks,

> 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
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Assignee: Vladimir Ozerov
>Priority: Critical
>
> 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)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

2017-05-11 Thread Denis Magda (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007260#comment-16007260
 ] 

Denis Magda commented on IGNITE-5204:
-

[~vozerov], [~sergi.vladykin], please look in here.

> 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
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Assignee: Vladimir Ozerov
>Priority: Critical
>
> 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)