[jira] [Assigned] (IGNITE-5198) Improve VisorDataCollectorTask

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-5198:


Assignee: Alexey Kuznetsov

> Improve VisorDataCollectorTask
> --
>
> Key: IGNITE-5198
> URL: https://issues.apache.org/jira/browse/IGNITE-5198
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
>
> VisorDataCollectorTask collect data about grid and caches, but its 
> implementation is not flexible.
> Possible improvements: 
> # Add some flags that will allow to "turn off" some collector logic, for 
> example - do not collect caches or IGFS metrics.
> # May be move IGFS metrics (as they may be slow) to separate task.
> # Optimize internal structures (for example, caches partitions, use bit set 
> or smth.)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5198) Improve VisorDataCollectorTask

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5198:


 Summary: Improve VisorDataCollectorTask
 Key: IGNITE-5198
 URL: https://issues.apache.org/jira/browse/IGNITE-5198
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 2.0
Reporter: Alexey Kuznetsov
 Fix For: 2.1


VisorDataCollectorTask collect data about grid and caches, but its 
implementation is not flexible.
Possible improvements: 
# Add some flags that will allow to "turn off" some collector logic, for 
example - do not collect caches or IGFS metrics.
# May be move IGFS metrics (as they may be slow) to separate task.
# Optimize internal structures (for example, caches partitions, use bit set or 
smth.)




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5082) Redesign base template

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-5082:
--

[~anovikov], please review the fixes.

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Ilya Borisov
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5082) Redesign base template

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-5082:


Assignee: Andrey Novikov  (was: Ilya Borisov)

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4974) Document .NET dynamically registered classes

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-4974.
---

Reviewed.

> Document .NET dynamically registered classes
> 
>
> Key: IGNITE-4974
> URL: https://issues.apache.org/jira/browse/IGNITE-4974
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.0
>
>
> [~ptupitsyn], please document modifications related to .NET dynamically 
> registered classes (IGNITE-2703) and assign the ticket on me and Prachi for 
> final polishment.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5153) CPP: BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5153:
-

Implemented for Decimals, Strings and Arrays. Added tests. Implementation for 
Collections is in progress.

> CPP: BinaryMarshaller should write ints in "varint" encoding where it makes 
> sense
> -
>
> Key: IGNITE-5153
> URL: https://issues.apache.org/jira/browse/IGNITE-5153
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vyacheslav Daradur
>Assignee: Igor Sapego
> Fix For: 2.1
>
>
> Need to implement IGNITE-5097



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4973) Document .NET Plugin System

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-4973.
---

Reviewed.

> Document .NET Plugin System
> ---
>
> Key: IGNITE-4973
> URL: https://issues.apache.org/jira/browse/IGNITE-4973
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> [~ptupitsyn], please document .NET plugin system (IGNITE-2940) with the usage 
> hints whenever applicable.
> As usual, assign on me and Prachi for the final review.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5052) Implement CREATE/DROP TABLE parsing and execution

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-5052:
-

[~vozerov]
1, 2, 3, 6 - fixed.
4, 5 - will most likely fix tomorrow.
7 - to me, PARSING should be thrown only from parser which is reasonably 
agnostic to caches, etc. So I'd leave these alone.
8 - we need this no more and no less than for any other SQL statement.
9 - yes.

> Implement CREATE/DROP TABLE parsing and execution
> -
>
> Key: IGNITE-5052
> URL: https://issues.apache.org/jira/browse/IGNITE-5052
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.1
>
>
> Convert SQL string to relevant Igntie command. This could be:
> - {{createCache}}
> - {{getOrCreateCache}} (for {{IF NOT EXISTS}} case)
> - {{destroyCache}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5197) Introduce AFFINITY KEY keywords and Ignite SQL mode to H2

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-5197:
---

 Summary: Introduce AFFINITY KEY keywords and Ignite SQL mode to H2
 Key: IGNITE-5197
 URL: https://issues.apache.org/jira/browse/IGNITE-5197
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5196) Concurrent modification in .GridDiscoveryManager.nodeCaches

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-5196:


Assignee: Semen Boikov  (was: Yakov Zhdanov)

> Concurrent modification in .GridDiscoveryManager.nodeCaches
> ---
>
> Key: IGNITE-5196
> URL: https://issues.apache.org/jira/browse/IGNITE-5196
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Semen Boikov
> Fix For: 2.1
>
>
> {noformat}
> ./grid149.tar.gz:org.apache.ignite.IgniteCheckedException: null
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7281) 
> ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:171)
>  [ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_121]
> ./grid149.tar.gz:   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_121]
> ./grid149.tar.gz:   at java.lang.Thread.run(Thread.java:745) 
> [na:1.8.0_121]
> ./grid149.tar.gz:Caused by: java.util.ConcurrentModificationException: null
> ./grid149.tar.gz:   at 
> java.util.HashMap$HashIterator.nextNode(HashMap.java:1437) ~[na:1.8.0_121]
> ./grid149.tar.gz:   at 
> java.util.HashMap$EntryIterator.next(HashMap.java:1471) ~[na:1.8.0_121]
> ./grid149.tar.gz:   at 
> java.util.HashMap$EntryIterator.next(HashMap.java:1469) ~[na:1.8.0_121]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.nodeCaches(GridDiscoveryManager.java:1733)
>  ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.createNodeBean(GridTopologyCommandHandler.java:219)
>  ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHO
> T]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:109)
>  ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:265)
>  ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:88)
>  ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:154)
>  [ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   ... 4 common frames omitted
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5196) Concurrent modification in .GridDiscoveryManager.nodeCaches

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-5196:
-

 Summary: Concurrent modification in 
.GridDiscoveryManager.nodeCaches
 Key: IGNITE-5196
 URL: https://issues.apache.org/jira/browse/IGNITE-5196
 Project: Ignite
  Issue Type: Bug
Reporter: Yakov Zhdanov
Assignee: Yakov Zhdanov
 Fix For: 2.1


{noformat}
./grid149.tar.gz:org.apache.ignite.IgniteCheckedException: null
./grid149.tar.gz:   at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7281) 
~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   at 
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:171)
 [ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_121]
./grid149.tar.gz:   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_121]
./grid149.tar.gz:   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
./grid149.tar.gz:Caused by: java.util.ConcurrentModificationException: null
./grid149.tar.gz:   at 
java.util.HashMap$HashIterator.nextNode(HashMap.java:1437) ~[na:1.8.0_121]
./grid149.tar.gz:   at 
java.util.HashMap$EntryIterator.next(HashMap.java:1471) ~[na:1.8.0_121]
./grid149.tar.gz:   at 
java.util.HashMap$EntryIterator.next(HashMap.java:1469) ~[na:1.8.0_121]
./grid149.tar.gz:   at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.nodeCaches(GridDiscoveryManager.java:1733)
 ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   at 
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.createNodeBean(GridTopologyCommandHandler.java:219)
 ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHO
T]
./grid149.tar.gz:   at 
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:109)
 ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:265)
 ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:88)
 ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   at 
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:154)
 [ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
./grid149.tar.gz:   ... 4 common frames omitted
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4971) Document how heartbeats are issued across the cluster ring

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-4971.
---

Reviewed.

> Document how heartbeats are issued across the cluster ring
> --
>
> Key: IGNITE-4971
> URL: https://issues.apache.org/jira/browse/IGNITE-4971
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> {{TcpDiscoverySpi.heartbeatsFrequency}} was removed from the API 
> (IGNITE-4799). Let's update TcpDiscoverySpi page and explain how the 
> heartbeats are issued across the cluster ring.
> https://dash.readme.io/project/apacheignite/v1.9/docs/cluster-configuration-20



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5097:
-

[~daradurvs], what about {{Date}} and {{Timestamp}} types? It seems like about 
2 bytes can be saved for them if we'll use varint64 for them. 

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4205:
---

I created new [GitHub pr|https://github.com/apache/ignite/pull/1925], with 
changes and a test for the scenario described in the ticket

> CassandraCacheStore should start IgniteThread threads in loadCache() method
> ---
>
> Key: IGNITE-4205
> URL: https://issues.apache.org/jira/browse/IGNITE-4205
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Konstantin Dudkov
>
> {{CassandraCacheStore.loadCache()}} method starts a generic thread pool for 
> parallel data load. Threads in this thread pool can't deserialize Ignite 
> internal objects (e.g. {{IgniteKernal}}) which can cause unexpected behavior. 
> Here is one of the scenarios:
> * There is column in Cassandra which stores an object as BLOB using 
> {{JavaSerializer}}.
> * {{CacheConfiguration.storeKeepBinary}} is {{true}}.
> * When an object is saved, it's passed to the store as an instance of 
> {{BinaryObject}} which is converted to a byte array and saved in Cassandra.
> * When the same object is loaded in {{loadCache}}, the store takes the byte 
> array and tries to convert it to {{BinaryObject}}. But it can't because this 
> implies calling {{IgnitionEx.localIgnite()}} from non-Ignite thread.
> To fix this we need to provide a thread factory that will create instances of 
> {{IgniteThread}} and use it in the pool that loads the data.
> Most likely the same issue exists in {{CacheAbstractJdbcStore}}.
> And in general, any threads created by Ignite internals should be 
> {{IgniteThread}}-s. This should be revisited.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5195) DataStreamer can fails if non-data node enter\leave the grid.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5195:
-
Attachment: DataStreamerFailure.java

