[jira] [Created] (IGNITE-2221) CPP: Need to implement Decimal data type support for binary protocol.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2221:
---

 Summary: CPP: Need to implement Decimal data type support for 
binary protocol.
 Key: IGNITE-2221
 URL: https://issues.apache.org/jira/browse/IGNITE-2221
 Project: Ignite
  Issue Type: Bug
  Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Decimal data type support needs to be implemented because some SQL queries 
return data of that type and we need to be able to deserialize it on the C++ 
client side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1979) Support case insensitive nonquoted cache names in SQL queries

[Sergi Vladykin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergi Vladykin resolved IGNITE-1979.

Resolution: Fixed

Reviewed and merged to 1.5

> Support case insensitive nonquoted cache names in SQL queries
> -
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.6
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache 
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation 
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive 
> and can contain all kind of symbols that are not supported by underlying H2 
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}} 
> that will let the end user use a cache name in case insensitive manner 
> without quoted identifiers in SQL queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1979) Support case insensitive nonquoted cache names in SQL queries

[Sergi Vladykin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergi Vladykin closed IGNITE-1979.
--

> Support case insensitive nonquoted cache names in SQL queries
> -
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.6
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache 
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation 
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive 
> and can contain all kind of symbols that are not supported by underlying H2 
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}} 
> that will let the end user use a cache name in case insensitive manner 
> without quoted identifiers in SQL queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2224) Add getEntry methods to the IgniteCache API

[Dmitriy Setrakyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-2224:
--
Description: 
We should have the following methods returning 
{{org.apache.ignite.cache.CacheEntry}}:
{code}
CacheEntry getEntry(K);
Collection> getEntries(Collection);
{code}
These methods should be available on {{IgniteCache}} API. The returned entries 
should include the additional information available on the {{CacheEntry}}, like 
{{updateTime}} or {{version}}.

  was:
We should have the following methods returning 
{{org.apache.ignite.cache.CacheEntry}}:
{code}
CacheEntry getEntry(K);
Collection> getEntries(Collection);
{code}


> Add getEntry methods to the IgniteCache API
> ---
>
> Key: IGNITE-2224
> URL: https://issues.apache.org/jira/browse/IGNITE-2224
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
> Fix For: 1.6
>
>
> We should have the following methods returning 
> {{org.apache.ignite.cache.CacheEntry}}:
> {code}
> CacheEntry getEntry(K);
> Collection> getEntries(Collection);
> {code}
> These methods should be available on {{IgniteCache}} API. The returned 
> entries should include the additional information available on the 
> {{CacheEntry}}, like {{updateTime}} or {{version}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2224) Add getEntry methods to the IgniteCache API

[Dmitriy Setrakyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-2224:
--
Labels: newbie  (was: )

> Add getEntry methods to the IgniteCache API
> ---
>
> Key: IGNITE-2224
> URL: https://issues.apache.org/jira/browse/IGNITE-2224
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>  Labels: newbie
> Fix For: 1.6
>
>
> We should have the following methods returning 
> {{org.apache.ignite.cache.CacheEntry}}:
> {code}
> CacheEntry getEntry(K);
> Collection> getEntries(Collection);
> {code}
> These methods should be available on {{IgniteCache}} API. The returned 
> entries should include the additional information available on the 
> {{CacheEntry}}, like {{updateTime}} or {{version}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2223:
---

 Summary: CPP: ODBC queries sometimes return wrong types for 
columns in metadata.
 Key: IGNITE-2223
 URL: https://issues.apache.org/jira/browse/IGNITE-2223
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Some SQL queries return wrong types in metadata. For example, if query result 
set has column of type "Decimal" it will be transferred as "Long" instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2224) Add getEntry methods to the IgniteCache API

[Dmitriy Setrakyan (JIRA)]

Dmitriy Setrakyan created IGNITE-2224:
-

 Summary: Add getEntry methods to the IgniteCache API
 Key: IGNITE-2224
 URL: https://issues.apache.org/jira/browse/IGNITE-2224
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Dmitriy Setrakyan
 Fix For: 1.6


We should have the following methods returning 
{{org.apache.ignite.cache.CacheEntry}}:
{code}
CacheEntry getEntry(K);
Collection> getEntries(Collection);
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2222) CPP: Implement Date data type support for binary protocol.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-:

Summary: CPP: Implement Date data type support for binary protocol.  (was: 
CPP: Implement Date type support for binary protocol.)

> CPP: Implement Date data type support for binary protocol.
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Date data type support needs to be implemented because some SQL queries 
> return data of that type and we need to be able to deserialize it on the C++ 
> client side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2221) CPP: Implement Decimal data type support for binary protocol.

[Igor Sapego (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Sapego updated IGNITE-2221:

Summary: CPP: Implement Decimal data type support for binary protocol.  
(was: CPP: Need to implement Decimal data type support for binary protocol.)

> CPP: Implement Decimal data type support for binary protocol.
> -
>
> Key: IGNITE-2221
> URL: https://issues.apache.org/jira/browse/IGNITE-2221
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Decimal data type support needs to be implemented because some SQL queries 
> return data of that type and we need to be able to deserialize it on the C++ 
> client side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2222) CPP: Implement Date type support for binary protocol.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-:
---

 Summary: CPP: Implement Date type support for binary protocol.
 Key: IGNITE-
 URL: https://issues.apache.org/jira/browse/IGNITE-
 Project: Ignite
  Issue Type: Bug
  Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Date data type support needs to be implemented because some SQL queries return 
data of that type and we need to be able to deserialize it on the C++ client 
side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (IGNITE-2188) Incorrect links in platform .Net documentation

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reopened IGNITE-2188:


> Incorrect links in platform .Net documentation
> --
>
> Key: IGNITE-2188
> URL: https://issues.apache.org/jira/browse/IGNITE-2188
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, interop
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Fix For: 1.5
>
>
> Lets open platforms/dotnet/docs/index.html.
> On the right side "Apache" word linked to 
> file:///.../platforms/dotnet/docs/namespace_apache.html
> Same issues on other descriptions in Packages, Classes lists



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2190) ScanQuery without a filter triggers object's deserialization on the server side

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-2190:

Assignee: Alexey Goncharuk

> ScanQuery without a filter triggers object's deserialization on the server 
> side
> ---
>
> Key: IGNITE-2190
> URL: https://issues.apache.org/jira/browse/IGNITE-2190
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
> Attachments: ScanQueryBug.java
>
>
> The issue is reproduced on version 1.4 where legacy PortableMarshaller is 
> used. However, I'm quiet sure that the issue happens when BinaryMarshaller is 
> used as well in 1.5.
> 1) Start a server using ignite.sh/bat
> 2) Create a simple app, that uses binary or portable marshaller, creates a 
> cache dynamically and executes a ScanQuery like below
> {{int size=employees1.query(new ScanQuery()).getAll().size();}}
> 3) As you see the query doesn't use any filters. However on the server side 
> some filter is still being checked 
> {{org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$5.checkPredicate(GridCacheQueryManager.java:963)}}
>  which makes the server to deserialize a value.
> According to the stack trace there is some internal filter that triggered 
> checkPredicate function - 
> filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b.
> {noformat}
> [11:05:22,725][SEVERE][ignite-#25%sys-null%][GridCacheDistributedQueryManager]
>   Failed to run query [qry=GridCacheQueryInfo [loc=false, 
> trans=null, rdc=null, qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b, 
> part=null, incMeta=false, metrics=null, pageSize=1024, timeout=0, 
> keepAll=false, incBackups=false, dedup=false, prj=null, keepPortable=false, 
> subjId=c6aeb542-1693-4b5f-89db-96db50e3435f, taskHash=0], locFut=null, 
> sndId=c6aeb542-1693-4b5f-89db-96db50e3435f, reqId=14, incMeta=false, 
> all=false], node=209c237a-9e33-4d05-abe4-bbc14f93c439]
> class org.apache.ignite.IgniteCheckedException: 
> **.SubMessageB
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$CachedResult.iterator(GridCacheQueryManager.java:2784)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runQuery(GridCacheQueryManager.java:1376)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryRequest(GridCacheDistributedQueryManager.java:226)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:105)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:103)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:580)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:198)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:77)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:160)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> **.SubMessageB
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 