> DataStreamer can fails if non-data node enter\leave the grid.
> -
>
> Key: IGNITE-5195
> URL: https://issues.apache.org/jira/browse/IGNITE-5195
> Project: Ignite
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
> Fix For: 2.1
>
> Attachments: DataStreamerFailure.java
>
>
> DataStreamer failed with "too many remaps" message even if non-data node 
> enter\leave topology.
> PFA repro attached. 
> Seems, we should ignore topology changes when non-data node enter\leave the 
> grid. 
> And also we need to sure that remapping doesn't occurs when there is no data 
> nodes in grid any more, as remapping make no sense and more suitable message 
> should be logged.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5195) DataStreamer can fails if non-data node enter\leave the grid.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5195:
-
Description: 
DataStreamer failed with "too many remaps" message even if non-data node 
enter\leave topology.
PFA repro attached. 

Seems, we should ignore topology changes when non-data node enter\leave the 
grid. 

And also we need to sure that remapping doesn't occurs when there is no data 
nodes in grid any more, as remapping make no sense and more suitable message 
should be logged.

> DataStreamer can fails if non-data node enter\leave the grid.
> -
>
> Key: IGNITE-5195
> URL: https://issues.apache.org/jira/browse/IGNITE-5195
> Project: Ignite
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
> Fix For: 2.1
>
> Attachments: DataStreamerFailure.java
>
>
> DataStreamer failed with "too many remaps" message even if non-data node 
> enter\leave topology.
> PFA repro attached. 
> Seems, we should ignore topology changes when non-data node enter\leave the 
> grid. 
> And also we need to sure that remapping doesn't occurs when there is no data 
> nodes in grid any more, as remapping make no sense and more suitable message 
> should be logged.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5195) DataStreamer can fails if non-data node enter\leave the grid.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5195:


 Summary: DataStreamer can fails if non-data node enter\leave the 
grid.
 Key: IGNITE-5195
 URL: https://issues.apache.org/jira/browse/IGNITE-5195
 Project: Ignite
  Issue Type: Bug
  Components: streaming
Affects Versions: 1.8
Reporter: Andrew Mashenkov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4575) Implement in Ignite wrapper for enums based on H2 user value type

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-4575:


[~vozerov], I have applied the comments you provided. Please, take a look again.

> Implement in Ignite wrapper for enums based on H2 user value type
> -
>
> Key: IGNITE-4575
> URL: https://issues.apache.org/jira/browse/IGNITE-4575
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3771) JDBC driver tries to initialize the cache store

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-3771:
-

[~vozerov], agree.

> JDBC driver tries to initialize the cache store
> ---
>
> Key: IGNITE-3771
> URL: https://issues.apache.org/jira/browse/IGNITE-3771
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
> Fix For: 2.1
>
>
> Since JDBC driver is read-only, the cache store doesn't make sense for it, 
> but having it in cache configuration leads to issues like described in [1]. 
> We should implement a mechanism to ignore such things on JDBC driver 
> (probably use daemon node?).
> [1] 
> http://apache-ignite-users.70518.x6.nabble.com/DiscoveryMetricsProvider-implementation-td7312.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5054) Support SQL schema sharing between different caches

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5054:


Github user devozerov closed the pull request at:

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


> Support SQL schema sharing between different caches
> ---
>
> Key: IGNITE-5054
> URL: https://issues.apache.org/jira/browse/IGNITE-5054
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> Current every cache "lives" in it's own schema. We need to allow different 
> caches to optionally share the same schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5194) .NET: TryGetIgnite does not work with AutoGenerateIgniteInstanceName

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5194:
---
Description: 
{{Ignition.GetIgnite()}} has been reworked to return instance with any name if 
there is only one present. This is needed to work nicely with 
{{AutoGenerateIgniteInstanceName}}.

{{TryGetIgnite()}}, however, was not updated.

  was:
`Ignition.GetIgnite()` has been reworked to return instance with any name if 
there is only one present. This is needed to work nicely with 
`AutoGenerateIgniteInstanceName`.

`TryGetIgnite()`, however, was not updated.


> .NET: TryGetIgnite does not work with AutoGenerateIgniteInstanceName
> 
>
> Key: IGNITE-5194
> URL: https://issues.apache.org/jira/browse/IGNITE-5194
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> {{Ignition.GetIgnite()}} has been reworked to return instance with any name 
> if there is only one present. This is needed to work nicely with 
> {{AutoGenerateIgniteInstanceName}}.
> {{TryGetIgnite()}}, however, was not updated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5194) .NET: TryGetIgnite does not work with AutoGenerateIgniteInstanceName

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5194:
--

 Summary: .NET: TryGetIgnite does not work with 
AutoGenerateIgniteInstanceName
 Key: IGNITE-5194
 URL: https://issues.apache.org/jira/browse/IGNITE-5194
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
 Fix For: 2.1


`Ignition.GetIgnite()` has been reworked to return instance with any name if 
there is only one present. This is needed to work nicely with 
`AutoGenerateIgniteInstanceName`.

`TryGetIgnite()`, however, was not updated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5194) .NET: TryGetIgnite does not work with AutoGenerateIgniteInstanceName

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-5194:
--

Assignee: Pavel Tupitsyn

> .NET: TryGetIgnite does not work with AutoGenerateIgniteInstanceName
> 
>
> Key: IGNITE-5194
> URL: https://issues.apache.org/jira/browse/IGNITE-5194
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> `Ignition.GetIgnite()` has been reworked to return instance with any name if 
> there is only one present. This is needed to work nicely with 
> `AutoGenerateIgniteInstanceName`.
> `TryGetIgnite()`, however, was not updated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5193) Hadoop: Ignite node fails to start if some , but not all HADOOP_XXX_HOME variables are set.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky updated IGNITE-5193:

Description: 
Ignite node fails to start if some , but not all 3 HADOOP_XXX_HOME variables 
are set (see trace below). This is caused by the following gap in Ignite logic: 
{{org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils#exists , 
#isDirectory , #isReadable}} return {{true}} for empty String argument. For the 
unset location variables the value is empty String, but 
{{org.apache.ignite.internal.processors.hadoop.HadoopLocations#xExists}} 
gets {{true}}, so the location considered to be valid. This is the cause of the 
problem.

{code}
[06:09:42] Security status [authentication=off, tls/ssl=off]
[06:17:23,822][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
java.lang.RuntimeException: class org.apache.ignite.IgniteCheckedException: 
Failed to resolve Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:422)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.(HadoopClassLoader.java:134)
at 
org.apache.ignite.internal.processors.hadoop.HadoopHelperImpl.commonClassLoader(HadoopHelperImpl.java:78)
at 
org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:254)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.(IgfsImpl.java:186)
at 
org.apache.ignite.internal.processors.igfs.IgfsContext.(IgfsContext.java:101)
at 
org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:128)
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1638)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:900)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1602)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:964)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:850)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:749)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:619)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve 
Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.hadoopUrls(HadoopClassLoader.java:456)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:419)
... 18 more
Caused by: java.io.IOException: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils$SearchDirectory.files(HadoopClasspathUtils.java:344)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils.classpathForClassLoader(HadoopClasspathUtils.java:68)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.hadoopUrls(HadoopClassLoader.java:453)
... 19 more
{code}

  was:
Ignite node fails to start if some , but not all 3 HADOOP_XXX_HOME variables 
are set (see trace below). This is caused by the following gap in Ignite logic: 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils#exists , 
#isDirectory , #isReadable return {true} for empty String argument. For the 
unset location variables the value is empty String, but 
{org.apache.ignite.internal.processors.hadoop.HadoopLocations#xExists} gets 
{true}, so the location considered to be valid. This is the cause of the 
problem.

{code}
[06:09:42] Security status [authentication=off, tls/ssl=off]
[06:17:23,822][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
java.lang.RuntimeException: class org.apache.ignite.IgniteCheckedException: 
Failed to resolve Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:422)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.(HadoopClassLoader.java:134)
at 
org.apache.ignite.internal.processors.hadoop.HadoopHelperImpl.commonClassLoader(HadoopHelperImpl.java:78)
at 

[jira] [Updated] (IGNITE-5193) Hadoop: Ignite node fails to start if some , but not all HADOOP_XXX_HOME variables are set.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky updated IGNITE-5193:

Description: 
Ignite node fails to start if some , but not all 3 HADOOP_XXX_HOME variables 
are set (see trace below). This is caused by the following gap in Ignite logic: 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils#exists , 
#isDirectory , #isReadable return {true} for empty String argument. For the 
unset location variables the value is empty String, but 
{org.apache.ignite.internal.processors.hadoop.HadoopLocations#xExists} gets 
{true}, so the location considered to be valid. This is the cause of the 
problem.

{code}
[06:09:42] Security status [authentication=off, tls/ssl=off]
[06:17:23,822][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
java.lang.RuntimeException: class org.apache.ignite.IgniteCheckedException: 
Failed to resolve Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:422)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.(HadoopClassLoader.java:134)
at 
org.apache.ignite.internal.processors.hadoop.HadoopHelperImpl.commonClassLoader(HadoopHelperImpl.java:78)
at 
org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:254)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.(IgfsImpl.java:186)
at 
org.apache.ignite.internal.processors.igfs.IgfsContext.(IgfsContext.java:101)
at 
org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:128)
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1638)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:900)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1602)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:964)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:850)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:749)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:619)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve 
Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.hadoopUrls(HadoopClassLoader.java:456)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:419)
... 18 more
Caused by: java.io.IOException: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils$SearchDirectory.files(HadoopClasspathUtils.java:344)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils.classpathForClassLoader(HadoopClasspathUtils.java:68)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.hadoopUrls(HadoopClassLoader.java:453)
... 19 more
{code}

  was:
Ignite node fails to start if some , but not all 3 HADOOP_XXX_HOME variables 
are set (see trace below). This is caused by the following gap in Ignite logic: 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils#exists 
returns {true} for empty String argument. For the unset location variables the 
value is empty string, but 
{org.apache.ignite.internal.processors.hadoop.HadoopLocations#xExists} gets 
{true}. This is the cause of the problem.

{code}
[06:09:42] Security status [authentication=off, tls/ssl=off]
[06:17:23,822][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
java.lang.RuntimeException: class org.apache.ignite.IgniteCheckedException: 
Failed to resolve Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:422)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.(HadoopClassLoader.java:134)
at 
org.apache.ignite.internal.processors.hadoop.HadoopHelperImpl.commonClassLoader(HadoopHelperImpl.java:78)
at 
org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:254)
at 

[jira] [Created] (IGNITE-5193) Hadoop: Ignite node fails to start if some , but not all HADOOP_XXX_HOME variables are set.

[Ivan Veselovsky (JIRA)]

Ivan Veselovsky created IGNITE-5193:
---

 Summary: Hadoop: Ignite node fails to start if some , but not all 
HADOOP_XXX_HOME variables are set.
 Key: IGNITE-5193
 URL: https://issues.apache.org/jira/browse/IGNITE-5193
 Project: Ignite
  Issue Type: Bug
  Components: hadoop
Affects Versions: 1.8
Reporter: Ivan Veselovsky
Assignee: Ivan Veselovsky
 Fix For: 2.1


Ignite node fails to start if some , but not all 3 HADOOP_XXX_HOME variables 
are set (see trace below). This is caused by the following gap in Ignite logic: 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils#exists 
returns {true} for empty String argument. For the unset location variables the 
value is empty string, but 
{org.apache.ignite.internal.processors.hadoop.HadoopLocations#xExists} gets 
{true}. This is the cause of the problem.

{code}
[06:09:42] Security status [authentication=off, tls/ssl=off]
[06:17:23,822][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
java.lang.RuntimeException: class org.apache.ignite.IgniteCheckedException: 
Failed to resolve Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:422)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.(HadoopClassLoader.java:134)
at 
org.apache.ignite.internal.processors.hadoop.HadoopHelperImpl.commonClassLoader(HadoopHelperImpl.java:78)
at 
org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:254)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.(IgfsImpl.java:186)
at 
org.apache.ignite.internal.processors.igfs.IgfsContext.(IgfsContext.java:101)
at 
org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:128)
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1638)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:900)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1602)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:964)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:850)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:749)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:619)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve 
Hadoop JAR locations: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.hadoopUrls(HadoopClassLoader.java:456)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.addHadoopUrls(HadoopClassLoader.java:419)
... 18 more
Caused by: java.io.IOException: Failed to get directory files [dir=]
at 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils$SearchDirectory.files(HadoopClasspathUtils.java:344)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClasspathUtils.classpathForClassLoader(HadoopClasspathUtils.java:68)
at 
org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.hadoopUrls(HadoopClassLoader.java:453)
... 19 more
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4425) .NET: Support "ICollection.Contains" in LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4425:
---
Fix Version/s: (was: 2.0)
   1.9

> .NET: Support "ICollection.Contains" in LINQ
> 
>
> Key: IGNITE-4425
> URL: https://issues.apache.org/jira/browse/IGNITE-4425
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .NET, LINQ
> Fix For: 1.9
>
>
> SQL supports IN queries
> https://apacheignite.readme.io/docs/sql-performance-and-debugging#sql-performance-and-usability-considerations
> Example SQL:
> {code}
> new SqlFieldsQuery("select p.name from Person p where id in (?, ?)", 1, 3);
> {code}
> Add support in LINQ like this:
> {code}
> persons.AsCacheQueryable().Where(x => new[] {1,3}.Contains(x.Value.Id))
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4359) .NET: Support DateTime properties in LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4359:
---
Fix Version/s: (was: 2.0)
   1.9

> .NET: Support DateTime properties in LINQ
> -
>
> Key: IGNITE-4359
> URL: https://issues.apache.org/jira/browse/IGNITE-4359
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.9
>
>
> Support {{DateTime}} properties such as Year, Month, Day in LINQ. See how 
> {{String.Length}} property is supported in {{MethodVisitor}}.
> See http://www.h2database.com/html/functions.html for supported SQL functions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5190) ArrayIndexOutOfBoundsException in GridMergeIndexSorted

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5190:
--

I've attach a repro. Seems, join with subquery is buggy.

> ArrayIndexOutOfBoundsException in GridMergeIndexSorted
> --
>
> Key: IGNITE-5190
> URL: https://issues.apache.org/jira/browse/IGNITE-5190
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
> Fix For: 2.1
>
> Attachments: join-on-subquery-exception.txt, 
> JoinWithSubQueryFails.java
>
>
> PFA stacktrace with query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5190) ArrayIndexOutOfBoundsException in GridMergeIndexSorted

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5190:
-
Attachment: JoinWithSubQueryFails.java

> ArrayIndexOutOfBoundsException in GridMergeIndexSorted
> --
>
> Key: IGNITE-5190
> URL: https://issues.apache.org/jira/browse/IGNITE-5190
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
> Fix For: 2.1
>
> Attachments: join-on-subquery-exception.txt, 
> JoinWithSubQueryFails.java
>
>
> PFA stacktrace with query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov reassigned IGNITE-4205:
-

Assignee: Konstantin Dudkov  (was: Igor Rudyak)

> CassandraCacheStore should start IgniteThread threads in loadCache() method
> ---
>
> Key: IGNITE-4205
> URL: https://issues.apache.org/jira/browse/IGNITE-4205
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Konstantin Dudkov
>
> {{CassandraCacheStore.loadCache()}} method starts a generic thread pool for 
> parallel data load. Threads in this thread pool can't deserialize Ignite 
> internal objects (e.g. {{IgniteKernal}}) which can cause unexpected behavior. 
> Here is one of the scenarios:
> * There is column in Cassandra which stores an object as BLOB using 
> {{JavaSerializer}}.
> * {{CacheConfiguration.storeKeepBinary}} is {{true}}.
> * When an object is saved, it's passed to the store as an instance of 
> {{BinaryObject}} which is converted to a byte array and saved in Cassandra.
> * When the same object is loaded in {{loadCache}}, the store takes the byte 
> array and tries to convert it to {{BinaryObject}}. But it can't because this 
> implies calling {{IgnitionEx.localIgnite()}} from non-Ignite thread.
> To fix this we need to provide a thread factory that will create instances of 
> {{IgniteThread}} and use it in the pool that loads the data.
> Most likely the same issue exists in {{CacheAbstractJdbcStore}}.
> And in general, any threads created by Ignite internals should be 
> {{IgniteThread}}-s. This should be revisited.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4205:
---

Due to no activity I'll try to complete ticket.

> CassandraCacheStore should start IgniteThread threads in loadCache() method
> ---
>
> Key: IGNITE-4205
> URL: https://issues.apache.org/jira/browse/IGNITE-4205
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Igor Rudyak
>
> {{CassandraCacheStore.loadCache()}} method starts a generic thread pool for 
> parallel data load. Threads in this thread pool can't deserialize Ignite 
> internal objects (e.g. {{IgniteKernal}}) which can cause unexpected behavior. 
> Here is one of the scenarios:
> * There is column in Cassandra which stores an object as BLOB using 
> {{JavaSerializer}}.
> * {{CacheConfiguration.storeKeepBinary}} is {{true}}.
> * When an object is saved, it's passed to the store as an instance of 
> {{BinaryObject}} which is converted to a byte array and saved in Cassandra.
> * When the same object is loaded in {{loadCache}}, the store takes the byte 
> array and tries to convert it to {{BinaryObject}}. But it can't because this 
> implies calling {{IgnitionEx.localIgnite()}} from non-Ignite thread.
> To fix this we need to provide a thread factory that will create instances of 
> {{IgniteThread}} and use it in the pool that loads the data.
> Most likely the same issue exists in {{CacheAbstractJdbcStore}}.
> And in general, any threads created by Ignite internals should be 
> {{IgniteThread}}-s. This should be revisited.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5192) NPE at CacheDataStoreImpl.canUpdateOldRow during load test

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova updated IGNITE-5192:

Attachment: ignite-base-load-config.xml
run-load.xml
run-load.properties

> NPE at CacheDataStoreImpl.canUpdateOldRow during load test
> --
>
> Key: IGNITE-5192
> URL: https://issues.apache.org/jira/browse/IGNITE-5192
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
> Attachments: ignite-base-load-config.xml, run-load.properties, 
> run-load.xml
>
>
> NPE occurs during load test:
> {noformat}
> [14:05:37,145][ERROR][sys-stripe-5-#6%null%][GridDhtTxLocal] Heuristic 
> transaction failure.
> class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Failed to locally write to cache (all transaction entries will be 
> invalidated, however there was a window when entries for this transaction 
> were visible to
> others) ...
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:829)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:772)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:580)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:466)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:514)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:841)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:720)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:676)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:95)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:153)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:151)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:863)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:386)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:100)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:253)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
> at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Runtime failure on search 
> row: 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$SearchRow@55f39849
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.invoke(BPlusTree.java:1615)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:925)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:326)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3241)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerSet(GridCacheMapEntry.java:992)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:663)
> ... 21 more
> Caused by: java.lang.NullPointerException
> at 
> 

[jira] [Created] (IGNITE-5192) NPE at CacheDataStoreImpl.canUpdateOldRow during load test

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-5192:
---

 Summary: NPE at CacheDataStoreImpl.canUpdateOldRow during load test
 Key: IGNITE-5192
 URL: https://issues.apache.org/jira/browse/IGNITE-5192
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Ksenia Rybakova


NPE occurs during load test:
{noformat}
[14:05:37,145][ERROR][sys-stripe-5-#6%null%][GridDhtTxLocal] Heuristic 
transaction failure.
class 
org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
Failed to locally write to cache (all transaction entries will be invalidated, 
however there was a window when entries for this transaction were visible to
others) ...
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:829)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:772)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:580)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:466)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:514)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:841)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:720)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:676)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:95)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:153)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:151)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:863)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:386)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:100)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:253)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Runtime failure on search 
row: 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$SearchRow@55f39849
at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.invoke(BPlusTree.java:1615)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:925)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:326)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3241)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerSet(GridCacheMapEntry.java:992)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:663)
... 21 more
Caused by: java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.canUpdateOldRow(IgniteCacheOffheapManagerImpl.java:913)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.createRow(IgniteCacheOffheapManagerImpl.java:970)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:3937)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:3895)
at 

[jira] [Commented] (IGNITE-5151) Add some warning when offheap eviction occurs

[Ivan Rakov (JIRA)]

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

Ivan Rakov commented on IGNITE-5151:


https://github.com/apache/ignite/pull/1921
This fix is ok, approved.

> Add some warning when offheap eviction occurs
> -
>
> Key: IGNITE-5151
> URL: https://issues.apache.org/jira/browse/IGNITE-5151
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
>Assignee: Wuwei Lin
>
> Currently if offheap eviction occurs we are silently losing data. It whould 
> be helpful to have some warning in log as it's done for onheap eviction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4360) .NET: LINQ documentation

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4360:
--

Assignee: Pavel Tupitsyn

> .NET: LINQ documentation
> 
>
> Key: IGNITE-4360
> URL: https://issues.apache.org/jira/browse/IGNITE-4360
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.0
>
>
> Document thoroughly what is supported in LINQ, especially all the methods 
> from MethodVisitor, since this can be non obvious (like 
> DateTime.ToString("y")).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4420) .NET: Improve documentation for query configuration combined with reflective serialization

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4420:
--

Assignee: Pavel Tupitsyn

> .NET: Improve documentation for query configuration combined with reflective 
> serialization
> --
>
> Key: IGNITE-4420
> URL: https://issues.apache.org/jira/browse/IGNITE-4420
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> With automatic properties the situation is straightforward: mark property 
> with [QuerySqlField].
> With manual backing fields there may be some confusion, because reflective 
> serializer operates on fields, and field names start with "_" in default 
> naming convention. 
> Make sure all situations are documented properly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5189) Unexpected error occurs when node left topology.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5189:
-
Description: 
Error occurs sporadically. Usually, it happens when one of server nodes left 
topology and client can't connect to other servers via communication.

Using preferIPv4 option solve the issue.
Also, possibly the fact that it seems ok on ignite-1.6 version, may be helpful.

ERROR 2017-05-10T09:57:58,282 - 
de.uplanet.test.integration.RemoteTestServiceBean[pool-4-thread-1]
Failed to send message to remote node: TcpDiscoveryNode 
[id=ef626cb1-3880-418e-a9d1-68fd692771fd, addrs=[0:0:0:0:0:0:0:1%lo, 10.0.2.15, 
127.0.0.1, 172.17.0.1], sockAddrs=[/172.17.0.1:0, 0:0:0:0:0:0:0:1%lo:0, 
/127.0.0.1:0, /10.0.2.15:0], discPort=0, order=3, intOrder=3, 
lastExchangeTime=1494410235152, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, 
isClient=true]
org.apache.ignite.spi.IgniteSpiException: Failed to send message to remote 
node: TcpDiscoveryNode [id=ef626cb1-3880-418e-a9d1-68fd692771fd, 
addrs=[0:0:0:0:0:0:0:1%lo, 10.0.2.15, 127.0.0.1, 172.17.0.1], 
sockAddrs=[/172.17.0.1:0, 0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, /10.0.2.15:0], 
discPort=0, order=3, intOrder=3, lastExchangeTime=1494410235152, loc=false, 
ver=2.0.0#20170430-sha1:d4eef3c6, isClient=true]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2483)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2419)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1329)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1698)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessageToGridTopic(GridIoManager.java:1473)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendUserMessage(GridIoManager.java:1588)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.IgniteMessagingImpl.sendOrdered(IgniteMessagingImpl.java:165)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
de.uplanet.lucy.server.distributed.cloud.datagrid.ignite.IgniteGridTopic.publish(IgniteGridTopic.java:58)
 ~[update/:?]
at 
de.uplanet.test.integration.RemoteTestServiceBean.lambda$3(RemoteTestServiceBean.java:123)
 ~[update/:?]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[?:1.8.0_92]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[?:1.8.0_92]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[?:1.8.0_92]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[?:1.8.0_92]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_92]
Caused by: org.apache.ignite.IgniteCheckedException: 
java.lang.NullPointerException
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7242) 
~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2630)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2455)
 ~[ignite-core-2.0.0.jar:2.0.0]
... 13 more
Caused by: java.util.concurrent.ExecutionException: 
java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
~[?:1.8.0_92]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) 
~[?:1.8.0_92]
at 
org.apache.ignite.internal.util.IgniteUtils.filterReachable(IgniteUtils.java:1895)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2891)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2702)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 

[jira] [Commented] (IGNITE-5054) Support SQL schema sharing between different caches

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5054:


GitHub user devozerov opened a pull request:

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

IGNITE-5054



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

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

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

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


commit 26229676f70dbc8fadcd449b5745ca644078ac67
Author: devozerov 
Date:   2017-05-10T10:40:02Z

Minor refactoring.

commit bbeedbfa6e2747d1647f80d009ca8331dcabc296
Author: devozerov 
Date:   2017-05-10T10:48:26Z

Minor refactoring (2).

commit ae1578e0b8e7c14c73e8cae901afc5bfa70b3ccf
Author: devozerov 
Date:   2017-05-10T10:56:33Z

Refactoring (3).

commit 116f5a2dc604b3051bda4068d6feb9022dac1dbe
Author: devozerov 
Date:   2017-05-10T11:25:50Z

WIP.

commit 1279f8b4b6fe94a9d3e197a66789804dfc37883f
Author: devozerov 
Date:   2017-05-10T11:53:00Z

WIP.




> Support SQL schema sharing between different caches
> ---
>
> Key: IGNITE-5054
> URL: https://issues.apache.org/jira/browse/IGNITE-5054
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> Current every cache "lives" in it's own schema. We need to allow different 
> caches to optionally share the same schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-5163:


Assignee: Taras Ledkov  (was: Igor Sapego)

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5185) Web console: Implement configuration of cache memory pagination.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-5185:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Web console: Implement configuration of cache memory pagination.
> 
>
> Key: IGNITE-5185
> URL: https://issues.apache.org/jira/browse/IGNITE-5185
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5190) ArrayIndexOutOfBoundsException in GridMergeIndexSorted

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5190:
-
Description: PFA stacktrace with query.

> ArrayIndexOutOfBoundsException in GridMergeIndexSorted
> --
>
> Key: IGNITE-5190
> URL: https://issues.apache.org/jira/browse/IGNITE-5190
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
> Fix For: 2.1
>
> Attachments: join-on-subquery-exception.txt
>
>
> PFA stacktrace with query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5190) ArrayIndexOutOfBoundsException in GridMergeIndexSorted

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5190:
-
Attachment: join-on-subquery-exception.txt

> ArrayIndexOutOfBoundsException in GridMergeIndexSorted
> --
>
> Key: IGNITE-5190
> URL: https://issues.apache.org/jira/browse/IGNITE-5190
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
> Fix For: 2.1
>
> Attachments: join-on-subquery-exception.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5190) ArrayIndexOutOfBoundsException in GridMergeIndexSorted

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5190:


 Summary: ArrayIndexOutOfBoundsException in GridMergeIndexSorted
 Key: IGNITE-5190
 URL: https://issues.apache.org/jira/browse/IGNITE-5190
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.0
Reporter: Andrew Mashenkov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5189) Unexpected error occurs when node left topology.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5189:
-
Affects Version/s: 1.8
   1.9
   2.0
 Priority: Minor  (was: Major)
  Description: 
Error occurs sporadically. Usually, it happens when one of server nodes left 
topology and client can't connect to other servers via communication.

Using preferIPv4 option solve the issue.

ERROR 2017-05-10T09:57:58,282 - 
de.uplanet.test.integration.RemoteTestServiceBean[pool-4-thread-1]
Failed to send message to remote node: TcpDiscoveryNode 
[id=ef626cb1-3880-418e-a9d1-68fd692771fd, addrs=[0:0:0:0:0:0:0:1%lo, 10.0.2.15, 
127.0.0.1, 172.17.0.1], sockAddrs=[/172.17.0.1:0, 0:0:0:0:0:0:0:1%lo:0, 
/127.0.0.1:0, /10.0.2.15:0], discPort=0, order=3, intOrder=3, 
lastExchangeTime=1494410235152, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, 
isClient=true]
org.apache.ignite.spi.IgniteSpiException: Failed to send message to remote 
node: TcpDiscoveryNode [id=ef626cb1-3880-418e-a9d1-68fd692771fd, 
addrs=[0:0:0:0:0:0:0:1%lo, 10.0.2.15, 127.0.0.1, 172.17.0.1], 
sockAddrs=[/172.17.0.1:0, 0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, /10.0.2.15:0], 
discPort=0, order=3, intOrder=3, lastExchangeTime=1494410235152, loc=false, 
ver=2.0.0#20170430-sha1:d4eef3c6, isClient=true]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2483)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2419)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1329)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1698)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessageToGridTopic(GridIoManager.java:1473)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendUserMessage(GridIoManager.java:1588)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.IgniteMessagingImpl.sendOrdered(IgniteMessagingImpl.java:165)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
de.uplanet.lucy.server.distributed.cloud.datagrid.ignite.IgniteGridTopic.publish(IgniteGridTopic.java:58)
 ~[update/:?]
at 
de.uplanet.test.integration.RemoteTestServiceBean.lambda$3(RemoteTestServiceBean.java:123)
 ~[update/:?]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[?:1.8.0_92]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[?:1.8.0_92]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[?:1.8.0_92]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[?:1.8.0_92]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_92]
Caused by: org.apache.ignite.IgniteCheckedException: 
java.lang.NullPointerException
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7242) 
~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2630)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2455)
 ~[ignite-core-2.0.0.jar:2.0.0]
... 13 more
Caused by: java.util.concurrent.ExecutionException: 
java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
~[?:1.8.0_92]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) 
~[?:1.8.0_92]
at 
org.apache.ignite.internal.util.IgniteUtils.filterReachable(IgniteUtils.java:1895)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2891)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2702)
 ~[ignite-core-2.0.0.jar:2.0.0]
at 

[jira] [Created] (IGNITE-5189) Unexpected error

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5189:


 Summary: Unexpected error 
 Key: IGNITE-5189
 URL: https://issues.apache.org/jira/browse/IGNITE-5189
 Project: Ignite
  Issue Type: Bug
Reporter: Andrew Mashenkov






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-5163:
---

Assignee: Igor Sapego  (was: Taras Ledkov)

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Igor Sapego
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5163:
---

Assignee: Taras Ledkov  (was: Vladimir Ozerov)

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5163:
---

Assignee: Vladimir Ozerov  (was: Taras Ledkov)

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5125) Need to improve logging in case of hang

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5125:


GitHub user zstan opened a pull request:

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

IGNITE-5125, improve logging in case of hang while exchange cannot fi…

…nish.

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

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

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

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


commit 5587c33c99c3e40d4efca0068a0508c40f8abc5c
Author: Evgeny Stanilovskiy 
Date:   2017-05-05T12:35:54Z

IGNITE-5125, improve logging in case of hang while exchange cannot finish.




> Need to improve logging in case of hang
> ---
>
> Key: IGNITE-5125
> URL: https://issues.apache.org/jira/browse/IGNITE-5125
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Fix For: 2.1
>
>
> 1. When cache operation hangs on node it is not reported as hanged although 
> partition map exchange cannot finish.
> {noformat}
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0x7fdd260fd7c0> (a 
> org.apache.ignite.internal.util.future.GridEmbeddedFuture)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:964)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1282)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:159)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2356)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2354)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4168)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2354)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2335)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2312)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1379)
> {noformat}
> {noformat}
>   java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0x7fa0698fee50> (a 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:161)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4570)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4544)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1428)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getAtomic(DataStructuresProcessor.java:589)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.sequence(DataStructuresProcessor.java:397)
> {noformat}
> 2. Partition exchnage future dumps objects only limited number of times. I 
> would suggest to switch to mode when we 

[jira] [Assigned] (IGNITE-4597) CPP: Add mechanism to reset arguments for sql queries.

[Wuwei Lin (JIRA)]

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

Wuwei Lin reassigned IGNITE-4597:
-

Assignee: Wuwei Lin

> CPP: Add mechanism to reset arguments for sql queries.
> --
>
> Key: IGNITE-4597
> URL: https://issues.apache.org/jira/browse/IGNITE-4597
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Wuwei Lin
>  Labels: cpp, newbie
>
> Currently, there is method {{AddArgument}} for {{SqlQuery}} and 
> {{SqlFieldsQuery}}, but there is no way to reset arguments for query once 
> they are set. This leads to inconvenience when user want to call the same 
> query with different arguments as they need to re-create exactly the same 
> query but set different arguments for it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5188) Support AFFINITY KEY keyword for CREATE TABLE command

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5188:

Issue Type: Task  (was: Test)

> Support AFFINITY KEY keyword for CREATE TABLE command
> -
>
> Key: IGNITE-5188
> URL: https://issues.apache.org/jira/browse/IGNITE-5188
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5188) Support AFFINITY KEY keyword for CREATE TABLE command

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5188:
---

 Summary: Support AFFINITY KEY keyword for CREATE TABLE command
 Key: IGNITE-5188
 URL: https://issues.apache.org/jira/browse/IGNITE-5188
 Project: Ignite
  Issue Type: Test
  Components: sql
Reporter: Vladimir Ozerov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5187) Dynamic index create/drop tests are flaky

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5187:

Component/s: sql

> Dynamic index create/drop tests are flaky
> -
>
> Key: IGNITE-5187
> URL: https://issues.apache.org/jira/browse/IGNITE-5187
> Project: Ignite
>  Issue Type: Test
>  Components: sql
>Reporter: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.1
>
>
> Currently we rely on {{Thread.sleep}}. Probably we need something more 
> reliable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5187) Dynamic index create/drop tests are flaky

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5187:
---

 Summary: Dynamic index create/drop tests are flaky
 Key: IGNITE-5187
 URL: https://issues.apache.org/jira/browse/IGNITE-5187
 Project: Ignite
  Issue Type: Test
Reporter: Vladimir Ozerov
Priority: Minor
 Fix For: 2.1


Currently we rely on {{Thread.sleep}}. Probably we need something more reliable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5186) Support CREATE/DROP SCHEMA commands

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5186:
---

 Summary: Support CREATE/DROP SCHEMA commands
 Key: IGNITE-5186
 URL: https://issues.apache.org/jira/browse/IGNITE-5186
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5054) Support SQL schema sharing between different caches

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5054:
---

Assignee: Vladimir Ozerov

> Support SQL schema sharing between different caches
> ---
>
> Key: IGNITE-5054
> URL: https://issues.apache.org/jira/browse/IGNITE-5054
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> Current every cache "lives" in it's own schema. We need to allow different 
> caches to optionally share the same schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4994) Restore GridH2TableSelfTest

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4994:

Fix Version/s: (was: 2.1)
   2.2

> Restore GridH2TableSelfTest
> ---
>
> Key: IGNITE-4994
> URL: https://issues.apache.org/jira/browse/IGNITE-4994
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.2
>
>
> Test is broken after recent refactoring due to DDL feature. Need to restore 
> it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5052) Implement CREATE/DROP TABLE parsing and execution

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5052:

Summary: Implement CREATE/DROP TABLE parsing and execution  (was: Implement 
CREATE/DROP table parsing and execution)

> Implement CREATE/DROP TABLE parsing and execution
> -
>
> Key: IGNITE-5052
> URL: https://issues.apache.org/jira/browse/IGNITE-5052
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.1
>
>
> Convert SQL string to relevant Igntie command. This could be:
> - {{createCache}}
> - {{getOrCreateCache}} (for {{IF NOT EXISTS}} case)
> - {{destroyCache}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4715) SQL: FullText index can't be disabled for cache with String values.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4715:

Fix Version/s: (was: 2.1)
   2.2

> SQL: FullText index can't be disabled for cache with String values. 
> 
>
> Key: IGNITE-4715
> URL: https://issues.apache.org/jira/browse/IGNITE-4715
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
>  Labels: newbie
> Fix For: 2.2
>
> Attachments: FullTextIndexTest.java
>
>
> There is no way to use Sorted only index for cache with String values.
> For String fields all works fine. PFA reproducer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4660) Add DML capabilities to legacy JDBC driver

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4660:

Fix Version/s: (was: 2.1)
   2.2

> Add DML capabilities to legacy JDBC driver
> --
>
> Key: IGNITE-4660
> URL: https://issues.apache.org/jira/browse/IGNITE-4660
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Alexander Paschenko
> Fix For: 2.2
>
>
> Legacy Ignite JDBC driver lacks DML capabilities, but it turns out that there 
> still are plenty of its users who need DML too, so we should de-deprecate it 
> and enable updating operations in it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4660) Add DML capabilities to legacy JDBC driver

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4660:

Fix Version/s: (was: 2.2)
   2.1

> Add DML capabilities to legacy JDBC driver
> --
>
> Key: IGNITE-4660
> URL: https://issues.apache.org/jira/browse/IGNITE-4660
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Alexander Paschenko
> Fix For: 2.2
>
>
> Legacy Ignite JDBC driver lacks DML capabilities, but it turns out that there 
> still are plenty of its users who need DML too, so we should de-deprecate it 
> and enable updating operations in it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4726) SQL: benchmark DML operations

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4726:

Fix Version/s: (was: 2.1)
   2.2

> SQL: benchmark DML operations
> -
>
> Key: IGNITE-4726
> URL: https://issues.apache.org/jira/browse/IGNITE-4726
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
> Fix For: 2.2
>
>
> We need to create benchmarks for DML operations similar to our cache 
> benchmarks and compare common cases. Results of cache API benchmarks can be 
> used as baseline for us.
> Preliminray list of benchmarks:
> 1) INSERT + DELETE (vs {{IgniteCache.put}} + {{IgniteCache.remove}})
> 2) Simple MERGE (vs {{IgniteCache.put}})
> 3) Simple UPDATE (vs {{IgniteCache.invoke}})



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4660) Add DML capabilities to legacy JDBC driver

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4660:

Fix Version/s: (was: 2.1)
   2.2

> Add DML capabilities to legacy JDBC driver
> --
>
> Key: IGNITE-4660
> URL: https://issues.apache.org/jira/browse/IGNITE-4660
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Alexander Paschenko
> Fix For: 2.2
>
>
> Legacy Ignite JDBC driver lacks DML capabilities, but it turns out that there 
> still are plenty of its users who need DML too, so we should de-deprecate it 
> and enable updating operations in it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4660) Add DML capabilities to legacy JDBC driver

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4660:

Priority: Minor  (was: Major)

> Add DML capabilities to legacy JDBC driver
> --
>
> Key: IGNITE-4660
> URL: https://issues.apache.org/jira/browse/IGNITE-4660
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Alexander Paschenko
>Priority: Minor
> Fix For: 2.2
>
>
> Legacy Ignite JDBC driver lacks DML capabilities, but it turns out that there 
> still are plenty of its users who need DML too, so we should de-deprecate it 
> and enable updating operations in it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4489) Maintain correct MERGE semantic in DML

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4489:

Fix Version/s: (was: 2.1)
   2.2

> Maintain correct MERGE semantic in DML
> --
>
> Key: IGNITE-4489
> URL: https://issues.apache.org/jira/browse/IGNITE-4489
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.2
>
>
> Currently it's impossible to MERGE object in UPDATE style - i.e. when key is 
> present in cache, unaffected field values should be retained, and instead of 
> building new object we should base it on previous one for given key.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4338) Cross-schema SQL SELECT on partitioned cache fails for no good reason

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4338:
-

[~al.psc], please verify that this is still the case.

> Cross-schema SQL SELECT on partitioned cache fails for no good reason
> -
>
> Key: IGNITE-4338
> URL: https://issues.apache.org/jira/browse/IGNITE-4338
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.1
>
>
> Inspired by IGNITE-4334.
> Suppose we have two caches, one partitioned and one replicated. The following 
> operation fails:
> {code:java}
> ignite.cache("replicated").query(new SqlFieldsQuery("select _key, _val from 
> \"partitioned\".SomeType")).getAll();
> {code}
> Exception is as follows:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Queries running on 
> replicated cache should not contain JOINs with partitioned tables 
> [rCache=replicated, pCache=partitioned]
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.stableDataNodes(GridReduceQueryExecutor.java:432)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:529)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:117)
>   ...
> {noformat}
> The reason is that during query analysis 
> ({{org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#queryTwoStep}})
>  we always deem leftmost cache (the one that the {{query}} method was called 
> on) as participating in the query which is clearly not true in the above 
> example. Then we add to the query the schema that it actually uses (it's the 
> cache named *partitioned* in this case), and resulting two-step query looks 
> as if its SQL contained {{JOIN}} on *partitioned* and *replicated* caches 
> which we don't support for now.
> Will consult Sergi about what to do next. According to Vlad, this should not 
> affect the release in any way and thus won't be fixed in 1.8.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4338) Cross-schema SQL SELECT on partitioned cache fails for no good reason

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4338:

Fix Version/s: (was: 2.2)
   2.1

> Cross-schema SQL SELECT on partitioned cache fails for no good reason
> -
>
> Key: IGNITE-4338
> URL: https://issues.apache.org/jira/browse/IGNITE-4338
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.1
>
>
> Inspired by IGNITE-4334.
> Suppose we have two caches, one partitioned and one replicated. The following 
> operation fails:
> {code:java}
> ignite.cache("replicated").query(new SqlFieldsQuery("select _key, _val from 
> \"partitioned\".SomeType")).getAll();
> {code}
> Exception is as follows:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Queries running on 
> replicated cache should not contain JOINs with partitioned tables 
> [rCache=replicated, pCache=partitioned]
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.stableDataNodes(GridReduceQueryExecutor.java:432)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:529)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:117)
>   ...
> {noformat}
> The reason is that during query analysis 
> ({{org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#queryTwoStep}})
>  we always deem leftmost cache (the one that the {{query}} method was called 
> on) as participating in the query which is clearly not true in the above 
> example. Then we add to the query the schema that it actually uses (it's the 
> cache named *partitioned* in this case), and resulting two-step query looks 
> as if its SQL contained {{JOIN}} on *partitioned* and *replicated* caches 
> which we don't support for now.
> Will consult Sergi about what to do next. According to Vlad, this should not 
> affect the release in any way and thus won't be fixed in 1.8.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4327) Failed to INSERT array of Bytes from SELECT

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4327:

Fix Version/s: (was: 2.1)
   2.2

> Failed to INSERT array of Bytes from SELECT
> ---
>
> Key: IGNITE-4327
> URL: https://issues.apache.org/jira/browse/IGNITE-4327
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.2
>
> Attachments: IGNITE-4327.zip
>
>
> An attempt to INSERT binary object having a {{Byte[]}} typed field from 
> {{SELECT *}} yeilds following exception (initially observed in IGNITE-4323):
> {code}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Can not set [Ljava.lang.Byte; field 
> org.apache.ignite.testtools.model.AllTypes.bytesCol to [Ljava.lang.Object;
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1440)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:2183)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1125)
>   at 
> org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:237)
>   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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Can not set 
> [Ljava.lang.Byte; field org.apache.ignite.testtools.model.AllTypes.bytesCol 
> to [Ljava.lang.Object;
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7185)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:169)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:118)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.get(GridDhtAtomicCache.java:482)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4783)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1395)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1118)
>   ... 6 more
> Caused by: java.lang.IllegalArgumentException: Can not set [Ljava.lang.Byte; 
> field org.apache.ignite.testtools.model.AllTypes.bytesCol to 
> [Ljava.lang.Object;
>   at 
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
>   at 
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
>   at 
> sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
>   at java.lang.reflect.Field.set(Field.java:741)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:829)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1498)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
>   at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
>   at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
>   at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
>   at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
>   at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:147)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1760)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:630)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:492)
>   at 
> 