[jira] [Commented] (IGNITE-2122) .NET: Add generic Read/WriteCollection and Read/WriteDictionary methods.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2122:


Moved to 1.6 because of api uncertainty.
Let's do a simple cleanup for 1.5: IGNITE-2215

> .NET: Add generic Read/WriteCollection and Read/WriteDictionary methods.
> 
>
> Key: IGNITE-2122
> URL: https://issues.apache.org/jira/browse/IGNITE-2122
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2218) Ignite nodes cannot run Hadoop native code (e.g. snappy)

[Ivan Veselovsky (JIRA)]

Ivan Veselovsky created IGNITE-2218:
---

 Summary: Ignite nodes cannot run Hadoop native code (e.g. snappy)
 Key: IGNITE-2218
 URL: https://issues.apache.org/jira/browse/IGNITE-2218
 Project: Ignite
  Issue Type: Bug
Reporter: Ivan Veselovsky
Assignee: Ivan Veselovsky


Mapreduce tasks fail with the following exception:
{code}
class org.apache.ignite.IgniteCheckedException: class 
org.apache.ignite.IgniteCheckedException: native snappy library not available: 
this version of libhadoop was built without snappy support.
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0(HadoopV2MapTask.java:105)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2Task.run(HadoopV2Task.java:54)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.run(HadoopV2TaskContext.java:249)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.runTask(HadoopRunnableTask.java:201)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call0(HadoopRunnableTask.java:144)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask$1.call(HadoopRunnableTask.java:116)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask$1.call(HadoopRunnableTask.java:114)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1.run(HadoopV2TaskContext.java:550)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.runAsJobOwner(HadoopV2TaskContext.java:548)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call(HadoopRunnableTask.java:114)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call(HadoopRunnableTask.java:46)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecutorService$2.body(HadoopExecutorService.java:186)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: native snappy library not available: 
this version of libhadoop was built without snappy support.
at 
org.apache.hadoop.io.compress.SnappyCodec.checkNativeCodeLoaded(SnappyCodec.java:65)
at 
org.apache.hadoop.io.compress.SnappyCodec.getDecompressorType(SnappyCodec.java:193)
at org.apache.hadoop.io.compress.CodecPool.getDecompressor(CodecPool.java:178)
at 
org.apache.hadoop.mapreduce.lib.input.LineRecordReader.initialize(LineRecordReader.java:90)
at 
com.splunk.mr.input.SplunkLineRecordReader.vixInitialize(SplunkLineRecordReader.java:17)
at 
com.splunk.mr.input.BaseSplunkRecordReader.initialize(BaseSplunkRecordReader.java:95)
at 
com.splunk.mr.JobSubmitterInputFormat.createRecordReader(JobSubmitterInputFormat.java:66)
at 
com.splunk.mr.JobSubmitterInputFormat.createRecordReader(JobSubmitterInputFormat.java:21)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0(HadoopV2MapTask.java:74)
... 16 more
at 
org.apache.ignite.internal.processors.hadoop.HadoopUtils.transformException(HadoopUtils.java:290)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.run(HadoopV2TaskContext.java:255)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.runTask(HadoopRunnableTask.java:201)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call0(HadoopRunnableTask.java:144)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask$1.call(HadoopRunnableTask.java:116)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask$1.call(HadoopRunnableTask.java:114)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1.run(HadoopV2TaskContext.java:550)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
at 
org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.runAsJobOwner(HadoopV2TaskContext.java:548)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call(HadoopRunnableTask.java:114)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call(HadoopRunnableTask.java:46)
at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecutorService$2.body(HadoopExecutorService.java:186)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{code}

This happens because class org.apache.hadoop.util.NativeCodeLoader substituted 
with org.apache.ignite.internal.processors.hadoop.v2.HadoopNativeCodeLoader .




--
This 

[jira] [Assigned] (IGNITE-2217) Add BinaryConfiguration support to cluster screen

[Vasiliy Sisko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasiliy Sisko reassigned IGNITE-2217:
-

Assignee: Vasiliy Sisko

> Add BinaryConfiguration support to cluster screen
> -
>
> Key: IGNITE-2217
> URL: https://issues.apache.org/jira/browse/IGNITE-2217
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2078) Need to clean cache after query in CacheQueryExample

[Alexey Goncharuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Goncharuk resolved IGNITE-2078.
--
Resolution: Fixed

This should be fixed in ignite-1.5 by now.

> Need to clean cache after query in CacheQueryExample
> 
>
> Key: IGNITE-2078
> URL: https://issues.apache.org/jira/browse/IGNITE-2078
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
> Environment: OS X 10.10.2
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1. Build examples 
> 2. Start several nodes: org/apache/ignite/examples/ExampleNodeStartup.java
> 3. Run org/apache/ignite/examples/datagrid/CacheQueryExample.java
> Example output:
> {noformat}
> >>> Cache query example started.
> >>> People with salaries between 0 and 1000 (queried with SCAN query): 
> >>> Entry [key=AffinityKey [key=1717604734904449, 
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe, 
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has 
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239, 
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
> >>> Bachelor Degree., salary=1000.0]]
> >>> People with salaries between 0 and 1000 (queried with SQL query): 
> >>> Entry [key=AffinityKey [key=1717604734904449, 
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe, 
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has 
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239, 
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
> >>> Bachelor Degree., salary=1000.0]]
> >>> People with salaries between 1000 and 2000 (queried with SQL query): 
> >>> Entry [key=AffinityKey [key=6165286975353599015, 
> >>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith, 
> >>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has 
> >>> Master Degree., salary=2000.0]]
> >>> Entry [key=AffinityKey [key=-3732623193094597924, 
> >>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe, 
> >>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has 
> >>> Master Degree., salary=2000.0]]
> >>> Following people are 'ApacheIgnite' employees: 
> >>> Following people are 'Other' employees: 
> >>> Entry [key=AffinityKey [key=-591199628496362239, 
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
> >>> Bachelor Degree., salary=1000.0]]
> >>> Following people have 'Master Degree' in their resumes: 
> >>> Entry [key=AffinityKey [key=6165286975353599015, 
> >>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith, 
> >>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has 
> >>> Master Degree., salary=2000.0]]
> >>> Entry [key=AffinityKey [key=-3732623193094597924, 
> >>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe, 
> >>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has 
> >>> Master Degree., salary=2000.0]]
> >>> Following people have 'Bachelor Degree' in their resumes: 
> >>> Entry [key=AffinityKey [key=1717604734904449, 
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe, 
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has 
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239, 
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
> >>> Bachelor Degree., salary=1000.0]]
> >>> Average salary for 'ApacheIgnite' employees: 
> >>> [null]
> >>> Names of all employees:
> >>> [Jane Smith]
> >>> [Jane Doe]
> >>> [John Doe]
> >>> [John Smith]
> >>> Names of all employees and organizations they belong to:
> >>> [John Smith, Other]
> >>> Cache query example finished.
> [13:01:23] Ignite node stopped OK [uptime=00:00:01:297]
> {noformat}
> 4. Start example second time (don't stop nodes).
> Example output:
> {noformat}
> >>> Cache query example started.
> >>> People with salaries between 0 and 1000 (queried with SCAN query): 
> >>> Entry [key=AffinityKey [key=1717604734904449, 
> >>> affKey=-6908357575301716955], val=Person 

[jira] [Resolved] (IGNITE-1979) Support case insensitive nonquoted cache names in SQL queries

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-1979.
--
Assignee: Pavel Konstantinov  (was: Vladimir Ershov)

Pavel, please test this new feature.
You need to configure sql schema in cache config and test sql queries with this 
schema.
Also Visor console should show sql schema in cache configuration.

> Support case insensitive nonquoted cache names in SQL queries
> -
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.6
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache 
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation 
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive 
> and can contain all kind of symbols that are not supported by underlying H2 
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}} 
> that will let the end user use a cache name in case insensitive manner 
> without quoted identifiers in SQL queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2214) Incorrect java-code for near configuration

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-2214.
--
Assignee: (was: Pavel Konstantinov)