[jira] [Updated] (IGNITE-4338) Cross-schema SQL SELECT on partitioned cache fails for no good reason

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4338:

Fix Version/s: (was: 2.1)
   2.2

> Cross-schema SQL SELECT on partitioned cache fails for no good reason
> -
>
> Key: IGNITE-4338
> URL: https://issues.apache.org/jira/browse/IGNITE-4338
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.1
>
>
> Inspired by IGNITE-4334.
> Suppose we have two caches, one partitioned and one replicated. The following 
> operation fails:
> {code:java}
> ignite.cache("replicated").query(new SqlFieldsQuery("select _key, _val from 
> \"partitioned\".SomeType")).getAll();
> {code}
> Exception is as follows:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Queries running on 
> replicated cache should not contain JOINs with partitioned tables 
> [rCache=replicated, pCache=partitioned]
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.stableDataNodes(GridReduceQueryExecutor.java:432)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:529)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:117)
>   ...
> {noformat}
> The reason is that during query analysis 
> ({{org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#queryTwoStep}})
>  we always deem leftmost cache (the one that the {{query}} method was called 
> on) as participating in the query which is clearly not true in the above 
> example. Then we add to the query the schema that it actually uses (it's the 
> cache named *partitioned* in this case), and resulting two-step query looks 
> as if its SQL contained {{JOIN}} on *partitioned* and *replicated* caches 
> which we don't support for now.
> Will consult Sergi about what to do next. According to Vlad, this should not 
> affect the release in any way and thus won't be fixed in 1.8.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4150) B-Tree index cannot be used efficiently with IN clause.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4150:

Fix Version/s: (was: 2.1)
   2.2

> B-Tree index cannot be used efficiently with IN clause.
> ---
>
> Key: IGNITE-4150
> URL: https://issues.apache.org/jira/browse/IGNITE-4150
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>  Labels: performance
> Fix For: 2.2
>
>
> Consider the following query:
> {code}
> SELECT * FROM table
> WHERE a = ? AND b IN (?, ?)
> {code}
> If there is an index {{(a, b)}}, it will not be used properly: only column 
> {{a}} will be used. This will leads to multiple unnecessary comparisons.
> Most obvious way to fix that - use temporary table and {{JOIN}}. However, 
> this approach doesn't work well when there are multiple {{IN}}'s. 
> Proper solution would be to hack deeper into H2.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4031) SQL: Optimize Date\Time\Timestamp function arguments conversion.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4031:

Fix Version/s: (was: 2.1)
   2.2

> SQL: Optimize Date\Time\Timestamp function arguments conversion.
> 
>
> Key: IGNITE-4031
> URL: https://issues.apache.org/jira/browse/IGNITE-4031
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.6
>Reporter: Andrew Mashenkov
>  Labels: performance
> Fix For: 2.2
>
>
> When sql function with Date\Time\Timestamp arguments is used, H2 internals 
> convert these objects using java.util.Calendar before pass them as arguments.
> In current H2 version we use: DateTimeUtils holds cache java.util.Calendar 
> instance in static field and synchronize every operation on it.
> If its possible, we need to have workaround to use java.util.Calendar more 
> effectively as it done for timestamp fields. See IgniteH2Indexing.wrap() 
> method.
> Startpoint: GridSQLQueryParser.FUNC_ALIAS



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4035) SQL: Avoid excessive calls of deterministic functions on same arguments

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4035:

Fix Version/s: (was: 2.1)
   2.2

> SQL: Avoid excessive calls of deterministic functions on same arguments
> ---
>
> Key: IGNITE-4035
> URL: https://issues.apache.org/jira/browse/IGNITE-4035
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.6, 1.7
>Reporter: Andrew Mashenkov
>Assignee: Sergey Kalashnikov
>  Labels: performance
> Fix For: 2.2
>
>
> In sql query example below, heavy "datediff" deterministic function will be 
> called 4 times per row. I'd expected function was called once per row. 
> Example:
> {noformat}
> Select
>   avg(datediff('s',ts1,ts2)) as avg_diff,
>   min(datediff('s',ts1,ts2)) as min_diff,
>   max(datediff('s',ts1,ts2)) as max_diff
> From table
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4191) Transactional support at the level of Ignite drivers and DML

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4191:

Fix Version/s: (was: 2.1)
   2.2

> Transactional support at the level of Ignite drivers and DML
> 
>
> Key: IGNITE-4191
> URL: https://issues.apache.org/jira/browse/IGNITE-4191
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
> Fix For: 2.2
>
>
> Presently there is no any way to execute data modification statements and 
> SELECT queries in a transactional fashion using our JDBC/ODBC drivers and DML 
> API.
> This can be fully supported once MVCC is ready and released.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4149) Consider adding bitmap index to SQL engine.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4149:

Fix Version/s: (was: 2.1)
   2.2

> Consider adding bitmap index to SQL engine.
> ---
>
> Key: IGNITE-4149
> URL: https://issues.apache.org/jira/browse/IGNITE-4149
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>  Labels: performance
> Fix For: 2.2
>
>
> Bitmap index can help us a lot when there are only several distinct values.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4268:

Fix Version/s: (was: 2.1)
   2.2

> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.2
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond 
> to key or its fields - direct modification would probably damage the index as 
> well as hash map integrity, so UPDATE for such cases would need to do first 
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be 
> implemented in later releases shortly to deliver initial implementation on 
> time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-3911) Unable to add user defined aggregate to H2

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3911:

Fix Version/s: (was: 2.1)
   2.2

> Unable to add user defined aggregate to H2
> --
>
> Key: IGNITE-3911
> URL: https://issues.apache.org/jira/browse/IGNITE-3911
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Tolstokulakov Nikolay
>Assignee: Tolstokulakov Nikolay
> Fix For: 2.2
>
>
> It is possible to add user defined function (@QuerySqlFunction annotation) 
> for H2 SQL, but it is not possible to add user defined aggregate. For 
> consistency I suggest create new annotation @QuerySqlAggregateClass



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3771) JDBC driver tries to initialize the cache store

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3771:
-

[~vkulichenko], as we have DML now, this behavior makes sense. I propose to 
close the ticket as won't fix. Agree?

> JDBC driver tries to initialize the cache store
> ---
>
> Key: IGNITE-3771
> URL: https://issues.apache.org/jira/browse/IGNITE-3771
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
> Fix For: 2.1
>
>
> Since JDBC driver is read-only, the cache store doesn't make sense for it, 
> but having it in cache configuration leads to issues like described in [1]. 
> We should implement a mechanism to ignore such things on JDBC driver 
> (probably use daemon node?).
> [1] 
> http://apache-ignite-users.70518.x6.nabble.com/DiscoveryMetricsProvider-implementation-td7312.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-3478) Transactional SQL

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3478:

Fix Version/s: (was: 2.2.)
   2.2

> Transactional SQL
> -
>
> Key: IGNITE-3478
> URL: https://issues.apache.org/jira/browse/IGNITE-3478
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Alexey Goncharuk
>Assignee: Sergi Vladykin
>  Labels: important
> Fix For: 2.2
>
>
> Current Ignite SQL does not take into account transaction boundaries. For 
> example, if a transaction atomically changes balance of two accounts, then a 
> concurrent SQL query can see partially committed transaction. This works for 
> data analytics, but does not work for more strict and demanding scenarios.
> It would be perfect if we had a mode which ensures transaction boundaries are 
> taken into account for SQL query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-3478) Transactional SQL

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3478:

Fix Version/s: (was: 2.1)
   2.2.

> Transactional SQL
> -
>
> Key: IGNITE-3478
> URL: https://issues.apache.org/jira/browse/IGNITE-3478
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Alexey Goncharuk
>Assignee: Sergi Vladykin
>  Labels: important
> Fix For: 2.2
>
>
> Current Ignite SQL does not take into account transaction boundaries. For 
> example, if a transaction atomically changes balance of two accounts, then a 
> concurrent SQL query can see partially committed transaction. This works for 
> data analytics, but does not work for more strict and demanding scenarios.
> It would be perfect if we had a mode which ensures transaction boundaries are 
> taken into account for SQL query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5145) Support multiple service deployment in API

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5145:

Fix Version/s: (was: None)

> Support multiple service deployment in API
> --
>
> Key: IGNITE-5145
> URL: https://issues.apache.org/jira/browse/IGNITE-5145
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>
> IgniteServices should support possibility of deploying batch of services at 
> once to speed up deployment.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2602:

Fix Version/s: (was: 2.1)
   2.2

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.2
>
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (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 closed IGNITE-2210.
---

> 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, sql
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> 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.15#6346)

[jira] [Updated] (IGNITE-3415) UNION query does not remove duplicates

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3415:

Fix Version/s: (was: 2.1)
   2.2.

> UNION query does not remove duplicates
> --
>
> Key: IGNITE-3415
> URL: https://issues.apache.org/jira/browse/IGNITE-3415
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.6
>Reporter: Semen Boikov
> Fix For: 2.2
>
>
> Looks like UNION query does not remove duplicates on reduce step.
> Added test reproducing issue - IgniteCacheUnionDuplicatesTest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (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 resolved IGNITE-2210.
-
Resolution: Won't Fix

We no longer support SQL fields on methods.

> 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, sql
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> 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.15#6346)

[jira] [Updated] (IGNITE-3415) UNION query does not remove duplicates

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3415:

Fix Version/s: (was: 2.2.)
   2.2

> UNION query does not remove duplicates
> --
>
> Key: IGNITE-3415
> URL: https://issues.apache.org/jira/browse/IGNITE-3415
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.6
>Reporter: Semen Boikov
> Fix For: 2.2
>
>
> Looks like UNION query does not remove duplicates on reduce step.
> Added test reproducing issue - IgniteCacheUnionDuplicatesTest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-5169) ODBC: Rework handshake to allow different handlers

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-5169.
-
Resolution: Fixed

> ODBC: Rework handshake to allow different handlers
> --
>
> Key: IGNITE-5169
> URL: https://issues.apache.org/jira/browse/IGNITE-5169
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5160) C++ Continuous Queries example has to demonstrate the filter usage

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5160:

Component/s: platforms

> C++ Continuous Queries example has to demonstrate the filter usage
> --
>
> Key: IGNITE-5160
> URL: https://issues.apache.org/jira/browse/IGNITE-5160
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.1
>
>
> The existing continuous queries example [1] has to be extended to the usage 
> of a remote filter explained here [2].
> [1] 
> https://github.com/apache/ignite/blob/master/modules/platforms/cpp/examples/continuous-query-example/src/continuous_query_example.cpp
> [2] 
> https://apacheignite-cpp.readme.io/docs/continuous-queries#section-remote-filter



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5159) Create DDL Example

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5159:

Component/s: examples

> Create DDL Example
> --
>
> Key: IGNITE-5159
> URL: https://issues.apache.org/jira/browse/IGNITE-5159
> Project: Ignite
>  Issue Type: Task
>  Components: examples, sql
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> We need to create a DDL example(s) that will demonstrate the following:
> - caches creation and removal using CREATE and DROP table commands.
> - indexes creation and removal using CREATE and DROP index commands.
> If CREATE SCHEME is supported by 2.1 then its usage should be demonstrated as 
> well.
> The example(s) has to be placed into new "sqlgrid" directory of the examples. 
> `CacheQueryExample` and `CacheQueryDmlExample` have to be moved there as 
> well. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5159) Create DDL Example

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5159:
---

Assignee: (was: Vladimir Ozerov)

> Create DDL Example
> --
>
> Key: IGNITE-5159
> URL: https://issues.apache.org/jira/browse/IGNITE-5159
> Project: Ignite
>  Issue Type: Task
>  Components: examples, sql
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> We need to create a DDL example(s) that will demonstrate the following:
> - caches creation and removal using CREATE and DROP table commands.
> - indexes creation and removal using CREATE and DROP index commands.
> If CREATE SCHEME is supported by 2.1 then its usage should be demonstrated as 
> well.
> The example(s) has to be placed into new "sqlgrid" directory of the examples. 
> `CacheQueryExample` and `CacheQueryDmlExample` have to be moved there as 
> well. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5159) Create DDL Example

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5159:

Component/s: sql

> Create DDL Example
> --
>
> Key: IGNITE-5159
> URL: https://issues.apache.org/jira/browse/IGNITE-5159
> Project: Ignite
>  Issue Type: Task
>  Components: examples, sql
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> We need to create a DDL example(s) that will demonstrate the following:
> - caches creation and removal using CREATE and DROP table commands.
> - indexes creation and removal using CREATE and DROP index commands.
> If CREATE SCHEME is supported by 2.1 then its usage should be demonstrated as 
> well.
> The example(s) has to be placed into new "sqlgrid" directory of the examples. 
> `CacheQueryExample` and `CacheQueryDmlExample` have to be moved there as 
> well. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5151) Add some warning when offheap eviction occurs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5151:


Github user shroman closed the pull request at:

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


> Add some warning when offheap eviction occurs
> -
>
> Key: IGNITE-5151
> URL: https://issues.apache.org/jira/browse/IGNITE-5151
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
>Assignee: Wuwei Lin
>
> Currently if offheap eviction occurs we are silently losing data. It whould 
> be helpful to have some warning in log as it's done for onheap eviction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5061) Add ability to enable and disable rebalancing per-node

[Alexander Belyak (JIRA)]

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

Alexander Belyak commented on IGNITE-5061:
--

Dev list thread
http://apache-ignite-developers.2346864.n4.nabble.com/Add-ability-to-enable-and-disable-rebalancing-per-node-td17494.html#a17529

> Add ability to enable and disable rebalancing per-node
> --
>
> Key: IGNITE-5061
> URL: https://issues.apache.org/jira/browse/IGNITE-5061
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexander Belyak
> Fix For: 2.1
>
>
> It would be nice to have an ability to enable and disable rebalancing per 
> node. 
> First of all, we need to come up with a simple API to allow this. 
> Corresponding methods most likely should be also added to Ignite MBean.
> We need to discuss on the dev-list whether it is enough to have this setting 
> per-node, or this needs to be done on a per-cache basis.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-3905) Optimize RendezvousAffinityFunction

[Taras Ledkov (JIRA)]

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

Taras Ledkov resolved IGNITE-3905.
--
Resolution: Duplicate

> Optimize RendezvousAffinityFunction
> ---
>
> Key: IGNITE-3905
> URL: https://issues.apache.org/jira/browse/IGNITE-3905
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Priority: Critical
> Fix For: 2.1
>
>
> Currently RendezvousAffinityFunction.assignPartition generates a lot of 
> garbage if called very often, on example in case of rebalancing a lot of 
> caches.
> This causes excessive pressure on GC, which is not always fast enough to 
> clear memory, producing long GC pauses leading to node segmentation.
> We should cache calculation of nodeHashBytes in node attribute or resort to 
> more efficient node hash calculation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4945) Web Console: Redesign filter controls for tables.

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-4945.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web Console: Redesign filter controls for tables.
> -
>
> Key: IGNITE-4945
> URL: https://issues.apache.org/jira/browse/IGNITE-4945
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Affects Versions: 1.9
>Reporter: Andrey Novikov
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
> Attachments: Filtration.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5151) Add some warning when offheap eviction occurs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5151:


GitHub user vinx13 opened a pull request:

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

IGNITE-5151: Add some warning when offheap eviction occurs



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

$ git pull https://github.com/vinx13/ignite ignite-5151

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

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


commit dfac94012f80d3f415d9e7a7c0b9c6153ce911ae
Author: Wuwei Lin 
Date:   2017-05-10T08:33:35Z

Show warning when off-heap eviction occurs




> Add some warning when offheap eviction occurs
> -
>
> Key: IGNITE-5151
> URL: https://issues.apache.org/jira/browse/IGNITE-5151
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
>Assignee: Wuwei Lin
>
> Currently if offheap eviction occurs we are silently losing data. It whould 
> be helpful to have some warning in log as it's done for onheap eviction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5151) Add some warning when offheap eviction occurs

[Wuwei Lin (JIRA)]

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

Wuwei Lin reassigned IGNITE-5151:
-

Assignee: Wuwei Lin

> Add some warning when offheap eviction occurs
> -
>
> Key: IGNITE-5151
> URL: https://issues.apache.org/jira/browse/IGNITE-5151
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
>Assignee: Wuwei Lin
>
> Currently if offheap eviction occurs we are silently losing data. It whould 
> be helpful to have some warning in log as it's done for onheap eviction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5163:

Component/s: (was: jdbc-driver)
 sql
 odbc

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5164) Rename common ODBC/JDBC classes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5164:

Component/s: (was: jdbc-driver)
 sql

> Rename common ODBC/JDBC classes
> ---
>
> Key: IGNITE-5164
> URL: https://issues.apache.org/jira/browse/IGNITE-5164
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4660) Add DML capabilities to legacy JDBC driver

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4660:

Component/s: (was: jdbc-driver)

> Add DML capabilities to legacy JDBC driver
> --
>
> Key: IGNITE-4660
> URL: https://issues.apache.org/jira/browse/IGNITE-4660
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Alexander Paschenko
> Fix For: 2.1
>
>
> Legacy Ignite JDBC driver lacks DML capabilities, but it turns out that there 
> still are plenty of its users who need DML too, so we should de-deprecate it 
> and enable updating operations in it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)