Tested.

> Incorrect java-code for near configuration
> --
>
> Key: IGNITE-2214
> URL: https://issues.apache.org/jira/browse/IGNITE-2214
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> Here is the currently generated java-code is:
> {code}
>  cache1.setNearConfiguration(new NearCacheConfiguration());
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
> {code}
> 'nearConfiguration' variable is undefined.
> The right code should be:
> {code}
>  NearCacheConfiguration nearConfiguration = new NearCacheConfiguration();
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
>  cache1.setNearConfiguration(nearConfiguration);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2180) Javadocs for some modules are missing from Maven repository

[Sergey Kozlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Kozlov updated IGNITE-2180:
--
Fix Version/s: (was: 1.5)
   1.6

> Javadocs for some modules  are missing from Maven repository 
> -
>
> Key: IGNITE-2180
> URL: https://issues.apache.org/jira/browse/IGNITE-2180
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.5
> Environment: Apache Ignite 1.5.0-b2 build #112
>Reporter: Vasilisa  Sidorova
> Fix For: 1.6
>
>
> Javadocs are missing from Maven repository for following modules:
> * ignite-clients
> * ignite-extdata-uri
> * ignite-osgi-karaf
> * ignite-osgi-paxlogging
> * ignite-scalar
> * ignite-scalar_2.10
> * ignite-spark
> * ignite-spark_2.10
> * ignite-visor-console
> * ignite-visor-console_2.10
> Please, fix it



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2225) Externalizable classes are serialized twice with binary marshaller

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2225:
---

 Summary: Externalizable classes are serialized twice with binary 
marshaller
 Key: IGNITE-2225
 URL: https://issues.apache.org/jira/browse/IGNITE-2225
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Valentin Kulichenko
Priority: Blocker
 Fix For: 1.5


Test that reproduces that issue is attached to IGNITE-2212



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2216:

Fix Version/s: (was: 1.6)
   1.5

> Duplicate field names with aliases do not work in queries.
> --
>
> Key: IGNITE-2216
> URL: https://issues.apache.org/jira/browse/IGNITE-2216
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1979) Support case insensitive nonquoted cache names in SQL queries

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-1979:
-

Guys,

We need to be sure that there is no performance drop as well for a standard use 
case - without a schema being set. Also I would run benchmarks for the case 
with a schema being set explicitly.

> Support case insensitive nonquoted cache names in SQL queries
> -
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.6
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache 
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation 
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive 
> and can contain all kind of symbols that are not supported by underlying H2 
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}} 
> that will let the end user use a cache name in case insensitive manner 
> without quoted identifiers in SQL queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1079) Implement Ignite-based cluster manager for Vert.x framework.

[Dmitriy Setrakyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1079:
--
Fix Version/s: (was: 1.5)
   1.6

> Implement Ignite-based cluster manager for Vert.x framework.
> 
>
> Key: IGNITE-1079
> URL: https://issues.apache.org/jira/browse/IGNITE-1079
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Gura
>Priority: Trivial
>  Labels: newbie
> Fix For: 1.6
>
>
> Implement Ignite-based cluster manager for Vert.x framework: http://vertx.io/
> vertx-hazelcast could be used as start point: 
> https://github.com/vert-x3/vertx-hazelcast



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.

[Konstantin Boudnik (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Boudnik closed IGNITE-1555.
--

> Combine ignite-hadoop and ignite-spark into signle assembly for downstream 
> consumption.
> ---
>
> Key: IGNITE-1555
> URL: https://issues.apache.org/jira/browse/IGNITE-1555
> Project: Ignite
>  Issue Type: New Feature
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 1.5
>
> Attachments: IGNITE-1555.patch, IGNITE-1555.patch, IGNITE-1555.patch, 
> IGNITE-1555.patch
>
>
> Let's combine all nice things that Ignite provides for Hadoop and Spark into 
> single assembly called ignite-accelerator. This will be advantageous for 
> downstream integrators like Bigtop, where all bits can be packaged together, 
> tested, and deployed with proper configurations and permissions to avoid 
> interoperability issues. A typical is when spark-shell starts an Ignite node 
> which crashes because user 'spark' isn't allowed to write into Ignite's 
> work-dir, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2206) Make the file SecondaryFileSystemProvider pluggable

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2206:

Fix Version/s: (was: 1.5)
   1.6

> Make the file SecondaryFileSystemProvider pluggable
> ---
>
> Key: IGNITE-2206
> URL: https://issues.apache.org/jira/browse/IGNITE-2206
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop, IGFS
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: 1.6
>
> Attachments: 2206.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2181) Refactoring summary page, implement form fields

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov closed IGNITE-2181.
--
Assignee: (was: Andrey Novikov)

Reviewed, merged.

> Refactoring summary page, implement form fields
> ---
>
> Key: IGNITE-2181
> URL: https://issues.apache.org/jira/browse/IGNITE-2181
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.6
>Reporter: Dmitriyff
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2205) clause HAVING doesn't work for count

[Sergi Vladykin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergi Vladykin closed IGNITE-2205.
--

> clause HAVING doesn't work for count
> 
>
> Key: IGNITE-2205
> URL: https://issues.apache.org/jira/browse/IGNITE-2205
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Sergey Soldatov
>Assignee: Sergi Vladykin
> Fix For: 1.5
>
>
> The setup is similar to IGNITE-2143
> Can be reproduced on a single node.
> Query : 
> sharedRDD.sql("select lang, count(lang) as cnt from gitrecord group by lang 
> having cnt > 5").show
> The result set contains all elements like there is no HAVING clause. That's 
> reproducible only for count field. Others works like a charm.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2190) ScanQuery without a filter triggers object's deserialization on the server side

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2190:
-

The issue is still reproduced even after IGNITE-2178 has been fixed.

Attached a reproducible example that was executing again ignite-1.5 branch.

> ScanQuery without a filter triggers object's deserialization on the server 
> side
> ---
>
> Key: IGNITE-2190
> URL: https://issues.apache.org/jira/browse/IGNITE-2190
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
>
> The issue is reproduced on version 1.4 where legacy PortableMarshaller is 
> used. However, I'm quiet sure that the issue happens when BinaryMarshaller is 
> used as well in 1.5.
> 1) Start a server using ignite.sh/bat
> 2) Create a simple app, that uses binary or portable marshaller, creates a 
> cache dynamically and executes a ScanQuery like below
> {{int size=employees1.query(new ScanQuery()).getAll().size();}}
> 3) As you see the query doesn't use any filters. However on the server side 
> some filter is still being checked 
> {{org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$5.checkPredicate(GridCacheQueryManager.java:963)}}
>  which makes the server to deserialize a value.
> According to the stack trace there is some internal filter that triggered 
> checkPredicate function - 
> filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b.
> {noformat}
> [11:05:22,725][SEVERE][ignite-#25%sys-null%][GridCacheDistributedQueryManager]
>   Failed to run query [qry=GridCacheQueryInfo [loc=false, 
> trans=null, rdc=null, qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b, 
> part=null, incMeta=false, metrics=null, pageSize=1024, timeout=0, 
> keepAll=false, incBackups=false, dedup=false, prj=null, keepPortable=false, 
> subjId=c6aeb542-1693-4b5f-89db-96db50e3435f, taskHash=0], locFut=null, 
> sndId=c6aeb542-1693-4b5f-89db-96db50e3435f, reqId=14, incMeta=false, 
> all=false], node=209c237a-9e33-4d05-abe4-bbc14f93c439]
> class org.apache.ignite.IgniteCheckedException: 
> **.SubMessageB
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$CachedResult.iterator(GridCacheQueryManager.java:2784)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runQuery(GridCacheQueryManager.java:1376)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryRequest(GridCacheDistributedQueryManager.java:226)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:105)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:103)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:580)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:198)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:77)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:160)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> **.SubMessageB
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)

[jira] [Updated] (IGNITE-2214) Incorrect java-code for near configuration

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-2214:
---
Description: 
Here is the currently generated java-code is:
{code}
 cache1.setNearConfiguration(new NearCacheConfiguration());
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
{code}

'nearConfiguration' variable is undefined.
The right code should be:
{code}
 nearConfiguration = new NearCacheConfiguration();
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
 cache1.setNearConfiguration(nearConfiguration);
{code}

  was:
Here is the currently generated java-code:
{code}
 cache1.setNearConfiguration(new NearCacheConfiguration());
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
{code}

'nearConfiguration' variable is undefined.
The right code should be:
{code}
 nearConfiguration = new NearCacheConfiguration();
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
 cache1.setNearConfiguration(nearConfiguration);
{code}


> Incorrect java-code for near configuration
> --
>
> Key: IGNITE-2214
> URL: https://issues.apache.org/jira/browse/IGNITE-2214
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 1.6
>
>
> Here is the currently generated java-code is:
> {code}
>  cache1.setNearConfiguration(new NearCacheConfiguration());
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
> {code}
> 'nearConfiguration' variable is undefined.
> The right code should be:
> {code}
>  nearConfiguration = new NearCacheConfiguration();
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
>  cache1.setNearConfiguration(nearConfiguration);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2214) Incorrect java-code for near configuration

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-2214:
---
Description: 
Here is the currently generated java-code is:
{code}
 cache1.setNearConfiguration(new NearCacheConfiguration());
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
{code}

'nearConfiguration' variable is undefined.
The right code should be:
{code}
 NearCacheConfiguration nearConfiguration = new NearCacheConfiguration();
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
 cache1.setNearConfiguration(nearConfiguration);
{code}

  was:
Here is the currently generated java-code is:
{code}
 cache1.setNearConfiguration(new NearCacheConfiguration());
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
{code}

'nearConfiguration' variable is undefined.
The right code should be:
{code}
 nearConfiguration = new NearCacheConfiguration();
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
 cache1.setNearConfiguration(nearConfiguration);
{code}


> Incorrect java-code for near configuration
> --
>
> Key: IGNITE-2214
> URL: https://issues.apache.org/jira/browse/IGNITE-2214
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 1.6
>
>
> Here is the currently generated java-code is:
> {code}
>  cache1.setNearConfiguration(new NearCacheConfiguration());
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
> {code}
> 'nearConfiguration' variable is undefined.
> The right code should be:
> {code}
>  NearCacheConfiguration nearConfiguration = new NearCacheConfiguration();
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
>  cache1.setNearConfiguration(nearConfiguration);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2214) Incorrect java-code for near configuration

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2214:
--

 Summary: Incorrect java-code for near configuration
 Key: IGNITE-2214
 URL: https://issues.apache.org/jira/browse/IGNITE-2214
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


Here is the currently generated java-code:
{code}
 cache1.setNearConfiguration(new NearCacheConfiguration());
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
{code}

'nearConfiguration' variable is undefined.
The right code should be:
{code}
 nearConfiguration = new NearCacheConfiguration();
 LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
 nearEvictionPolicy.setMaxSize(10);
 nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
 cache1.setNearConfiguration(nearConfiguration);
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2188) Incorrect links in platform .Net documentation

[Sergey Kozlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Kozlov closed IGNITE-2188.
-

> Incorrect links in platform .Net documentation
> --
>
> Key: IGNITE-2188
> URL: https://issues.apache.org/jira/browse/IGNITE-2188
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, interop
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Fix For: 1.5
>
>
> Lets open platforms/dotnet/docs/index.html.
> On the right side "Apache" word linked to 
> file:///.../platforms/dotnet/docs/namespace_apache.html
> Same issues on other descriptions in Packages, Classes lists



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2188) Incorrect links in platform .Net documentation

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-2188:
--

Assignee: Pavel Tupitsyn  (was: Sergey Kozlov)

> Incorrect links in platform .Net documentation
> --
>
> Key: IGNITE-2188
> URL: https://issues.apache.org/jira/browse/IGNITE-2188
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, interop
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Fix For: 1.5
>
>
> Lets open platforms/dotnet/docs/index.html.
> On the right side "Apache" word linked to 
> file:///.../platforms/dotnet/docs/namespace_apache.html
> Same issues on other descriptions in Packages, Classes lists



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2215) .NET: Replace collection factory/adder in BinaryReader with Func/Action

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2215:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2215 .NET: Replace collection factory/adder in BinaryReader with 
Func/Action

…th Func/Action

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

$ git pull https://github.com/ptupitsyn/ignite ignite-2215

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

https://github.com/apache/ignite/pull/358.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 #358


commit d8ebff8c5c1be280ed8b9f8f15ccf7c5d9e75dcd
Author: Pavel Tupitsyn 
Date:   2015-12-21T09:27:14Z

IGNITE-2215 .NET: Replace collection factory/adder in BinaryReader with 
Func/Action




> .NET: Replace collection factory/adder in BinaryReader with Func/Action
> ---
>
> Key: IGNITE-2215
> URL: https://issues.apache.org/jira/browse/IGNITE-2215
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.5
>
>
> To make it easier to understand and use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2227) Please add support of cache alias on web console

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2227:
--

 Summary: Please add support of cache alias on web console
 Key: IGNITE-2227
 URL: https://issues.apache.org/jira/browse/IGNITE-2227
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov


https://issues.apache.org/jira/browse/IGNITE-1979



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2222) CPP: Implement Date data type support for binary protocol.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-:

Description: It is need to implement date data type support because some 
SQL queries return data of that type and we need to be able to deserialize it 
on the C++ client side.  (was: Date data type support needs to be implemented 
because some SQL queries return data of that type and we need to be able to 
deserialize it on the C++ client side.)

> CPP: Implement Date data type support for binary protocol.
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> It is need to implement date data type support because some SQL queries 
> return data of that type and we need to be able to deserialize it on the C++ 
> client side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1701) Bump Spark dependenency to 1.5.1 (the latest stable)

[Konstantin Boudnik (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Boudnik closed IGNITE-1701.
--

> Bump Spark dependenency to 1.5.1 (the latest stable)
> 
>
> Key: IGNITE-1701
> URL: https://issues.apache.org/jira/browse/IGNITE-1701
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: ignite-1.4
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 1.5
>
> Attachments: IGNITE-1701.patch
>
>
> At the moment, {{ignite-spark}} module is built against spark 1.3.1 which is 
> like 3 versions old already. Let's bump the version to 1.5.1, which is the 
> latest stable.
> In the process, I'd like to add an ability to specify the version of Spark 
> during the build time, like it is done for Hadoop now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2089) Implement static block callout

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov closed IGNITE-2089.
--
Assignee: (was: Andrey Novikov)

Reviewed, merged.

> Implement static block callout 
> ---
>
> Key: IGNITE-2089
> URL: https://issues.apache.org/jira/browse/IGNITE-2089
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.6
>Reporter: Dmitriyff
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-2216:
---

Assignee: Vladimir Ozerov

> Duplicate field names with aliases do not work in queries.
> --
>
> Key: IGNITE-2216
> URL: https://issues.apache.org/jira/browse/IGNITE-2216
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2225) Externalizable classes are serialized twice with binary marshaller

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-2225:
---

Assignee: Vladimir Ozerov

> Externalizable classes are serialized twice with binary marshaller
> --
>
> Key: IGNITE-2225
> URL: https://issues.apache.org/jira/browse/IGNITE-2225
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Valentin Kulichenko
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Test that reproduces that issue is attached to IGNITE-2212



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2228) .NET: Ensure async Task can be cancelled.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2228:
---

 Summary: .NET: Ensure async Task can be cancelled.
 Key: IGNITE-2228
 URL: https://issues.apache.org/jira/browse/IGNITE-2228
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


Java has IgniteFuture.cancel() method. Depending on the context, it perofrms 
different things. From no-op to task/closure cancellation. 

We need to ensure that TPL infrastructure in .NET is able to propagate 
cancellation to Java future.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2226) Replace dash in 1.5.0-final with dot 1.5.0.final

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-2226:
---

I think we can discuss the better solution on the dev list for 1.6. For now, 
the quickest fix is to replace dash with a dot. Let's do it for 1.50.final 
release.

> Replace dash in 1.5.0-final with dot 1.5.0.final
> 
>
> Key: IGNITE-2226
> URL: https://issues.apache.org/jira/browse/IGNITE-2226
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Dmitriy Setrakyan
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2228) .NET: Ensure async Task can be cancelled.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2228:

Fix Version/s: (was: 1.5)

> .NET: Ensure async Task can be cancelled.
> -
>
> Key: IGNITE-2228
> URL: https://issues.apache.org/jira/browse/IGNITE-2228
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> Java has IgniteFuture.cancel() method. Depending on the context, it perofrms 
> different things. From no-op to task/closure cancellation. 
> We need to ensure that TPL infrastructure in .NET is able to propagate 
> cancellation to Java future.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2228) .NET: Ensure async Task can be cancelled.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2228:

Fix Version/s: 1.6

> .NET: Ensure async Task can be cancelled.
> -
>
> Key: IGNITE-2228
> URL: https://issues.apache.org/jira/browse/IGNITE-2228
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> Java has IgniteFuture.cancel() method. Depending on the context, it perofrms 
> different things. From no-op to task/closure cancellation. 
> We need to ensure that TPL infrastructure in .NET is able to propagate 
> cancellation to Java future.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2070) "Back to Clusters" link doesn't work on Security page

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-2070.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov

Fixed.

> "Back to Clusters" link doesn't work on Security page
> -
>
> Key: IGNITE-2070
> URL: https://issues.apache.org/jira/browse/IGNITE-2070
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> Nothing happens when I clicking on it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2226) Replace dash in 1.5.0-final with dot 1.5.0.final

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-2226:


Yet another discussion will produce a very different result, I am sure ;)

> Replace dash in 1.5.0-final with dot 1.5.0.final
> 
>
> Key: IGNITE-2226
> URL: https://issues.apache.org/jira/browse/IGNITE-2226
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Dmitriy Setrakyan
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2216:
---

 Summary: Duplicate field names with aliases do not work in queries.
 Key: IGNITE-2216
 URL: https://issues.apache.org/jira/browse/IGNITE-2216
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2211) Console SQL tab with wrong address.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-2211:
-
Fix Version/s: 1.6

> Console SQL tab with wrong address.
> ---
>
> Key: IGNITE-2211
> URL: https://issues.apache.org/jira/browse/IGNITE-2211
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> # Open some notebook.
> # Change notebook id in URL to non-existent.
> We can see empty notebook, but expect to see some error page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2214) Incorrect java-code for near configuration

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-2214.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Fixed. Please test.

> Incorrect java-code for near configuration
> --
>
> Key: IGNITE-2214
> URL: https://issues.apache.org/jira/browse/IGNITE-2214
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> Here is the currently generated java-code is:
> {code}
>  cache1.setNearConfiguration(new NearCacheConfiguration());
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
> {code}
> 'nearConfiguration' variable is undefined.
> The right code should be:
> {code}
>  NearCacheConfiguration nearConfiguration = new NearCacheConfiguration();
>  LruEvictionPolicy nearEvictionPolicy = new LruEvictionPolicy();
>  nearEvictionPolicy.setMaxSize(10);
>  nearConfiguration.setNearEvictionPolicy(nearEvictionPolicy);
>  cache1.setNearConfiguration(nearConfiguration);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2195) Accessing from IGFS to HDFS that is in kerberised environment

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2195:

Fix Version/s: (was: 1.5)
   1.6

> Accessing from IGFS to HDFS that is in kerberised environment
> -
>
> Key: IGNITE-2195
> URL: https://issues.apache.org/jira/browse/IGNITE-2195
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop, IGFS
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Ivan Veselovsky
>Priority: Critical
> Fix For: 1.6
>
>
> There is some issue in the current IGFS implementation that doesn't take into 
> account some Kerberos user related settings which leads to the exception 
> below when there is an attempt to work with Kerberised cluster
> {noformat}
> Connecting to HDFS with the following settings [uri=null, cfg=all-site.xml, 
> userName=null]
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> org.apache.hadoop.security.AccessControlException: SIMPLE authentication is 
> not enabled. Available:[TOKEN, KERBEROS]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at 
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
> at 
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73)
> at org.apache.hadoop.hdfs.DFSClient.listPaths(DFSClient.java:2096)
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem$DirListingIterator.(DistributedFileSystem.java:944)
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem$DirListingIterator.(DistributedFileSystem.java:927)
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem$19.doCall(DistributedFileSystem.java:872)
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem$19.doCall(DistributedFileSystem.java:868)
> at 
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem.listLocatedStatus(DistributedFileSystem.java:868)
> at org.apache.hadoop.fs.FileSystem.listLocatedStatus(FileSystem.java:1694)
> at org.apache.hadoop.fs.FileSystem$6.(FileSystem.java:1786)
> at org.apache.hadoop.fs.FileSystem.listFiles(FileSystem.java:1783)
> at com.ig.HadoopFsIssue.main(HadoopFsIssue.java:35)
> Caused by: 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
>  SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS]
> at org.apache.hadoop.ipc.Client.call(Client.java:1427)
> at org.apache.hadoop.ipc.Client.call(Client.java:1358)
> at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy7.getListing(Unknown Source)
> at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getListing(ClientNamenodeProtocolTranslatorPB.java:573)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy8.getListing(Unknown Source)
> at org.apache.hadoop.hdfs.DFSClient.listPaths(DFSClient.java:2094)
> {noformat}
> The issue is fixed in the following way. Need to revisit the fix and check 
> whether it can lead to some other consequences.
> {noformat}
> /**
> * @return {@link org.apache.hadoop.fs.FileSystem}  instance for this 
> secondary Fs.
> * @throws IOException
> */
> public FileSystem createFileSystem(String userName) throws IOException {
> userName = IgfsUtils.fixUserName(userName);
> UserGroupInformation.setConfiguration(cfg);
> UserGroupInformation ugi = UserGroupInformation.createProxyUser(userName, 
> UserGroupInformation.getCurrentUser());
> try {
> return ugi.doAs(new PrivilegedExceptionAction() {
> @Override
> public FileSystem run() throws Exception {
> return FileSystem.get(uri, cfg);
> }
> });
> } catch (InterruptedException e) {
> 

[jira] [Commented] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2216:
-

Sample test reproducing the issue. It fails with both OptimziedMarshaller and 
BinaryMarshaller.

{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.
 */

package org.apache.ignite.internal.processors.cache;

import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.Ignition;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.CacheRebalanceMode;
import org.apache.ignite.cache.CacheWriteSynchronizationMode;
import org.apache.ignite.cache.query.SqlFieldsQuery;
import org.apache.ignite.cache.query.SqlQuery;
import org.apache.ignite.cache.query.annotations.QuerySqlField;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.binary.BinaryMarshaller;
import org.apache.ignite.internal.util.typedef.G;
import org.apache.ignite.marshaller.optimized.OptimizedMarshaller;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;

import javax.cache.Cache;
import java.util.Iterator;
import java.util.List;

/**
 * Tests for class with duplicate field names and aliases on them.
 */
public class BinaryDuplicateFieldsWithAliasQuerySelfTest extends 
GridCommonAbstractTest {
/** Field 1. */
private static final String FIELD_1 = "x1";

/** Field 2. */
private static final String FIELD_2 = "x2";

/** Ignite instance. */
private Ignite ignite;

/** Cache. */
private IgniteCache cache;

/** {@inheritDoc} */
@SuppressWarnings("unchecked")
@Override protected void beforeTest() throws Exception {
IgniteConfiguration cfg = new IgniteConfiguration();

cfg.setLocalHost("127.0.0.1");

TcpDiscoverySpi discoSpi = new TcpDiscoverySpi();
discoSpi.setIpFinder(new TcpDiscoveryVmIpFinder(true));
cfg.setDiscoverySpi(discoSpi);

//cfg.setMarshaller(new BinaryMarshaller());
cfg.setMarshaller(new OptimizedMarshaller());

CacheConfiguration cacheCfg = new CacheConfiguration();

cacheCfg.setName(null);
cacheCfg.setCacheMode(CacheMode.PARTITIONED);
cacheCfg.setAtomicityMode(CacheAtomicityMode.ATOMIC);

cacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
cacheCfg.setRebalanceMode(CacheRebalanceMode.SYNC);

cacheCfg.setIndexedTypes(Integer.class, Entity2.class);

cfg.setCacheConfiguration(cacheCfg);

ignite = Ignition.start(cfg);

cache = ignite.cache(null);
}

/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
G.stopAll(true);

ignite = null;
cache = null;
}

/**
 * Test duplicate fields querying.
 *
 * @throws Exception If failed.
 */
@SuppressWarnings("unchecked")
public void testDuplicateFields() throws Exception {
cache.put(1, new Entity2(10, 11));
cache.put(2, new Entity2(20, 21));
cache.put(3, new Entity2(30, 31));

// Test first field.
Iterator iter = cache.query(new SqlQuery(Entity2.class, FIELD_1 + 
"=20")).iterator();

assert iter.hasNext();

Cache.Entry res = (Cache.Entry)iter.next();

assertEquals(2, (int)res.getKey());
assertEquals(20, res.getValue().get1());
assertEquals(21, res.getValue().get2());

assert !iter.hasNext();

// Test second field.
iter = cache.query(new SqlQuery(Entity2.class, FIELD_2 + 
"=21")).iterator();

assert iter.hasNext();

res = (Cache.Entry)iter.next();

assertEquals(2, (int)res.getKey());
assertEquals(20, res.getValue().get1());
assertEquals(21, res.getValue().get2());

assert 

[jira] [Closed] (IGNITE-2215) .NET: Replace collection factory/adder in BinaryReader with Func/Action

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-2215.
---

> .NET: Replace collection factory/adder in BinaryReader with Func/Action
> ---
>
> Key: IGNITE-2215
> URL: https://issues.apache.org/jira/browse/IGNITE-2215
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> To make it easier to understand and use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2208) Queries with object arguments doesn't work wth BinaryMarshaller.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2208:

Fix Version/s: (was: 1.5)
   1.6

> Queries with object arguments doesn't work wth BinaryMarshaller.
> 
>
> Key: IGNITE-2208
> URL: https://issues.apache.org/jira/browse/IGNITE-2208
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> This happens because we cannot compare binary and non-binary objects.
> Problematic code frame: 
> {code}
> GridH2ValueCacheObject.compareSecure
> {code}
> Affected tests:
> {code}
> IgniteCacheAbstractQuerySelfTest.testObjectQuery
> IgniteCacheAbstractQuerySelfTest.testBadHashObjectKey
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2210) Cannot query annotated methods when BinaryMarshaller is set.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2210:

Component/s: (was: interop)

> Cannot query annotated methods when BinaryMarshaller is set.
> 
>
> Key: IGNITE-2210
> URL: https://issues.apache.org/jira/browse/IGNITE-2210
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> Because it is impossible to call method from object in binary form. Several 
> solutions could be applied here:
> 1) Throw exception when method annotation is found and BinaryMarshaller is 
> set.
> 2) Or call this method and record it as a field to the object.
> Sample test: 
> IgniteCacheAbstractFieldsQuerySelfTest.testMethodAnnotationWithoutGet



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2208) Queries with object arguments doesn't work wth BinaryMarshaller.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2208:

Component/s: (was: interop)

> Queries with object arguments doesn't work wth BinaryMarshaller.
> 
>
> Key: IGNITE-2208
> URL: https://issues.apache.org/jira/browse/IGNITE-2208
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
> Fix For: 1.6
>
>
> This happens because we cannot compare binary and non-binary objects.
> Problematic code frame: 
> {code}
> GridH2ValueCacheObject.compareSecure
> {code}
> Affected tests:
> {code}
> IgniteCacheAbstractQuerySelfTest.testObjectQuery
> IgniteCacheAbstractQuerySelfTest.testBadHashObjectKey
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2208) Queries with object arguments doesn't work wth BinaryMarshaller.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2208:

Assignee: (was: Vladimir Ozerov)

> Queries with object arguments doesn't work wth BinaryMarshaller.
> 
>
> Key: IGNITE-2208
> URL: https://issues.apache.org/jira/browse/IGNITE-2208
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
> Fix For: 1.6
>
>
> This happens because we cannot compare binary and non-binary objects.
> Problematic code frame: 
> {code}
> GridH2ValueCacheObject.compareSecure
> {code}
> Affected tests:
> {code}
> IgniteCacheAbstractQuerySelfTest.testObjectQuery
> IgniteCacheAbstractQuerySelfTest.testBadHashObjectKey
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2210) Cannot query annotated methods when BinaryMarshaller is set.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2210:

Fix Version/s: (was: 1.5)
   1.6

> Cannot query annotated methods when BinaryMarshaller is set.
> 
>
> Key: IGNITE-2210
> URL: https://issues.apache.org/jira/browse/IGNITE-2210
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> Because it is impossible to call method from object in binary form. Several 
> solutions could be applied here:
> 1) Throw exception when method annotation is found and BinaryMarshaller is 
> set.
> 2) Or call this method and record it as a field to the object.
> Sample test: 
> IgniteCacheAbstractFieldsQuerySelfTest.testMethodAnnotationWithoutGet



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2217) Add BinaryConfiguration support to cluster screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2217:


 Summary: Add BinaryConfiguration support to cluster screen
 Key: IGNITE-2217
 URL: https://issues.apache.org/jira/browse/IGNITE-2217
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2213) Handle duplicate field names in BinaryMarshaller.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2213:

Summary: Handle duplicate field names in BinaryMarshaller.  (was: Handle 
duplicate field names in BniaryMarshaller.)

> Handle duplicate field names in BinaryMarshaller.
> -
>
> Key: IGNITE-2213
> URL: https://issues.apache.org/jira/browse/IGNITE-2213
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Consider the following scenario:
> {code}
> class A {
> int field;
> }
> class B : class A {
> int field;
> }
> {code}
> In this case BinaryMarshaller will throw an exception about duplicate field 
> names. And there is no sensible workaround for user. 
> We can add some prefix/suffix to comflicting fields. E.g. A.field will be 
> written as "field", B.field will be written as "field_B".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2216:

Component/s: (was: general)
 cache

> Duplicate field names with aliases do not work in queries.
> --
>
> Key: IGNITE-2216
> URL: https://issues.apache.org/jira/browse/IGNITE-2216
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2185) CPP: Investigate version policies for autotools.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2185:

Fix Version/s: (was: 1.5)
   1.6

> CPP: Investigate version policies for autotools.
> 
>
> Key: IGNITE-2185
> URL: https://issues.apache.org/jira/browse/IGNITE-2185
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> Starting from this release we gave different version scheme - suffix is 
> added. E.g.: 1.5.0-b1, 1.5.0-GA, etc.
> We need to understand how to properly handle this case with autotools. Can we 
> simply set this string as version?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2184) .NET: Investigate version policies.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-2184.
---

> .NET: Investigate version policies.
> ---
>
> Key: IGNITE-2184
> URL: https://issues.apache.org/jira/browse/IGNITE-2184
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> Starting from this release we have different versioning scheme - suffix is 
> added. E.g.: 1.5.0-b2, 1.5.0-GA, etc.
> We need to understand how to properly update versions in AssemblyInfo.cs 
> files so that correct version is obvious for users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-887) Fix ContinuousQueries to support initial state as well as in-focus and out-of-focus events

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-887:
--

Andrey, I have checked the discussion, and my concerns here are the JCache TCK, 
JCache spec, and the backward compatibility. We have to make sure that we 
conform with all of the above.

> Fix ContinuousQueries to support initial state as well as in-focus and 
> out-of-focus events
> --
>
> Key: IGNITE-887
> URL: https://issues.apache.org/jira/browse/IGNITE-887
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Kornev
> Fix For: 1.6
>
>
> The discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-Query-td136.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2205) clause HAVING doesn't work for count

[Sergi Vladykin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergi Vladykin resolved IGNITE-2205.

Resolution: Fixed

Pushed fix into 1.5

> clause HAVING doesn't work for count
> 
>
> Key: IGNITE-2205
> URL: https://issues.apache.org/jira/browse/IGNITE-2205
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Sergey Soldatov
>Assignee: Sergi Vladykin
> Fix For: 1.5
>
>
> The setup is similar to IGNITE-2143
> Can be reproduced on a single node.
> Query : 
> sharedRDD.sql("select lang, count(lang) as cnt from gitrecord group by lang 
> having cnt > 5").show
> The result set contains all elements like there is no HAVING clause. That's 
> reproducible only for count field. Others works like a charm.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Anton Vinogradov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov reassigned IGNITE-2175:


Assignee: Anton Vinogradov  (was: Yakov Zhdanov)

> Not valid exceptions in case when example can't works with remote node 
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
>   at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
>   ... 13 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:274)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
>   at 
> 

[jira] [Updated] (IGNITE-2110) Replace workarond for local node flag in TcpDiscoveryNode with better solution

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-2110:
-
Fix Version/s: (was: 1.5)
   1.6

> Replace workarond for local node flag in TcpDiscoveryNode with better solution
> --
>
> Key: IGNITE-2110
> URL: https://issues.apache.org/jira/browse/IGNITE-2110
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Minor
> Fix For: 1.6
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> We should get read of this workaround in
> GridDhtAffinityAssignmentResponse#finishUnmarshal
> {code:java}
> // TODO IGNITE-10: setting 'local' for nodes not needed when 
> IGNITE-10 is implemented.
> int assignments = affAssignment.size();
> for (int n = 0; n < assignments; n++) {
> List nodes = affAssignment.get(n);
> int size = nodes.size();
> for (int i = 0; i < size; i++) {
> ClusterNode node = nodes.get(i);
> if (node instanceof TcpDiscoveryNode)
> 
> ((TcpDiscoveryNode)node).local(node.id().equals(ctx.localNodeId()));
> }
> }
> {code}
> by designing new solution for TcpDiscoveryNode.local transient flag



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1081) Create integration for OrientDB

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-1081:
-
Fix Version/s: (was: 1.5)
   1.6

> Create integration for OrientDB
> ---
>
> Key: IGNITE-1081
> URL: https://issues.apache.org/jira/browse/IGNITE-1081
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: sprint-7
>Reporter: Alexey Kuznetsov
>Assignee: Gianfranco Murador
>Priority: Minor
>  Labels: newbie
> Fix For: 1.6
>
>
> Create integration for OrientDB
> Create integration for OrientDB https://github.com/orientechnologies/orientdb
> OHazelcastPlugin can be used as start point: 
> https://github.com/orientechnologies/orientdb/blob/master/distributed/src/main/java/com/orientechnologies/orient/server/hazelcast/OHazelcastPlugin.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2205) clause HAVING doesn't work for count

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-2205:
-
Fix Version/s: (was: 1.5)
   1.6

> clause HAVING doesn't work for count
> 
>
> Key: IGNITE-2205
> URL: https://issues.apache.org/jira/browse/IGNITE-2205
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Sergey Soldatov
>Assignee: Sergi Vladykin
> Fix For: 1.6
>
>
> The setup is similar to IGNITE-2143
> Can be reproduced on a single node.
> Query : 
> sharedRDD.sql("select lang, count(lang) as cnt from gitrecord group by lang 
> having cnt > 5").show
> The result set contains all elements like there is no HAVING clause. That's 
> reproducible only for count field. Others works like a charm.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2087) Ignite CacheManager ignores provided class loader

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-2087:
-
Fix Version/s: (was: 1.5)
   1.6

> Ignite CacheManager ignores provided class loader
> -
>
> Key: IGNITE-2087
> URL: https://issues.apache.org/jira/browse/IGNITE-2087
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.6
>
>
> {{CacheManager}} should delegate the provided class loader to 
> {{IgniteConfiguration.setClassLoader()}}. Currently it's ignored.
> user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Help-with-integrating-Ignite-as-JCache-with-JBoss-EAP-6-4-td2134.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-708) Need to remove background partition exchange

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-708:

Fix Version/s: (was: 1.5)

> Need to remove background partition exchange
> 
>
> Key: IGNITE-708
> URL: https://issues.apache.org/jira/browse/IGNITE-708
> Project: Ignite
>  Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Yakov Zhdanov
>Assignee: Gianfranco Murador
>Priority: Blocker
>  Labels: datagrid
> Fix For: 1.6
>
>
> Now every node sends its partition map to cache coordinator (which is the 
> oldest node in topology) and coordinator spreads full partition map to every 
> node in topology. This happens for each cache separately. This seems to take 
> place even if there were no changes to local partition maps. Given we 
> guarantee communication message delivery this background process seems to be 
> an overkill.
> Exchange should happen only if any changes took place.
> After dynamic cache start has been introduced, we can have significant amount 
> of live caches at some point of app lifecycle and app may suffer from  
> background exchange which is obviously not a requirement (and may be never 
> has been the one).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2205) clause HAVING doesn't work for count

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-2205:
-
Fix Version/s: (was: 1.6)
   1.5

> clause HAVING doesn't work for count
> 
>
> Key: IGNITE-2205
> URL: https://issues.apache.org/jira/browse/IGNITE-2205
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Sergey Soldatov
>Assignee: Sergi Vladykin
> Fix For: 1.5
>
>
> The setup is similar to IGNITE-2143
> Can be reproduced on a single node.
> Query : 
> sharedRDD.sql("select lang, count(lang) as cnt from gitrecord group by lang 
> having cnt > 5").show
> The result set contains all elements like there is no HAVING clause. That's 
> reproducible only for count field. Others works like a charm.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-887) Fix ContinuousQueries to support initial state as well as in-focus and out-of-focus events

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-887:

Fix Version/s: (was: 1.5)
   1.6

> Fix ContinuousQueries to support initial state as well as in-focus and 
> out-of-focus events
> --
>
> Key: IGNITE-887
> URL: https://issues.apache.org/jira/browse/IGNITE-887
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Kornev
> Fix For: 1.6
>
>
> The discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-Query-td136.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2087) Ignite CacheManager ignores provided class loader

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2087:
--

Fixed at 1.5, tests will be provided later.

> Ignite CacheManager ignores provided class loader
> -
>
> Key: IGNITE-2087
> URL: https://issues.apache.org/jira/browse/IGNITE-2087
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.6
>
>
> {{CacheManager}} should delegate the provided class loader to 
> {{IgniteConfiguration.setClassLoader()}}. Currently it's ignored.
> user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Help-with-integrating-Ignite-as-JCache-with-JBoss-EAP-6-4-td2134.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2194) IgniteCacheProxy is not serialized properly.

[Alexey Goncharuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Goncharuk reassigned IGNITE-2194:


Assignee: Alexey Goncharuk

> IgniteCacheProxy is not serialized properly.
> 
>
> Key: IGNITE-2194
> URL: https://issues.apache.org/jira/browse/IGNITE-2194
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 1.6
>
>
> See 
> org.apache.ignite.internal.processors.cache.IgniteCacheSerializationSelfTest
> I believe that only proxy instances should be serializable. However, the 
> change should be done carefully to preserve backward compatibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2194) IgniteCacheProxy is not serialized properly.

[Alexey Goncharuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Goncharuk updated IGNITE-2194:
-
Fix Version/s: (was: 1.5)
   1.6

> IgniteCacheProxy is not serialized properly.
> 
>
> Key: IGNITE-2194
> URL: https://issues.apache.org/jira/browse/IGNITE-2194
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
> Fix For: 1.6
>
>
> See 
> org.apache.ignite.internal.processors.cache.IgniteCacheSerializationSelfTest
> I believe that only proxy instances should be serializable. However, the 
> change should be done carefully to preserve backward compatibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion

[Avihai Berkovitz (JIRA)]

Avihai Berkovitz created IGNITE-2219:


 Summary: ClassCastException from NodeIdMessage to 
AffinityTopologyVersion
 Key: IGNITE-2219
 URL: https://issues.apache.org/jira/browse/IGNITE-2219
 Project: Ignite
  Issue Type: Bug
Affects Versions: ignite-1.4
 Environment: Ubuntu 12.04 64 bit
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
Ignite 1.4.0
Reporter: Avihai Berkovitz


We had a cluster up and running for a couple of days. Without doing anything 
new, we got the following error in one of the nodes:
{noformat}
Caught unhandled exception in NIO worker thread (restart the node). 
java.lang.ClassCastException: 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$NodeIdMessage 
cannot be cast to 
org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:176)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.direct.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:963)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:252)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:249)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:79)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:104)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:78)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2124)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:173)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:898)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1437)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1379)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1263)
 ~[ignite-core-1.4.0.jar:1.4.0]
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
[ignite-core-1.4.0.jar:1.4.0]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
{noformat}

It happened only once so far, but killed the communication from this node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2209) Some query tests fail with ClassCastException when BinaryMarshaller is enabled.

[Alexey Goncharuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Goncharuk closed IGNITE-2209.


> Some query tests fail with ClassCastException when BinaryMarshaller is 
> enabled.
> ---
>
> Key: IGNITE-2209
> URL: https://issues.apache.org/jira/browse/IGNITE-2209
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 1.5
>
>
> *Problem*
> Sample stack trace:
> {code}
> java.lang.ClassCastException: 
> org.apache.ignite.internal.binary.BinaryObjectImpl cannot be cast to 
> org.apache.ignite.internal.processors.cache.IgniteCacheAbstractQuerySelfTest$ObjectValue
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheAbstractQuerySelfTest.testObjectQueryWithSwap(IgniteCacheAbstractQuerySelfTest.java:574)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1699)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:116)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1637)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> *Steps to reproduce*
> 1) Set BinaryMarshaller
> 2) Run IgniteCacheLocalQuerySelfTest
> 3) Observe failures due to class-cast in the following tests:
> - testArray
> - testObjectQueryWithSwap
> - testComplexType
> *Reason*
> Unknown; looks like we do not unwrap binary objects in some cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2220) upgrade gulp tasks

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2220:
-

 Summary: upgrade gulp tasks
 Key: IGNITE-2220
 URL: https://issues.apache.org/jira/browse/IGNITE-2220
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 1.6
Reporter: Dmitriyff
Assignee: Dmitriyff
 Fix For: 1.6






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2134) .Net: Query configuration via attributes

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn resolved IGNITE-2134.

Resolution: Fixed

> .Net: Query configuration via attributes
> 
>
> Key: IGNITE-2134
> URL: https://issues.apache.org/jira/browse/IGNITE-2134
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> See QuerySqlField and related annotations in Java.
> Need a similar mechanism in .NET



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2134) .Net: Query configuration via attributes

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn closed IGNITE-2134.
--

> .Net: Query configuration via attributes
> 
>
> Key: IGNITE-2134
> URL: https://issues.apache.org/jira/browse/IGNITE-2134
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> See QuerySqlField and related annotations in Java.
> Need a similar mechanism in .NET



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)