[jira] [Updated] (IGNITE-3915) Web console: add 'copy to clipboard' button in Preview of each section if browser is supports such feature

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-3915:
---
Description: https://clipboardjs.com/

> Web console: add 'copy to clipboard' button in Preview of each section if 
> browser is supports such feature
> --
>
> Key: IGNITE-3915
> URL: https://issues.apache.org/jira/browse/IGNITE-3915
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>
> https://clipboardjs.com/



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

[jira] [Commented] (IGNITE-3915) Web console: add 'copy to clipboard' button in Preview of each section if browser is supports such feature

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-3915:


https://clipboardjs.com/

> Web console: add 'copy to clipboard' button in Preview of each section if 
> browser is supports such feature
> --
>
> Key: IGNITE-3915
> URL: https://issues.apache.org/jira/browse/IGNITE-3915
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>
> https://clipboardjs.com/



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

[jira] [Resolved] (IGNITE-3915) Web console: add 'copy to clipboard' button in Preview of each section if browser is supports such feature

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov resolved IGNITE-3915.

Resolution: Won't Fix

> Web console: add 'copy to clipboard' button in Preview of each section if 
> browser is supports such feature
> --
>
> Key: IGNITE-3915
> URL: https://issues.apache.org/jira/browse/IGNITE-3915
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>




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

[jira] [Closed] (IGNITE-3915) Web console: add 'copy to clipboard' button in Preview of each section if browser is supports such feature

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-3915.
--

> Web console: add 'copy to clipboard' button in Preview of each section if 
> browser is supports such feature
> --
>
> Key: IGNITE-3915
> URL: https://issues.apache.org/jira/browse/IGNITE-3915
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>




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

[jira] [Updated] (IGNITE-878) Large GC if load data to the cache using datastreamer

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-878:
--
Description: Visor shows large GC during load  (was: Visor UI shows large 
GC during load)

> Large GC if load data to the cache using datastreamer 
> --
>
> Key: IGNITE-878
> URL: https://issues.apache.org/jira/browse/IGNITE-878
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
> Fix For: 2.1
>
> Attachments: ig-878.png, 
> #_IGNITE-878_GC_using_on_data_streaming_test.patch
>
>
> Visor shows large GC during load



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

[jira] [Closed] (IGNITE-3036) We need to set red border to empty mandatory fields after Save

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-3036.
--

> We need to set red border to empty mandatory fields after Save
> --
>
> Key: IGNITE-3036
> URL: https://issues.apache.org/jira/browse/IGNITE-3036
> Project: Ignite
>  Issue Type: Task
>Reporter: Pavel Konstantinov
>




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

[jira] [Resolved] (IGNITE-2984) Need to add validation that Alias and Index fields are present in Fields list

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov resolved IGNITE-2984.

Resolution: Won't Fix

UI will be reworked, no needs to do this.

> Need to add validation that Alias and Index fields are present in Fields list
> -
>
> Key: IGNITE-2984
> URL: https://issues.apache.org/jira/browse/IGNITE-2984
> Project: Ignite
>  Issue Type: Task
>Reporter: Pavel Konstantinov
>




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

[jira] [Closed] (IGNITE-2984) Need to add validation that Alias and Index fields are present in Fields list

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-2984.
--

> Need to add validation that Alias and Index fields are present in Fields list
> -
>
> Key: IGNITE-2984
> URL: https://issues.apache.org/jira/browse/IGNITE-2984
> Project: Ignite
>  Issue Type: Task
>Reporter: Pavel Konstantinov
>




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

[jira] [Resolved] (IGNITE-3036) We need to set red border to empty mandatory fields after Save

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov resolved IGNITE-3036.

Resolution: Won't Fix

Already fixed in web-console

> We need to set red border to empty mandatory fields after Save
> --
>
> Key: IGNITE-3036
> URL: https://issues.apache.org/jira/browse/IGNITE-3036
> Project: Ignite
>  Issue Type: Task
>Reporter: Pavel Konstantinov
>




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

[jira] [Updated] (IGNITE-878) Large GC if load data to the cache using datastreamer

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-878:
--
Description: Visor UI shows large GC during load

> Large GC if load data to the cache using datastreamer 
> --
>
> Key: IGNITE-878
> URL: https://issues.apache.org/jira/browse/IGNITE-878
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
> Fix For: 2.1
>
> Attachments: ig-878.png, 
> #_IGNITE-878_GC_using_on_data_streaming_test.patch
>
>
> Visor UI shows large GC during load



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

[jira] [Commented] (IGNITE-5121) REST API call with empty cache name causes NPE

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-5121:
--

[~s.kozlov] Can you please verify it is fixed?

> REST API call with empty cache name causes NPE
> --
>
> Key: IGNITE-5121
> URL: https://issues.apache.org/jira/browse/IGNITE-5121
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Minor
> Fix For: 2.1
>
>
> Request cache entry without cacheName causes NPE on the node:
> {noformat}
> [19:58:33,960][SEVERE][qtp153051342-48][GridJettyRestProtocol] Failed to 
> process HTTP request [action=/ignite, req=(POST 
> /ignite?cmd=get=mykey-529=2128506-ad94-4a21-a711-529=)@2130154253
>  org.eclipse.jetty.server.Request@7ef7930d]
> class org.apache.ignite.IgniteCheckedException: null
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7242)
>   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:172)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at 
> java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:333)
>   at 
> java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:988)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.cache(GridCacheProcessor.java:3439)
>   at 
> org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler.localCache(GridCacheCommandHandler.java:752)
>   at 
> org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler.executeCommand(GridCacheCommandHandler.java:678)
>   at 
> org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler.handleAsync(GridCacheCommandHandler.java:427)
>   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:266)
>   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:89)
>   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:155)
>   ... 4 more
> {noformat}



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

[jira] [Commented] (IGNITE-4324) ScanQuery throws incomprehensible exception when topology does not contain data nodes

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4324:
-

[~ntikhonov], would you be able to review the fix?

> ScanQuery throws incomprehensible exception when topology does not contain 
> data nodes
> -
>
> Key: IGNITE-4324
> URL: https://issues.apache.org/jira/browse/IGNITE-4324
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: Nikolay Tikhonov
>Assignee: William Do
>  Labels: newbie
> Fix For: 2.1
>
> Attachments: Tests.patch
>
>
> ScanQuery throws incomprehensible exception when topology does not contain 
> data nodes (for example with node filter).  See attached test.
> {code}
> java.lang.IllegalArgumentException: bound must be positive
>   at java.util.Random.nextInt(Random.java:388)
>   at org.apache.ignite.internal.util.lang.GridFunc.rand(GridFunc.java:677)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.nodes(GridCacheQueryAdapter.java:582)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:527)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4119)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4094)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.iterator(IgniteCacheProxy.java:1979)
>   at 
> org.apache.ignite.internal.CacheFilterQueryTest.testScanQuery(CacheFilterQueryTest.java:90)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1768)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1706)
>   at java.lang.Thread.run(Thread.java:745)
> [
> {code}



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

[jira] [Updated] (IGNITE-5277) Asynchronously establish connection to all the needed nodes in IgniteH2Indexing.send()

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-5277:
--
Fix Version/s: 2.1

> Asynchronously establish connection to all the needed nodes in 
> IgniteH2Indexing.send()
> --
>
> Key: IGNITE-5277
> URL: https://issues.apache.org/jira/browse/IGNITE-5277
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergi Vladykin
> Fix For: 2.1
>
>
> it's only a minor optimization until the point when establishing each 
> connection takes 3-4 seconds, and we establish 32 of them in sequence.  At 
> that point it becomes a serious issue: the customer cannot run SQL queries 
> from their development machines



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

[jira] [Created] (IGNITE-5285) Update metrics documentation

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5285:
---

 Summary: Update metrics documentation
 Key: IGNITE-5285
 URL: https://issues.apache.org/jira/browse/IGNITE-5285
 Project: Ignite
  Issue Type: Sub-task
Reporter: Denis Magda
Assignee: Denis Magda


1) Describe new metrics related to the Persistent Store.
2) Update the existing metrics: 
https://issues.apache.org/jira/browse/IGNITE-5124



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

[jira] [Commented] (IGNITE-5284) Split IgniteH2Indexing into multiple classes if possible

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5284:


GitHub user devozerov opened a pull request:

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

IGNITE-5284



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

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

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

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


commit 99d2299d0964c163396c9335b9de098f5c533b8a
Author: devozerov 
Date:   2017-05-23T11:44:56Z

WIP.

commit 56a6bf342f3b213ec2a6ffb37657605b39a5e8fc
Author: devozerov 
Date:   2017-05-23T11:47:08Z

WIP.

commit ea983d7a5fe1bbe6aa34baed2600df61f018484f
Author: devozerov 
Date:   2017-05-23T12:01:46Z

WIP.

commit f046fe04952e78a94af97a9e361012409b6b1a7c
Author: devozerov 
Date:   2017-05-23T12:02:41Z

Done.

commit 21f94a2a2460b8b2a17bfa989f94735c6661211f
Author: devozerov 
Date:   2017-05-23T12:45:44Z

Done.

commit 650c6f537567e1008360e25b348bd5e53baed5e8
Author: devozerov 
Date:   2017-05-23T17:45:03Z

Merge branch 'master' into ignite-5282

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheProxy.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryIndexing.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DmlStatementsProcessor.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java

commit e126c89792259e88ead379607f7ae3c7efb6f681
Author: devozerov 
Date:   2017-05-23T18:03:04Z

WIP.

commit adc79f578e211fdeca5908ecc400d90103f63b76
Author: devozerov 
Date:   2017-05-23T18:10:52Z

WIP on removing cache name.

commit eb2b21a630e5ff25fb01da01ba848b789d00e9b8
Author: devozerov 
Date:   2017-05-23T18:24:52Z

Splitting H2 indexing.

commit 546e82d055db1e1bbd3c08945bdea916b64d0dd8
Author: devozerov 
Date:   2017-05-23T19:33:37Z

FIxed DML.

commit 607bfc25892d6dc447d6db6482aa8697972e7624
Author: devozerov 
Date:   2017-05-23T19:39:09Z

Merge branch 'ignite-5282' into ignite-5282-1

# Conflicts:
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DmlStatementsProcessor.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java

commit 8c44cec3c691f4f1b2789df319e1d5e0dcc333f1
Author: devozerov 
Date:   2017-05-23T20:33:19Z

WIP.

commit 2faca3facb56ec20cff3cb7d607939c48e18c616
Author: devozerov 
Date:   2017-05-23T20:35:37Z

Removed unused methods.

commit 2acde63c558943dd9f3dd624649b4a1469d3b105
Author: devozerov 
Date:   2017-05-23T20:36:50Z

Dangerous commit: removed cacheNameForSchemaAndTable.

commit bc5dc7880115e19b3d828d415d27e0b09a6d670b
Author: devozerov 
Date:   2017-05-23T20:37:37Z

Revert dangerous commit.

commit a0a1c4a3de4d3b2eb94fab12f04b7916df2f0fbb
Author: devozerov 
Date:   2017-05-23T20:48:22Z

Finished.

commit b7863c9c9abe846fdc84c12a563096ce2ced0d37
Author: devozerov 
Date:   2017-05-23T21:05:20Z

Merge branch 'master' into ignite-5284

# Conflicts:
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DmlStatementsProcessor.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java




> Split IgniteH2Indexing into multiple classes if possible
> 
>
> Key: IGNITE-5284
> URL: https://issues.apache.org/jira/browse/IGNITE-5284
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> {{IgniteH2Indexing}} is overly complex. Let's move inner classes out of it 
> where applicable.



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

[jira] [Resolved] (IGNITE-5282) Pass "keepBinary" flag to SQL processor from the outside

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-5282.
-
Resolution: Fixed

> Pass "keepBinary" flag to SQL processor from the outside
> 
>
> Key: IGNITE-5282
> URL: https://issues.apache.org/jira/browse/IGNITE-5282
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently "keepBinary" is sometimes passed from the outside, but sometimes is 
> taken from cache context. We need to always take it from the outside.



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

[jira] [Commented] (IGNITE-5282) Pass "keepBinary" flag to SQL processor from the outside

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5282:


Github user devozerov closed the pull request at:

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


> Pass "keepBinary" flag to SQL processor from the outside
> 
>
> Key: IGNITE-5282
> URL: https://issues.apache.org/jira/browse/IGNITE-5282
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently "keepBinary" is sometimes passed from the outside, but sometimes is 
> taken from cache context. We need to always take it from the outside.



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

[jira] [Created] (IGNITE-5284) Split IgniteH2Indexing into multiple classes if possible

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5284:
---

 Summary: Split IgniteH2Indexing into multiple classes if possible
 Key: IGNITE-5284
 URL: https://issues.apache.org/jira/browse/IGNITE-5284
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.1


{{IgniteH2Indexing}} is overly complex. Let's move inner classes out of it 
where applicable.



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

[jira] [Closed] (IGNITE-4052) Add ability to set up users for MESOS

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-4052.
---

Reviewed.

> Add ability to set up users for MESOS
> -
>
> Key: IGNITE-4052
> URL: https://issues.apache.org/jira/browse/IGNITE-4052
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Prachi Garg
>Priority: Trivial
>
> In current implementation Ignite Mesos Framework connects to MESOS cluster 
> via current user. Need to add ability to configure this parameters via system 
> env properties. Also need to add properties for mesos role.
> See org/apache/ignite/mesos/IgniteFramework.java:537



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

[jira] [Commented] (IGNITE-3355) CPP: Implement Compute::Call() for Ignite C++.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-3355:
-

All functionality implemented. Tests implemented and pass on Windows. Need to 
re-factor and test on Linux.

> CPP: Implement Compute::Call() for Ignite C++.
> --
>
> Key: IGNITE-3355
> URL: https://issues.apache.org/jira/browse/IGNITE-3355
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> Need to implement {{Compute}} class with {{Compute::Call}} method.



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

[jira] [Commented] (IGNITE-5203) JDBC driver should support BLOB fields

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-5203:
-

[~vkulichenko] Thanks for comments. Fixed. PR updated.

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



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

[jira] [Commented] (IGNITE-5281) Change "space" notion to "cacheName"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5281:


Github user devozerov closed the pull request at:

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


> Change "space" notion to "cacheName"
> 
>
> Key: IGNITE-5281
> URL: https://issues.apache.org/jira/browse/IGNITE-5281
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Space is always equal to cache name. Let's rename all internals from "space" 
> to "cacheName". No need for confusion.



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

[jira] [Commented] (IGNITE-5277) Asynchronously establish connection to all the needed nodes in IgniteH2Indexing.send()

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5277:
-

The discussion on the dev list: 
http://apache-ignite-developers.2346864.n4.nabble.com/Inefficient-approach-to-executing-remote-SQL-queries-td17882.html

> Asynchronously establish connection to all the needed nodes in 
> IgniteH2Indexing.send()
> --
>
> Key: IGNITE-5277
> URL: https://issues.apache.org/jira/browse/IGNITE-5277
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergi Vladykin
>
> it's only a minor optimization until the point when establishing each 
> connection takes 3-4 seconds, and we establish 32 of them in sequence.  At 
> that point it becomes a serious issue: the customer cannot run SQL queries 
> from their development machines



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

[jira] [Assigned] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov reassigned IGNITE-5038:
-

Assignee: Vladislav Pyatkov

> BinaryMarshaller might need to use context class loader for deserialization
> ---
>
> Key: IGNITE-5038
> URL: https://issues.apache.org/jira/browse/IGNITE-5038
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>Assignee: Vladislav Pyatkov
>  Labels: features
> Fix For: 2.1
>
>
> There is a special use case discussed on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224
> According to the use case, BinaryMarshaller might need to try to deserialize 
> an object using a context class loader if it failed to do so with a custom 
> classloader (`IgniteConfiguration.getClassLoader()`) or the system one.



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

[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-532:
---

GitHub user dream-x opened a pull request:

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

IGNITE-532: Implement IgniteAkkaStreamer to stream data from Akka actors.



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

$ git pull https://github.com/dream-x/ignite ignite-532

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

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


commit f47ab06b1ca4416eefc10ee80237898864dc67e5
Author: Max Kozlov 
Date:   2017-04-03T14:02:17Z

Init akka stream module.

commit d105635dbe0ae8617404ef82a933a181a07cad8e
Author: Max Kozlov 
Date:   2017-04-04T09:49:09Z

Add akka-actor and -stream dependency in pom.xml.

commit d44d4edaa07d11b9e69aef5e20f4e4ab1249d64e
Author: Max Kozlov 
Date:   2017-04-06T16:45:54Z

Update akka dependency.

commit c63fc6290558fb552fb84e1213d2f85c9e51ddc6
Author: Max Kozlov 
Date:   2017-04-06T16:46:19Z

wip

commit 4aafc72c70941c89da36a26d3d00e23f2f384246
Author: Max Kozlov 
Date:   2017-04-13T08:47:01Z

Add akka-stream streamer.

commit f9b35d691517822fee29dd61cc10b4b160bbd3f6
Author: Max Kozlov 
Date:   2017-04-13T08:47:15Z

Add akka-stream streamer test.

commit b79bc8dfaf9e7ef8a385ee245b09629216e10b17
Author: Max Kozlov 
Date:   2017-04-13T08:47:36Z

Delete ExampleAkkaStreamToIgniteStream.java

commit a835cee93c86ba5f9f5119621d2e5efe73423ed5
Author: Max Kozlov 
Date:   2017-04-13T09:01:56Z

Delete onComplete test.

commit 513d3c75be5ec625f1ca5b6b3d3b27ed2d75aab3
Author: Max Kozlov 
Date:   2017-04-13T10:45:51Z

wip.

commit 924c9ae96b0a91c662ad9c06bd7c919f4935faf6
Author: Max Kozlov 
Date:   2017-04-14T08:24:28Z

Change version akka to 2.5.

commit 09d26b9972931e5595a7bb30e9796ef8816ff455
Author: Max Kozlov 
Date:   2017-04-18T14:35:18Z

Ignite streamer based on Scala Actor.

commit cc3548f429484e24a2454ec2e98961d102e3fe55
Author: Max Kozlov 
Date:   2017-04-19T13:57:29Z

Refactoring.

commit a912475488da162df8f7662489382fec90716024
Author: Max Kozlov 
Date:   2017-04-27T14:35:59Z

wip

commit 5dde548ff359f466de9df155aacc093cbfab77fd
Author: Max Kozlov 
Date:   2017-05-02T13:32:52Z

Add test akka actor streamer.

commit cb45c197d377e13f9d489bcc562615d8d7e5a3a2
Author: Max Kozlov 
Date:   2017-05-03T11:10:36Z

Refactoring scala tests.

commit b5be16c5221a91467699aec487543c676635433b
Author: Max Kozlov 
Date:   2017-05-03T11:15:14Z

Update akka to 2.5

commit ffc3c9975e6dd8fb2e881d6a0c6b3f2708208874
Author: Max Kozlov 
Date:   2017-05-03T12:33:18Z

Update pom.xml

commit 6e9203eec0096f168c89158c16659808f14cc498
Author: Max Kozlov 
Date:   2017-05-04T13:31:22Z

Refactoring.

commit 318748ab26819eab16be9a971b26386ed0244d4c
Author: Max Kozlov 
Date:   2017-05-15T09:24:46Z

Delete unused code.

commit 805490ef138bc351ac357cc80de5329115a4a5a7
Author: Max Kozlov 
Date:   2017-05-22T14:30:45Z

Remove java classes. Refactor imports.

commit ec7917681480d3b5476a141a30e86b7c89609e4f
Author: Max Kozlov 
Date:   2017-05-23T15:36:41Z

Refactoring code.




> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Maksim Kozlov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala 
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka 
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If 
> not provided, then we should have some default mechanism.
> * 

[jira] [Comment Edited] (IGNITE-3562) Dependency to outdated Lucene 3.5.0

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov edited comment on IGNITE-3562 at 5/23/17 3:27 PM:
---

Tests looks good after upgrade to 4.10.4.

Upgrading to latest Lucene version 5.5.2 seems to be much easy 
if it made in 2 steps: 3.5.0 -> 4.x -> 5.x 



was (Author: amashenkov):
Tests looks good after upgrade to 4.10.4.

Upgrading to latest Lucene version 6.5.1 seems to be much easy 
if it made in 3 steps: 3.5.0 -> 4.x -> 5.x -> latest 6.x.

Waiting for TC test for Lucene 6.5.1.


> Dependency to outdated Lucene 3.5.0
> ---
>
> Key: IGNITE-3562
> URL: https://issues.apache.org/jira/browse/IGNITE-3562
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexander Veit
>Assignee: Andrew Mashenkov
>  Labels: jar-hell
> Fix For: 2.1
>
>
> Ignite 1.6.0 comes with Lucene 3.5.0 core as dependency, which dates back to 
> the year 2011.
> This makes it difficult to integrate with newer software.



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

[jira] [Resolved] (IGNITE-2133) Schema Import Utility should print warning about wrong IGNITE_HOME

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-2133.
--
Resolution: Won't Fix
  Assignee: Alexey Kuznetsov

Schema Import development was discontinued in ignite-2.0 in favor of Web 
Console. 

> Schema Import Utility should print warning about wrong IGNITE_HOME
> --
>
> Key: IGNITE-2133
> URL: https://issues.apache.org/jira/browse/IGNITE-2133
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Minor
>




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

[jira] [Updated] (IGNITE-3365) .NET: User-defined affinity mapper

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3365:
---
Description: See {{AffinityKeyMapper}} interface in Java. Provide this 
interface in .NET.

> .NET: User-defined affinity mapper
> --
>
> Key: IGNITE-3365
> URL: https://issues.apache.org/jira/browse/IGNITE-3365
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> See {{AffinityKeyMapper}} interface in Java. Provide this interface in .NET.



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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4575:


.NET is failing because it does not expect enum field map in the metadata. We 
need to implement all the new APIs there:
* {{IBinary.BuildEnum(string, string)}}
* {{IBinary.RegisterEnum(string, string)}}
* {{IBinaryObject.EnumName}}
* Serialize and deserialize enums in binary form 
({{GridBinaryMarshaller.BINARY_ENUM = 38}} type code}}

I'm working on these in a separate branch.

[~vozerov] can you please explain why do we need {{IgniteBinary.registerEnum}} 
method? We don't have such methods for regular types, they are registered 
either in {{BinaryConfiguration}} or automatically.

> 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-3562) Dependency to outdated Lucene 3.5.0

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-3562:
--

Tests looks good after upgrade to 4.10.4.

Upgrading to latest Lucene version 6.5.1 seems to be much easy 
if it made in 3 steps: 3.5.0 -> 4.x -> 5.x -> latest 6.x.

Waiting for TC test for Lucene 6.5.1.


> Dependency to outdated Lucene 3.5.0
> ---
>
> Key: IGNITE-3562
> URL: https://issues.apache.org/jira/browse/IGNITE-3562
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexander Veit
>Assignee: Andrew Mashenkov
>  Labels: jar-hell
> Fix For: 2.1
>
>
> Ignite 1.6.0 comes with Lucene 3.5.0 core as dependency, which dates back to 
> the year 2011.
> This makes it difficult to integrate with newer software.



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

[jira] [Comment Edited] (IGNITE-2492) .NET: Peer assembly loading

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-2492 at 5/23/17 2:34 PM:
-

[~vozerov], peer deploying assemblies to a separate AppDomain allows unloading, 
but has the following issues:
* Multiple AppDomains are not supported in .NET Core (Cross-platform .NET, 
IGNITE-2662)
* AppDomains do not share anything. Static variables have different values, you 
can't pass object references from one to another. So user code will observe 
unexpected behavior with static state
* AppDomains are expensive. We'll have to spin up all Ignite APIs in a separate 
domain again, register binary types, prepare reflective actions, and so on. 
Managing lifetime of these objects and JNI interop will be complicated.

Given all of the above, I propose the following:
* Replace {{IgniteConfiguration.PeerAssemblyLoadingEnabled}} with an enum 
{{IgniteConfiguration.PeerAssemblyLoadingMode}} with values {{None}} (default) 
and {{SameAppDomain}}.
* Release current implementation and implement isolated mode later.

This way users have clear understanding of what is going on and that other 
modes will be added in future.
Agreed?


was (Author: ptupitsyn):
[~vozerov], peer deploying assemblies to a separate AppDomain allows unloading, 
but has the following issues:
* Multiple AppDomains are not supported in .NET Core (Cross-platform .NET, 
IGNITE-2662)
* AppDomains do not share anything. Static variables have different values, you 
can't pass object references from one to another. So user code will observer 
unexpected behavior with static state
* AppDomains are expensive. We'll have to spin up all Ignite APIs in a separate 
domain again, register binary types, prepare reflective actions, and so on. 
Managing lifetime of these objects and JNI interop will be complicated.

Given all of the above, I propose the following:
* Replace {{IgniteConfiguration.PeerAssemblyLoadingEnabled}} with an enum 
{{IgniteConfiguration.PeerAssemblyLoadingMode}} with values {{None}} (default) 
and {{SameAppDomain}}.
* Release current implementation and implement isolated mode later.

This way users have clear understanding of what is going on and that other 
modes will be added in future.
Agreed?

> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load 
> assemblies on already started nodes, so that a node can execute jobs that are 
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate 
> AppDomain, can we work with that?



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

[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2492:


[~vozerov], peer deploying assemblies to a separate AppDomain allows unloading, 
but has the following issues:
* Multiple AppDomains are not supported in .NET Core (Cross-platform .NET, 
IGNITE-2662)
* AppDomains do not share anything. Static variables have different values, you 
can't pass object references from one to another. So user code will observer 
unexpected behavior with static state
* AppDomains are expensive. We'll have to spin up all Ignite APIs in a separate 
domain again, register binary types, prepare reflective actions, and so on. 
Managing lifetime of these objects and JNI interop will be complicated.

Given all of the above, I propose the following:
* Replace {{IgniteConfiguration.PeerAssemblyLoadingEnabled}} with an enum 
{{IgniteConfiguration.PeerAssemblyLoadingMode}} with values {{None}} (default) 
and {{SameAppDomain}}.
* Release current implementation and implement isolated mode later.

This way users have clear understanding of what is going on and that other 
modes will be added in future.
Agreed?

> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load 
> assemblies on already started nodes, so that a node can execute jobs that are 
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate 
> AppDomain, can we work with that?



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

[jira] [Commented] (IGNITE-5203) JDBC driver should support BLOB fields

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-5203:
-

[~agura], here are my comments:
* Do we also need to implement {{Connection.createBlob}} and 
{{PreparedStatement.setBlob}} methods?
* {{U.systemCopy}} should be used instead of {{System.arrayCopy}}. It utilizes 
unsafe where possible.
* Unsupported methods should throw {{SQLFeatureNotSupportedException}}, not 
{{UnsupportedOperationException}}.

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



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

[jira] [Assigned] (IGNITE-5053) Add missing features to H2 parser for CREATE/DROP TABLE

[Vadim Opolski (JIRA)]

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

Vadim Opolski reassigned IGNITE-5053:
-

Assignee: (was: Vadim Opolski)

> Add missing features to H2 parser for CREATE/DROP TABLE
> ---
>
> Key: IGNITE-5053
> URL: https://issues.apache.org/jira/browse/IGNITE-5053
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> We need to {{AFFINITY KEY}} attribute. 
> Final name is yet to be defined. May be we should have several synonyms 
> resembling other databases to make migration to Ignite easier.



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

[jira] [Commented] (IGNITE-5242) Disallow DROP TABLE on statically configured caches

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-5242:
-

PR: https://github.com/apache/ignite/pull/1996

> Disallow DROP TABLE on statically configured caches
> ---
>
> Key: IGNITE-5242
> URL: https://issues.apache.org/jira/browse/IGNITE-5242
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Should we allow {{DROP TABLE}} on statically configured cache, there will be 
> a room for weird situations when it is impossible to understand on whether to 
> start the cache or not.



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4994:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4994 Restored GridH2TableSelfTest



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

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

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

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


commit d64c115f5e1a944a360e899f35a4073a44959695
Author: Alexander Paschenko 
Date:   2017-05-22T12:07:33Z

IGNITE-4994 Restored GridH2TableSelfTest




> 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.1
>
>
> 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] [Resolved] (IGNITE-5223) Allow use local binary metadata cache if it's possible

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev resolved IGNITE-5223.
-
Resolution: Fixed

> Allow use local binary metadata cache if it's possible
> --
>
> Key: IGNITE-5223
> URL: https://issues.apache.org/jira/browse/IGNITE-5223
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 1.9
>
>
> Add system property that will use local binary metadata cache instead of 
> distributed one, when all classes available on all nodes and don't change.



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

[jira] [Created] (IGNITE-5283) Transaction recovery works incorrectly with cache store and writeThrough enabled

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-5283:
---

 Summary: Transaction recovery works incorrectly with cache store 
and writeThrough enabled
 Key: IGNITE-5283
 URL: https://issues.apache.org/jira/browse/IGNITE-5283
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Andrey Gura


Transaction (at least optimistic) recovery on backups works incorrectly when 
cache store and writeThrough enabled. Changes aren't propagated to DB (it's 
correct) but propagated to cache if primary node left topology.

It happens because {{IgniteTxRemoteStateAdapter.storeUsed()}} method always 
returns {{false}}. As result incorrect code branch executes in 
{{NodeFailureTimeoutObject.onTimeout0()}} method ({{salvageTx()}} method should 
be invoked).

*Steps to reproduce*:
- Start two nodes A and B with cache. Cache store and writeThrough are anbled.
- From node A start optimistic transaction which executes put/update operation 
for key. Node A should be primary for this key.
- Kill node A when {{CacheStore.sessionEnd()}} method is invoked but changes 
are not propagated to underlying database (before commit on connection).
- DB doesn't contain changes but node B contains it.

*Expected behaviour:*

All changes should be rolled back.



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

[jira] [Commented] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5176:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5176 JDBC Driver: implement query execution for thin jdbc driver 
based on common odbc/jdbc protocol



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

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

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

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


commit c7e215347e567f5c6c11954d932cfbb63743ec24
Author: tledkov-gridgain 
Date:   2017-05-04T14:59:38Z

IGNITE-5163 save the progress

commit b0023f87ab9f08063001bee77931ae9edc13487e
Author: tledkov-gridgain 
Date:   2017-05-05T12:03:08Z

IGNITE-5163 save the progress

commit fa9fee2a996f676f2a1c3371adaf0a35ce2810f7
Author: tledkov-gridgain 
Date:   2017-05-05T12:03:14Z

Merge branch '_master' into ignite-5163

commit dca4546b82547f1eef97e7bd1f3254914d3b5055
Author: tledkov-gridgain 
Date:   2017-05-05T12:06:04Z

Merge branch '_master' into ignite-5163

commit db57be2da1beddc91df301033386f2a97ec578f2
Author: tledkov-gridgain 
Date:   2017-05-05T12:11:29Z

IGNITE-5163: fix after merge

commit 4412b1b085c7f81426e4d11b139ad856f0b6bf2d
Author: tledkov-gridgain 
Date:   2017-05-05T12:33:10Z

IGNITE-5163: minor

commit d8d0a9b6309cd75b37ff50f18c22560a26c9c23b
Author: tledkov-gridgain 
Date:   2017-05-05T14:02:46Z

Merge branch 'master' into ignite-5163

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/SqlListenerProtocolVersion.java

commit 7f60086405d8160c5d24f9a5cd36f99e81fd8e4e
Author: tledkov-gridgain 
Date:   2017-05-05T14:54:15Z

IGNITE-5163: fix after merge

commit 461a6fe654db0e81f84c74649b5e88a703af80c9
Author: tledkov-gridgain 
Date:   2017-05-05T15:04:50Z

IGNITE-5163: add properties to handshake

commit abd3894dd3419bdc1a14f15893fc9737d1cd0761
Author: tledkov-gridgain 
Date:   2017-05-05T15:08:01Z

IGNITE-5163: minors

commit 7ddc2f7641f222a29dbc8caa5197f453db0d5981
Author: tledkov-gridgain 
Date:   2017-05-10T08:49:17Z

Merge branch '_master' into ignite-5163

commit 9bfe91d3a597083da921220650c3e417dbb0b5c6
Author: devozerov 
Date:   2017-05-10T09:59:22Z

Merge branch 'master' into ignite-5163

commit a303e25e5d1fe815e314d4fad2858d1d374487a8
Author: devozerov 
Date:   2017-05-10T10:24:00Z

Review.

commit 8b94095ab8ab8a70d7fc9ec20df52e0c19d5bd19
Author: devozerov 
Date:   2017-05-10T10:25:28Z

Merge remote-tracking branch 'upstream/ignite-5163' into ignite-5163

# Conflicts:
#   modules/core/src/main/java/org/apache/ignite/IgniteJdbcThinDriver.java
#   
modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/JdbcTcpIo.java

commit e8eb3f519dbd8a1bca3acf42bb8b8477afc385e4
Author: tledkov-gridgain 
Date:   2017-05-11T12:03:18Z

IGNITE-5163: fix review issues

commit 081f27794d76adbf61add720dd0b1f88a69b373e
Author: tledkov-gridgain 
Date:   2017-05-11T12:10:13Z

IGNITE-5163: minors

commit 0c045b61faa1791f7c4929f208bd0e83e3b581cb
Author: tledkov-gridgain 
Date:   2017-05-11T12:59:54Z

Merge branch '_master' into ignite-5163

commit d715f83068877c4532c9f0bcb008f2ab5e0571e1
Author: tledkov-gridgain 
Date:   2017-05-11T15:58:25Z

IGNITE-5176: save the progress

commit 9f1c6ac0c1223c550335387737b817ca491615c3
Author: tledkov-gridgain 
Date:   2017-05-12T11:57:08Z

IGNITE-5176: save the progress

commit 58417ef19844d625935b8d4ca7a3237cca7c72af
Author: tledkov-gridgain 
Date:   2017-05-12T12:44:44Z

Merge branch '_master' into ignite-5163

commit 80435c4344dea89a8f39fe4bfe6cc78174c2bede
Author: tledkov-gridgain 
Date:   2017-05-12T12:45:42Z

Merge branch '_master' into ignite-5176

commit 3e366385f336a385fd4c4818578626eeca73e38d
Author: tledkov-gridgain 
Date:   2017-05-12T13:15:58Z

IGNITE-5163: serialization refactoring

commit e4e38acc67f0d607ac08d8e53ecece2459d6a364
Author: tledkov-gridgain 
Date:   2017-05-12T13:16:33Z

Merge branch 'ignite-5163' into ignite-5176

commit 

[jira] [Commented] (IGNITE-5245) MIN function returns NULL if a numeric column of class has NULL values

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-5245:


I have checked this and found out that Ignite behaviour is actually the same as 
H2.
In case there is only {{null}} values in the field, the result for {{select 
min(value) from test}} is {{null}}.
In case there are some meaningful values along with {{null}} values, the result 
for  {{select min(value) from test}} is minimum value among non-null values.

Below are my tests for both Ignite and H2:

{code:java}
package org.apache.ignite.internal.processors.query.h2;

import java.util.List;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.cache.query.QueryCursor;
import org.apache.ignite.cache.query.SqlFieldsQuery;
import org.apache.ignite.cache.query.annotations.QuerySqlField;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;

/** Test for https://issues.apache.org/jira/browse/IGNITE-5245 */
public class Issue_5245_Test extends GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new 
TcpDiscoveryVmIpFinder(true);

/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();

startGrids(4);
}

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

stopAllGrids();
}

/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String gridName) 
throws Exception {
IgniteConfiguration cfg = super.getConfiguration(gridName);

TcpDiscoverySpi spi = (TcpDiscoverySpi)cfg.getDiscoverySpi();

spi.setIpFinder(IP_FINDER);

CacheConfiguration ccfg = new 
CacheConfiguration<>(DEFAULT_CACHE_NAME);

ccfg.setIndexedTypes(Integer.class, ValueObj.class);

cfg.setCacheConfiguration(ccfg);

if ("client".equals(gridName))
cfg.setClientMode(true);

return cfg;
}

/** Check min() over null */
public void testQueryMinMaxNull() throws Exception {
try (Ignite client = startGrid("client")) {
IgniteCache cache = 
client.cache(DEFAULT_CACHE_NAME);

cache.put(1, new ValueObj(null));

SqlFieldsQuery qry = new SqlFieldsQuery("select min(value) from 
ValueObj");

QueryCursor cursor = cache.query(qry);

List result = cursor.getAll();

assertNull(result.get(0).get(0));

final Short testVal = 1;

cache.put(2, new ValueObj(testVal));

cursor = cache.query(qry);

result = cursor.getAll();

assertEquals(testVal, result.get(0).get(0));
}
}

/** Value object for test cache */
public class ValueObj {
/** */
@QuerySqlField
private Short value;

/** */
public ValueObj(Short value) {
this.value = value;
}

/** {@inheritDoc} */
@Override public int hashCode() {
return value;
}

/** {@inheritDoc} */
@Override public boolean equals(Object o) {
if (this == o)
return true;

if (!(o instanceof ValueObj))
return false;

ValueObj other = (ValueObj)o;

return value == other.value;
}
}
}
{code}

H2 Console test:
{code}
drop table test if exists;
create table test(id smallint);
insert into test values (null);
select min(id) from test;
insert into test values (1);
select min(id) from test;
{code}

H2 Console results
{noformat}
MIN(ID)  
null
(1 row, 1 ms)

MIN(ID)  
1
(1 row, 0 ms)
{noformat}


> MIN function returns NULL if a numeric column of class has NULL values
> --
>
> Key: IGNITE-5245
> URL: https://issues.apache.org/jira/browse/IGNITE-5245
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
>
> 1. Use class ({{DefaultTable}}) with the numeric field (e.g. {{Short 
> col_Short_1}})
> 2. Put a few entries where one entry has the field is null
> 3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
> 4. It returns NULL but for same case h2 returns non-null minimal value



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

[jira] [Assigned] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4865:
---

Assignee: Alexandr Kuramshin  (was: Vladimir Ozerov)

> Non-informative error message on using GridClientOptimizedMarshaller with 
> unknown task classes
> --
>
> Key: IGNITE-4865
> URL: https://issues.apache.org/jira/browse/IGNITE-4865
> Project: Ignite
>  Issue Type: Improvement
>  Components: clients
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Alexandr Kuramshin
> Fix For: 2.1
>
>
> Upon {{GridClientCompute.execute()}} I get non-informative error if a task 
> class is not present in {{classnames.properties}}. It occurs when 
> {{GridClient}} was configured to use {{GridClientOptimizedMarshaller}}.
> {noformat}
> Closing NIO session because of unhandled exception [cls=class 
> o.a.i.i.util.nio.GridNioException, msg=class o.a.i.IgniteCheckedException: 
> Failed to deserialize object with given class loader: null]
> {noformat}
> There is two problems:
> * Actual problem was hidden
> {noformat}
> Caused by: java.lang.UnsupportedOperationException
> at 
> org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller$ClientMarshallerContext.className(GridClientOptimizedMarshaller.java:137)
> at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:367)
> {noformat}
> * Even reading the cause we don't understand what is wrong
> What to do:
> * Log stacktrace every time
> * Throw UnsupportedOperationException with informative message.



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

[jira] [Commented] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4865:
-

[~ein], could you please merge PR with master and make sure that the fix is 
still relevant? I see that methods where you changed error message have gone in 
current master.

> Non-informative error message on using GridClientOptimizedMarshaller with 
> unknown task classes
> --
>
> Key: IGNITE-4865
> URL: https://issues.apache.org/jira/browse/IGNITE-4865
> Project: Ignite
>  Issue Type: Improvement
>  Components: clients
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Upon {{GridClientCompute.execute()}} I get non-informative error if a task 
> class is not present in {{classnames.properties}}. It occurs when 
> {{GridClient}} was configured to use {{GridClientOptimizedMarshaller}}.
> {noformat}
> Closing NIO session because of unhandled exception [cls=class 
> o.a.i.i.util.nio.GridNioException, msg=class o.a.i.IgniteCheckedException: 
> Failed to deserialize object with given class loader: null]
> {noformat}
> There is two problems:
> * Actual problem was hidden
> {noformat}
> Caused by: java.lang.UnsupportedOperationException
> at 
> org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller$ClientMarshallerContext.className(GridClientOptimizedMarshaller.java:137)
> at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:367)
> {noformat}
> * Even reading the cause we don't understand what is wrong
> What to do:
> * Log stacktrace every time
> * Throw UnsupportedOperationException with informative message.



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

[jira] [Assigned] (IGNITE-5245) MIN function returns NULL if a numeric column of class has NULL values

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov reassigned IGNITE-5245:
--

Assignee: Sergey Kalashnikov

> MIN function returns NULL if a numeric column of class has NULL values
> --
>
> Key: IGNITE-5245
> URL: https://issues.apache.org/jira/browse/IGNITE-5245
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
>
> 1. Use class ({{DefaultTable}}) with the numeric field (e.g. {{Short 
> col_Short_1}})
> 2. Put a few entries where one entry has the field is null
> 3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
> 4. It returns NULL but for same case h2 returns non-null minimal value



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5163:


Github user asfgit closed the pull request at:

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


> 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] [Commented] (IGNITE-5282) Pass "keepBinary" flag to SQL processor from the outside

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5282:


GitHub user devozerov opened a pull request:

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

IGNITE-5282



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

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

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

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


commit 99d2299d0964c163396c9335b9de098f5c533b8a
Author: devozerov 
Date:   2017-05-23T11:44:56Z

WIP.

commit 56a6bf342f3b213ec2a6ffb37657605b39a5e8fc
Author: devozerov 
Date:   2017-05-23T11:47:08Z

WIP.

commit ea983d7a5fe1bbe6aa34baed2600df61f018484f
Author: devozerov 
Date:   2017-05-23T12:01:46Z

WIP.

commit f046fe04952e78a94af97a9e361012409b6b1a7c
Author: devozerov 
Date:   2017-05-23T12:02:41Z

Done.

commit 21f94a2a2460b8b2a17bfa989f94735c6661211f
Author: devozerov 
Date:   2017-05-23T12:45:44Z

Done.




> Pass "keepBinary" flag to SQL processor from the outside
> 
>
> Key: IGNITE-5282
> URL: https://issues.apache.org/jira/browse/IGNITE-5282
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently "keepBinary" is sometimes passed from the outside, but sometimes is 
> taken from cache context. We need to always take it from the outside.



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

[jira] [Created] (IGNITE-5282) Pass "keepBinary" flag to SQL processor from the outside

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5282:
---

 Summary: Pass "keepBinary" flag to SQL processor from the outside
 Key: IGNITE-5282
 URL: https://issues.apache.org/jira/browse/IGNITE-5282
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.1


Currently "keepBinary" is sometimes passed from the outside, but sometimes is 
taken from cache context. We need to always take it from the outside.



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

[jira] [Commented] (IGNITE-4904) .NET: DML via LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4904:


{{RemoveAll}} is a better name (since we have {{ICache.RemoveAll}} and there is 
{{List.RemoveAll}}),

> .NET: DML via LINQ
> --
>
> Key: IGNITE-4904
> URL: https://issues.apache.org/jira/browse/IGNITE-4904
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, LINQ
> Fix For: 2.1
>
>
> Perform bulk update operations via LINQ: {{UPDATE WHERE}}, {{DELETE WHERE}}. 
> Insert can already be done on object level with {{ICache.PutAll}}.
> 1) {{DELETE WHERE}}. This is quite simple. We can provide an extension method 
> like this:
> {code}
> public static int DeleteAll(this ICache cache, 
> IQueryable> items);
> {code}
> 2) {{UPDATE WHERE}}. This is tricky, because LINQ only works with expression 
> trees, and multi-line methods are not supported. We should come up with a way 
> to provide a list of columns and values, something like
> {code}
> public static int UpdateAll(this ICache cache, 
> IQueryable> items, params UpdateAction[] actions);
> {code}
> where UpdateAction can consist of a MemberExpression and a value for that 
> member.
> We should probably do delete as a separate task first.



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

[jira] [Comment Edited] (IGNITE-4904) .NET: DML via LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4904 at 5/23/17 12:42 PM:
--

{{RemoveAll}} is a better name (since we have {{ICache.RemoveAll}} and there is 
{{List.RemoveAll}}).


was (Author: ptupitsyn):
{{RemoveAll}} is a better name (since we have {{ICache.RemoveAll}} and there is 
{{List.RemoveAll}}),

> .NET: DML via LINQ
> --
>
> Key: IGNITE-4904
> URL: https://issues.apache.org/jira/browse/IGNITE-4904
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, LINQ
> Fix For: 2.1
>
>
> Perform bulk update operations via LINQ: {{UPDATE WHERE}}, {{DELETE WHERE}}. 
> Insert can already be done on object level with {{ICache.PutAll}}.
> 1) {{DELETE WHERE}}. This is quite simple. We can provide an extension method 
> like this:
> {code}
> public static int DeleteAll(this ICache cache, 
> IQueryable> items);
> {code}
> 2) {{UPDATE WHERE}}. This is tricky, because LINQ only works with expression 
> trees, and multi-line methods are not supported. We should come up with a way 
> to provide a list of columns and values, something like
> {code}
> public static int UpdateAll(this ICache cache, 
> IQueryable> items, params UpdateAction[] actions);
> {code}
> where UpdateAction can consist of a MemberExpression and a value for that 
> member.
> We should probably do delete as a separate task first.



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

[jira] [Updated] (IGNITE-5212) Allow custom affinity for system caches

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-5212:
-
Fix Version/s: 2.1

> Allow custom affinity for system caches
> ---
>
> Key: IGNITE-5212
> URL: https://issues.apache.org/jira/browse/IGNITE-5212
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Vladislav Pyatkov
>  Labels: newbie
> Fix For: 2.1
>
>
> Currently there is no option to specify affinity function atomics system 
> cache, which may be not appropriate in custom data placement scenarios.
> Suggestion: allow setting custom affinity for AtomicConfiguration



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

[jira] [Updated] (IGNITE-5253) .NET: Fields query cursor metadata

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5253:
---
Priority: Minor  (was: Major)

> .NET: Fields query cursor metadata
> --
>
> Key: IGNITE-5253
> URL: https://issues.apache.org/jira/browse/IGNITE-5253
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET
> Fix For: 2.1
>
>
> Same as IGNITE-5252 for .NET:
> Provide a way to get fields information from the query cursor.



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

[jira] [Commented] (IGNITE-5252) SqlFieldsQuery result set should expose fields metadata.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5252:


Github user asfgit closed the pull request at:

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


> SqlFieldsQuery result set should expose fields metadata.
> 
>
> Key: IGNITE-5252
> URL: https://issues.apache.org/jira/browse/IGNITE-5252
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.1
>
>
> Internal class QueryCursorImpl can contains fields metadata, but QueryCursor 
> does not provide any method for this. So, the only way for user to get 
> metadata is to cast result object to internal class.
> We should extend QueryCursor in child interface and change 
> IgniteCache.query() return type for SqlFieldsQueries.



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

[jira] [Comment Edited] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-1094 at 5/23/17 12:10 PM:


 [~DmitriyGovorukhin] 
There are some issues regarding your comment on withdrawing cache :

*public DynamicCacheDescriptor withdrawCache(String cacheName){*
*It is not enough for correct clean up. Check all shared managers.*  

When an exception raised in createCache(), no cache managers are created, and 
no cache context created.I see no cache-related info in *shared managers* in 
that very time.
But there are some info in *grid components* from GridKernalContext(i.e. 
GridContinuousProcessor). So could you clearify what *shared managers* should 
be deleted.

So , there 2 options on how to delete cache-related info from *grid components*:
1)manually delete it (first i need to make field 
*ClusterCachesInfo#registeredCaches* public and then call 
*registeredCaches.remove()*, and then delete other info)

2)Or, i could initiatate correct cache delete request by calling 
*GridCacheProcessor#dynamicDestroyCache()*.

PS.
Unfortunately, i cannot delete cache by creating *DynamicCacheChangeRequest* 
and putting it into *exchActions.addCacheToStop* from 
GridDhtPartitionsExchangeFuture.
Because method onDone() is got called with error.


was (Author: alexey kuznetsov):
 [~DmitriyGovorukhin] 
There are some issues regarding your comment on withdrawing cache :

*public DynamicCacheDescriptor withdrawCache(String cacheName){*
*It is not enough for correct clean up. Check all shared managers.*  

When an exception raised in createCache(), no cache managers are created, and 
no cache context created.I see no cache-related info in *shared managers* in 
that very time.
But there are some info in *grid components* from GridKernalContext(i.e. 
GridContinuousProcessor). So could you clearify what *shared managers* should 
be deleted.

So , there 2 options on how to delete cache-related info from *grid components*:
manually delete it (first i need to make field 
*ClusterCachesInfo#registeredCaches* public and then call 
*registeredCaches.remove()*, and then delete other info)
Or, i could initiatate correct cache delete request by calling 
*GridCacheProcessor#dynamicDestroyCache()*.

PS.
Unfortunately, i cannot delete cache by creating *DynamicCacheChangeRequest* 
and putting it into *exchActions.addCacheToStop* from 
GridDhtPartitionsExchangeFuture.
Because method onDone() is got called with error.

> Ignite.createCache(CacheConfiguration) hangs if some exception occurs during 
> cache initialization
> -
>
> Key: IGNITE-1094
> URL: https://issues.apache.org/jira/browse/IGNITE-1094
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Sergey Evdokimov
>Assignee: Alexey Kuznetsov
>  Labels: Muted_test
> Fix For: 2.1
>
>
> User can pass broken configuration, for example, store factory that throws 
> exception from create() method. I created test to demonstrate the problem. 
> See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' 
> branch 



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

[jira] [Comment Edited] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-1094 at 5/23/17 12:09 PM:


 [~DmitriyGovorukhin] 
There are some issues regarding your comment on withdrawing cache :

*public DynamicCacheDescriptor withdrawCache(String cacheName){*
*It is not enough for correct clean up. Check all shared managers.*  

When an exception raised in createCache(), no cache managers are created, and 
no cache context created.I see no cache-related info in *shared managers* in 
that very time.
But there are some info in *grid components* from GridKernalContext(i.e. 
GridContinuousProcessor). So could you clearify what *shared managers* should 
be deleted.

So , there 2 options on how to delete cache-related info from *grid components*:
manually delete it (first i need to make field 
*ClusterCachesInfo#registeredCaches* public and then call 
*registeredCaches.remove()*, and then delete other info)
Or, i could initiatate correct cache delete request by calling 
*GridCacheProcessor#dynamicDestroyCache()*.

PS.
Unfortunately, i cannot delete cache by creating *DynamicCacheChangeRequest* 
and putting it into *exchActions.addCacheToStop* from 
GridDhtPartitionsExchangeFuture.
Because method onDone() is got called with error.


was (Author: alexey kuznetsov):
 [~DmitriyGovorukhin] 
There are some issues regarding your comment on withdrawing cache :

*public DynamicCacheDescriptor withdrawCache(String cacheName){*
*It is not enough for correct clean up. Check all shared managers.*  

When an exception raised in createCache(), no cache managers are created, and 
no cache context created.I see no cache-related info in *shared managers* in 
that very time.
But there are some info in *grid components* from GridKernalContext(i.e. 
GridContinuousProcessor). So could you clearify what *shared managers* should 
be deleted.

So , there 2 options on how to delete cache-related info from *grid components*:
manually delete it (first i need to make field 
*ClusterCachesInfo#registeredCaches* public and then call 
*registeredCaches.remove()*, and then delete other info)
Or, i could initiatate correct cache delete request by calling 
*GridCacheProcessor#dynamicDestroyCache()*.



> Ignite.createCache(CacheConfiguration) hangs if some exception occurs during 
> cache initialization
> -
>
> Key: IGNITE-1094
> URL: https://issues.apache.org/jira/browse/IGNITE-1094
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Sergey Evdokimov
>Assignee: Alexey Kuznetsov
>  Labels: Muted_test
> Fix For: 2.1
>
>
> User can pass broken configuration, for example, store factory that throws 
> exception from create() method. I created test to demonstrate the problem. 
> See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' 
> branch 



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

[jira] [Commented] (IGNITE-5150) Allocated memory pages count is incorrect during load test

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5150:


Github user asfgit closed the pull request at:

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


> Allocated memory pages count is incorrect during load test
> --
>
> Key: IGNITE-5150
> URL: https://issues.apache.org/jira/browse/IGNITE-5150
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
> Fix For: 2.1
>
> Attachments: 183504_id0_server.log, 183507_id0_driver.log, 
> ignite-base-load-config.xml, run-load.properties, run-load.xml, 
> top-driver.log, top-server.log
>
>
> Load test config:
> - CacheRandomOpearion benchmark
> - 1 server (-Xms4g -Xmx4g)
> - 1 client (-Xms4g -Xmx4g)
> - 1 cache with following config
> {noformat}
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
> 
> 
> 
> 
> 
> 
> 
>  value="org.apache.ignite.yardstick.cache.model.Organization"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {noformat}
> - preloaded data: 40M entries
> - backup count: 0
> - memory config:
> {noformat}
> 
> 
>  
> 
>
>
>
> 
>   
>   
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
> 
> 
>   
> 
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
>  value="memPolicyCfg_evict_LRU"/>
>value="RANDOM_LRU"/>
> 
>   
> 
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
>  value="memPolicyCfg_evict_2LRU"/>
>value="RANDOM_2_LRU"/>
> 
>   
> 
>   
> 
> 
> 
> {noformat}
> 40M entries consume about 4Gb offheap memory. It might be proved by {{top}} 
> command (RES value - JVM memory = 8Gb - 4Gb) or by summing all "Allocated 
> next memory segment" printed in server log.
> After all data preloaded metrics show the following:
> {noformat}
> [18:37:18,152][INFO ][grid-timeout-worker-#23%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=dc009e3c, name=null, uptime=00:02:10:102]
> ^-- H/N/C [hosts=2, nodes=2, CPUs=32]
> ^-- CPU [cur=19.53%, avg=11.99%, GC=0.03%]
> ^-- PageMemory [pages=22527667]
> ^-- Heap [used=238MB, free=94.17%, comm=4096MB]
> ^-- Non heap [used=40MB, free=68.18%, comm=45MB]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=10, qSize=0]
> ^-- Outbound messages queue [size=0]
> {noformat}
> pages=22527667 seems to be wrong, otherwise offheap memory size would be 
> 22527667 * 2KB = about 43Gb.
> Driver and server logs, yardstick configs, top logs are attached.
> Note:
> This problem leads to eviction working incorrectly. 
> {code}
> boolean shouldEvict = allocatedPagesCnt > (memorySize / sysPageSize * 
> plcCfg.getEvictionThreshold()) &&
> emptyDataPagesCnt < plcCfg.getEmptyPagesPoolSize();
> {code}
> If I change memory policy for the cache to memPolicyCfg_evict_2LRU I expect 
> that eviction happens when about 4Gb of offheap memory is used. But it 
> happens at 1Gb, since at this point memory pages count =~ 2M (2M * 2Kb =~ 
> 4Gb).



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

[jira] [Commented] (IGNITE-5150) Allocated memory pages count is incorrect during load test

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-5150:
--

Merged to master. Ksenia, can you please re-check?

> Allocated memory pages count is incorrect during load test
> --
>
> Key: IGNITE-5150
> URL: https://issues.apache.org/jira/browse/IGNITE-5150
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
> Fix For: 2.1
>
> Attachments: 183504_id0_server.log, 183507_id0_driver.log, 
> ignite-base-load-config.xml, run-load.properties, run-load.xml, 
> top-driver.log, top-server.log
>
>
> Load test config:
> - CacheRandomOpearion benchmark
> - 1 server (-Xms4g -Xmx4g)
> - 1 client (-Xms4g -Xmx4g)
> - 1 cache with following config
> {noformat}
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
> 
> 
> 
> 
> 
> 
> 
>  value="org.apache.ignite.yardstick.cache.model.Organization"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {noformat}
> - preloaded data: 40M entries
> - backup count: 0
> - memory config:
> {noformat}
> 
> 
>  
> 
>
>
>
> 
>   
>   
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
> 
> 
>   
> 
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
>  value="memPolicyCfg_evict_LRU"/>
>value="RANDOM_LRU"/>
> 
>   
> 
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
>  value="memPolicyCfg_evict_2LRU"/>
>value="RANDOM_2_LRU"/>
> 
>   
> 
>   
> 
> 
> 
> {noformat}
> 40M entries consume about 4Gb offheap memory. It might be proved by {{top}} 
> command (RES value - JVM memory = 8Gb - 4Gb) or by summing all "Allocated 
> next memory segment" printed in server log.
> After all data preloaded metrics show the following:
> {noformat}
> [18:37:18,152][INFO ][grid-timeout-worker-#23%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=dc009e3c, name=null, uptime=00:02:10:102]
> ^-- H/N/C [hosts=2, nodes=2, CPUs=32]
> ^-- CPU [cur=19.53%, avg=11.99%, GC=0.03%]
> ^-- PageMemory [pages=22527667]
> ^-- Heap [used=238MB, free=94.17%, comm=4096MB]
> ^-- Non heap [used=40MB, free=68.18%, comm=45MB]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=10, qSize=0]
> ^-- Outbound messages queue [size=0]
> {noformat}
> pages=22527667 seems to be wrong, otherwise offheap memory size would be 
> 22527667 * 2KB = about 43Gb.
> Driver and server logs, yardstick configs, top logs are attached.
> Note:
> This problem leads to eviction working incorrectly. 
> {code}
> boolean shouldEvict = allocatedPagesCnt > (memorySize / sysPageSize * 
> plcCfg.getEvictionThreshold()) &&
> emptyDataPagesCnt < plcCfg.getEmptyPagesPoolSize();
> {code}
> If I change memory policy for the cache to memPolicyCfg_evict_2LRU I expect 
> that eviction happens when about 4Gb of offheap memory is used. But it 
> happens at 1Gb, since at this point memory pages count =~ 2M (2M * 2Kb =~ 
> 4Gb).



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

[jira] [Assigned] (IGNITE-5150) Allocated memory pages count is incorrect during load test

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-5150:


Assignee: Ksenia Rybakova  (was: Alexey Goncharuk)

> Allocated memory pages count is incorrect during load test
> --
>
> Key: IGNITE-5150
> URL: https://issues.apache.org/jira/browse/IGNITE-5150
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
> Fix For: 2.1
>
> Attachments: 183504_id0_server.log, 183507_id0_driver.log, 
> ignite-base-load-config.xml, run-load.properties, run-load.xml, 
> top-driver.log, top-server.log
>
>
> Load test config:
> - CacheRandomOpearion benchmark
> - 1 server (-Xms4g -Xmx4g)
> - 1 client (-Xms4g -Xmx4g)
> - 1 cache with following config
> {noformat}
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
> 
> 
> 
> 
> 
> 
> 
>  value="org.apache.ignite.yardstick.cache.model.Organization"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {noformat}
> - preloaded data: 40M entries
> - backup count: 0
> - memory config:
> {noformat}
> 
> 
>  
> 
>
>
>
> 
>   
>   
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
> 
> 
>   
> 
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
>  value="memPolicyCfg_evict_LRU"/>
>value="RANDOM_LRU"/>
> 
>   
> 
>class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
>  value="memPolicyCfg_evict_2LRU"/>
>value="RANDOM_2_LRU"/>
> 
>   
> 
>   
> 
> 
> 
> {noformat}
> 40M entries consume about 4Gb offheap memory. It might be proved by {{top}} 
> command (RES value - JVM memory = 8Gb - 4Gb) or by summing all "Allocated 
> next memory segment" printed in server log.
> After all data preloaded metrics show the following:
> {noformat}
> [18:37:18,152][INFO ][grid-timeout-worker-#23%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=dc009e3c, name=null, uptime=00:02:10:102]
> ^-- H/N/C [hosts=2, nodes=2, CPUs=32]
> ^-- CPU [cur=19.53%, avg=11.99%, GC=0.03%]
> ^-- PageMemory [pages=22527667]
> ^-- Heap [used=238MB, free=94.17%, comm=4096MB]
> ^-- Non heap [used=40MB, free=68.18%, comm=45MB]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=10, qSize=0]
> ^-- Outbound messages queue [size=0]
> {noformat}
> pages=22527667 seems to be wrong, otherwise offheap memory size would be 
> 22527667 * 2KB = about 43Gb.
> Driver and server logs, yardstick configs, top logs are attached.
> Note:
> This problem leads to eviction working incorrectly. 
> {code}
> boolean shouldEvict = allocatedPagesCnt > (memorySize / sysPageSize * 
> plcCfg.getEvictionThreshold()) &&
> emptyDataPagesCnt < plcCfg.getEmptyPagesPoolSize();
> {code}
> If I change memory policy for the cache to memPolicyCfg_evict_2LRU I expect 
> that eviction happens when about 4Gb of offheap memory is used. But it 
> happens at 1Gb, since at this point memory pages count =~ 2M (2M * 2Kb =~ 
> 4Gb).



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

[jira] [Updated] (IGNITE-5263) ODBC: use schema notion instead of cache name

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5263:

Labels: cpp odbc  (was: )

> ODBC: use schema notion instead of cache name
> -
>
> Key: IGNITE-5263
> URL: https://issues.apache.org/jira/browse/IGNITE-5263
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp, odbc
> Fix For: 2.1
>
>
> We should no longer operate on "cacheName". Instead, we should work with 
> schemas.



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

[jira] [Commented] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-1094:
--

 [~DmitriyGovorukhin] 
There are some issues regarding your comment on withdrawing cache :

*public DynamicCacheDescriptor withdrawCache(String cacheName){*
*It is not enough for correct clean up. Check all shared managers.*  

When an exception raised in createCache(), no cache managers are created, and 
no cache context created.I see no cache-related info in *shared managers* in 
that very time.
But there are some info in *grid components* from GridKernalContext(i.e. 
GridContinuousProcessor). So could you clearify what *shared managers* should 
be deleted.

So , there 2 options on how to delete cache-related info from *grid components*:
manually delete it (first i need to make field 
*ClusterCachesInfo#registeredCaches* public and then call 
*registeredCaches.remove()*, and then delete other info)
Or, i could initiatate correct cache delete request by calling 
*GridCacheProcessor#dynamicDestroyCache()*.



> Ignite.createCache(CacheConfiguration) hangs if some exception occurs during 
> cache initialization
> -
>
> Key: IGNITE-1094
> URL: https://issues.apache.org/jira/browse/IGNITE-1094
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Sergey Evdokimov
>Assignee: Alexey Kuznetsov
>  Labels: Muted_test
> Fix For: 2.1
>
>
> User can pass broken configuration, for example, store factory that throws 
> exception from create() method. I created test to demonstrate the problem. 
> See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' 
> branch 



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

[jira] [Commented] (IGNITE-5281) Change "space" notion to "cacheName"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5281:


GitHub user devozerov opened a pull request:

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

IGNITE-5281



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

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

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

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


commit 99d2299d0964c163396c9335b9de098f5c533b8a
Author: devozerov 
Date:   2017-05-23T11:44:56Z

WIP.

commit 56a6bf342f3b213ec2a6ffb37657605b39a5e8fc
Author: devozerov 
Date:   2017-05-23T11:47:08Z

WIP.

commit ea983d7a5fe1bbe6aa34baed2600df61f018484f
Author: devozerov 
Date:   2017-05-23T12:01:46Z

WIP.

commit f046fe04952e78a94af97a9e361012409b6b1a7c
Author: devozerov 
Date:   2017-05-23T12:02:41Z

Done.




> Change "space" notion to "cacheName"
> 
>
> Key: IGNITE-5281
> URL: https://issues.apache.org/jira/browse/IGNITE-5281
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Space is always equal to cache name. Let's rename all internals from "space" 
> to "cacheName". No need for confusion.



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

[jira] [Resolved] (IGNITE-3605) Commits\rollbacks count is ZERO for transactional cache in case if the load generated by client node

[Stanilovsky Evgeny (JIRA)]

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

Stanilovsky Evgeny resolved IGNITE-3605.

   Resolution: Cannot Reproduce
Fix Version/s: 1.7

> Commits\rollbacks count is ZERO for transactional cache in case if the load 
> generated by client node 
> -
>
> Key: IGNITE-3605
> URL: https://issues.apache.org/jira/browse/IGNITE-3605
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Pavel Konstantinov
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Fix For: 1.7
>
>
> Start any cluster
> Start any load via client node to transactional cache
> Take metrics from this cache and verify amount of commits and rollbacks



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

[jira] [Closed] (IGNITE-5215) Allow user to configure memory policy with maxSize lesser than default initialSize

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk closed IGNITE-5215.


> Allow user to configure memory policy with maxSize lesser than default 
> initialSize
> --
>
> Key: IGNITE-5215
> URL: https://issues.apache.org/jira/browse/IGNITE-5215
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Ivan Rakov
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
>
> Attempt to create memory policy with small maxSize ends with error:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: MemoryPolicy 
> maxSize must not be smaller than initialSize [name=dfltMemPlc, initSize=268,4 
> MB, maxSize=209,7 MB]
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.checkPolicySize(IgniteCacheDatabaseSharedManager.java:419)
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.validateConfiguration(IgniteCacheDatabaseSharedManager.java:337)
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:112)
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:99)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.initDataBase(GridCacheDatabaseSharedManager.java:493)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.start0(GridCacheDatabaseSharedManager.java:436)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:644)
>   at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
>   ... 29 more
> {noformat}
> This can be easily fixed by setting initialSize. Though, it would be better 
> to don't oblige user to spend time on fixing it.



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

[jira] [Created] (IGNITE-5281) Change "space" notion to "cacheName"

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5281:
---

 Summary: Change "space" notion to "cacheName"
 Key: IGNITE-5281
 URL: https://issues.apache.org/jira/browse/IGNITE-5281
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.1


Space is always equal to cache name. Let's rename all internals from "space" to 
"cacheName". No need for confusion.



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

[jira] [Assigned] (IGNITE-5174) Need to have opportunity to list only server nodes for specified topology version

[Stanilovsky Evgeny (JIRA)]

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

Stanilovsky Evgeny reassigned IGNITE-5174:
--

Assignee: Alexey Goncharuk  (was: Eduard Shangareev)

> Need to have opportunity to list only server nodes for specified topology 
> version
> -
>
> Key: IGNITE-5174
> URL: https://issues.apache.org/jira/browse/IGNITE-5174
> Project: Ignite
>  Issue Type: Bug
>Reporter: Stanilovsky Evgeny
>Assignee: Alexey Goncharuk
>Priority: Minor
> Fix For: 2.1
>
>
> Need to have common utility function which filters client nodes for specified 
> topology version.



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

[jira] [Assigned] (IGNITE-4551) Reconsider cache key/value peer class loading

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov reassigned IGNITE-4551:


Assignee: (was: Nikolay Tikhonov)

> Reconsider cache key/value peer class loading
> -
>
> Key: IGNITE-4551
> URL: https://issues.apache.org/jira/browse/IGNITE-4551
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Alexey Goncharuk
> Fix For: 2.1
>
>
> In new cache implementation after entry is written in offheap information 
> about key/value classloaders in lost (before classloader ids were stored in 
> swap/offheap see GridCacheMapEntry.swap in 'master').
> Need decide how it should work with new architecture (maybe single type per 
> cache can simplify implementation).



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

[jira] [Commented] (IGNITE-5215) Allow user to configure memory policy with maxSize lesser than default initialSize

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5215:


Github user asfgit closed the pull request at:

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


> Allow user to configure memory policy with maxSize lesser than default 
> initialSize
> --
>
> Key: IGNITE-5215
> URL: https://issues.apache.org/jira/browse/IGNITE-5215
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Ivan Rakov
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
>
> Attempt to create memory policy with small maxSize ends with error:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: MemoryPolicy 
> maxSize must not be smaller than initialSize [name=dfltMemPlc, initSize=268,4 
> MB, maxSize=209,7 MB]
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.checkPolicySize(IgniteCacheDatabaseSharedManager.java:419)
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.validateConfiguration(IgniteCacheDatabaseSharedManager.java:337)
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:112)
>   at 
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:99)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.initDataBase(GridCacheDatabaseSharedManager.java:493)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.start0(GridCacheDatabaseSharedManager.java:436)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:644)
>   at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
>   ... 29 more
> {noformat}
> This can be easily fixed by setting initialSize. Though, it would be better 
> to don't oblige user to spend time on fixing it.



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

[jira] [Updated] (IGNITE-1678) IgniteAtomicSequence: make following reservations in advance

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-1678:
---
Fix Version/s: (was: 2.1)
   2.2

> IgniteAtomicSequence: make following reservations in advance
> 
>
> Key: IGNITE-1678
> URL: https://issues.apache.org/jira/browse/IGNITE-1678
> Project: Ignite
>  Issue Type: Improvement
>  Components: data structures
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Dmitriy Govorukhin
> Fix For: 2.2
>
> Attachments: Screenshot from 2016-12-15 10-50-22.png
>
>
> In current implementation a new reservation is made when the current local 
> sequence boundary is exceeded.
> In cases when there are many nodes that use the same atomic sequence there 
> can be a situation when all the nodes start doing a new reservation at the 
> same time. This can lead to performance drops.
> As a performance optimization it makes sense to start reserving new sequence 
> slot in advance (in background), like when around 80% of current reservation 
> has already been used. Probably we should add a special parameter to 
> {{AtomicConfiguration}} that will manage such behavior.



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

[jira] [Updated] (IGNITE-2539) NPE at RendezvousAffinityFunction

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-2539:
---
Fix Version/s: (was: 2.1)
   2.2

> NPE at RendezvousAffinityFunction
> -
>
> Key: IGNITE-2539
> URL: https://issues.apache.org/jira/browse/IGNITE-2539
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.2
>
> Attachments: ignite.log
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> RendezvousAffinityFunction#assignPartition throws NPE, probably due to 
> simultaneous topology change and  cache stop. We should write a test and fix 
> this.



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

[jira] [Commented] (IGNITE-5264) DDL operations must operate on per-schema basis

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5264:


Github user devozerov closed the pull request at:

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


> DDL operations must operate on per-schema basis
> ---
>
> Key: IGNITE-5264
> URL: https://issues.apache.org/jira/browse/IGNITE-5264
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently we rely on cache name in schema operations. Schema should be used 
> instead:
> 1) Start missing caches in case of "TABLE NOT FOUND" and "INDEX NOT FOUND" 
> errors as well;
> 2) Pass schema name to {{SchemaChangeOperation}} instead of cache name.
> 3) Concurrency control on per-schema basis in {{GridQueryProcessor}}.



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

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

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov updated IGNITE-2216:
---
Fix Version/s: (was: 2.1)
   2.2

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




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

[jira] [Updated] (IGNITE-5273) MemoryMetrics API improvements to be ported to .NET

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-5273:

Fix Version/s: 2.1

> MemoryMetrics API improvements to be ported to .NET
> ---
>
> Key: IGNITE-5273
> URL: https://issues.apache.org/jira/browse/IGNITE-5273
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Sergey Chugunov
>  Labels: important
> Fix For: 2.1
>
>
> Improvements already made for linked ticket need to be ported on .NET side.



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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5204:

Component/s: sql

> The Unicode character in the value of a field which are included in an 
> un-unique index will cause "stack overhead" exception
> 
>
> Key: IGNITE-5204
> URL: https://issues.apache.org/jira/browse/IGNITE-5204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Priority: Critical
> Fix For: 2.1
>
>
> When put  "草DX009090" as the value of BillId, which is a field of entity 
> Bill. If I define a index includes the BillId, and execute the query like 
> "select * from Bill where BillId=’草DX009090‘ in the H2 debug console, there 
> throws an exception by the H2 with a code 5000. 
> another scenario is, I have two entities, "Bill" and "Detail", both have 
> field "BillId". If either of them have value like "草DX009090" and execute the 
> query like "select bill.* from bill left join detail on 
> bill.billid=detail.billid", the whole ignite cache node will halt ( suppose 
> there should be an stack overhead exception, dead loop).
> ==
> I think the issue should relate to hash computing on the unicode character.



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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5204:
---

Assignee: (was: Vladimir Ozerov)

> The Unicode character in the value of a field which are included in an 
> un-unique index will cause "stack overhead" exception
> 
>
> Key: IGNITE-5204
> URL: https://issues.apache.org/jira/browse/IGNITE-5204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Priority: Critical
> Fix For: 2.1
>
>
> When put  "草DX009090" as the value of BillId, which is a field of entity 
> Bill. If I define a index includes the BillId, and execute the query like 
> "select * from Bill where BillId=’草DX009090‘ in the H2 debug console, there 
> throws an exception by the H2 with a code 5000. 
> another scenario is, I have two entities, "Bill" and "Detail", both have 
> field "BillId". If either of them have value like "草DX009090" and execute the 
> query like "select bill.* from bill left join detail on 
> bill.billid=detail.billid", the whole ignite cache node will halt ( suppose 
> there should be an stack overhead exception, dead loop).
> ==
> I think the issue should relate to hash computing on the unicode character.



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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5204:

Fix Version/s: 2.1

> The Unicode character in the value of a field which are included in an 
> un-unique index will cause "stack overhead" exception
> 
>
> Key: IGNITE-5204
> URL: https://issues.apache.org/jira/browse/IGNITE-5204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.1
>
>
> When put  "草DX009090" as the value of BillId, which is a field of entity 
> Bill. If I define a index includes the BillId, and execute the query like 
> "select * from Bill where BillId=’草DX009090‘ in the H2 debug console, there 
> throws an exception by the H2 with a code 5000. 
> another scenario is, I have two entities, "Bill" and "Detail", both have 
> field "BillId". If either of them have value like "草DX009090" and execute the 
> query like "select bill.* from bill left join detail on 
> bill.billid=detail.billid", the whole ignite cache node will halt ( suppose 
> there should be an stack overhead exception, dead loop).
> ==
> I think the issue should relate to hash computing on the unicode character.



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

[jira] [Commented] (IGNITE-5252) SqlFieldsQuery result set should expose fields metadata.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5252:
--

TC tests looks fine.

> SqlFieldsQuery result set should expose fields metadata.
> 
>
> Key: IGNITE-5252
> URL: https://issues.apache.org/jira/browse/IGNITE-5252
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.1
>
>
> Internal class QueryCursorImpl can contains fields metadata, but QueryCursor 
> does not provide any method for this. So, the only way for user to get 
> metadata is to cast result object to internal class.
> We should extend QueryCursor in child interface and change 
> IgniteCache.query() return type for SqlFieldsQueries.



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

[jira] [Comment Edited] (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:comment-tabpanel=16020970#comment-16020970
 ] 

Taras Ledkov edited comment on IGNITE-5163 at 5/23/17 10:21 AM:


Fixed, 
[tests|http://195.239.208.174/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F1912%2Fhead]
 are OK.


was (Author: tledkov-gridgain):
Fixed, waiting for 
[tests|http://195.239.208.174/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F1912%2Fhead].

> 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] [Commented] (IGNITE-5053) Add missing features to H2 parser for CREATE/DROP TABLE

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5053:
-

[~javaller], please note that the patch is already submitted to H2 community 
for review. This ticket is created only to track the progress of separate 
contribution to H2.

> Add missing features to H2 parser for CREATE/DROP TABLE
> ---
>
> Key: IGNITE-5053
> URL: https://issues.apache.org/jira/browse/IGNITE-5053
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vadim Opolski
>  Labels: important
> Fix For: 2.1
>
>
> We need to {{AFFINITY KEY}} attribute. 
> Final name is yet to be defined. May be we should have several synonyms 
> resembling other databases to make migration to Ignite easier.



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

[jira] [Assigned] (IGNITE-5053) Add missing features to H2 parser for CREATE/DROP TABLE

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5053:
---

Assignee: Vladimir Ozerov  (was: Vadim Opolski)

> Add missing features to H2 parser for CREATE/DROP TABLE
> ---
>
> Key: IGNITE-5053
> URL: https://issues.apache.org/jira/browse/IGNITE-5053
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> We need to {{AFFINITY KEY}} attribute. 
> Final name is yet to be defined. May be we should have several synonyms 
> resembling other databases to make migration to Ignite easier.



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

[jira] [Assigned] (IGNITE-5053) Add missing features to H2 parser for CREATE/DROP TABLE

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5053:
---

Assignee: Vadim Opolski  (was: Vladimir Ozerov)

> Add missing features to H2 parser for CREATE/DROP TABLE
> ---
>
> Key: IGNITE-5053
> URL: https://issues.apache.org/jira/browse/IGNITE-5053
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vadim Opolski
>  Labels: important
> Fix For: 2.1
>
>
> We need to {{AFFINITY KEY}} attribute. 
> Final name is yet to be defined. May be we should have several synonyms 
> resembling other databases to make migration to Ignite easier.



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

[jira] [Commented] (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:comment-tabpanel=16020970#comment-16020970
 ] 

Taras Ledkov commented on IGNITE-5163:
--

Fixed, waiting for 
[tests|http://195.239.208.174/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F1912%2Fhead].

> 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] [Commented] (IGNITE-5264) DDL operations must operate on per-schema basis

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5264:
-

Tests looks fine.

> DDL operations must operate on per-schema basis
> ---
>
> Key: IGNITE-5264
> URL: https://issues.apache.org/jira/browse/IGNITE-5264
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently we rely on cache name in schema operations. Schema should be used 
> instead:
> 1) Start missing caches in case of "TABLE NOT FOUND" and "INDEX NOT FOUND" 
> errors as well;
> 2) Pass schema name to {{SchemaChangeOperation}} instead of cache name.
> 3) Concurrency control on per-schema basis in {{GridQueryProcessor}}.



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

[jira] [Created] (IGNITE-5280) SparseDistributedMatrix refactorig

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5280:
--

 Summary: SparseDistributedMatrix refactorig
 Key: IGNITE-5280
 URL: https://issues.apache.org/jira/browse/IGNITE-5280
 Project: Ignite
  Issue Type: Sub-task
Reporter: Yury Babak
Assignee: Yury Babak


We must refactor SparseDistributedMatrix for decrease communication during 
computations.



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

[jira] [Created] (IGNITE-5279) DDL: Improve test coverage for objects with different cases (upper/lower)

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5279:
---

 Summary: DDL: Improve test coverage for objects with different 
cases (upper/lower)
 Key: IGNITE-5279
 URL: https://issues.apache.org/jira/browse/IGNITE-5279
 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-5278) BLAS implementation

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5278:
--

 Summary: BLAS implementation
 Key: IGNITE-5278
 URL: https://issues.apache.org/jira/browse/IGNITE-5278
 Project: Ignite
  Issue Type: Sub-task
Reporter: Yury Babak
Assignee: Artem Malykh


We need BLAS implementation for local computations.



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

[jira] [Commented] (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:comment-tabpanel=16020931#comment-16020931
 ] 

Vladimir Ozerov commented on IGNITE-5163:
-

[~tledkov-gridgain], my comments: 
1) {{JdbcConnection.ctor}} - no validation for host (null, empty string)
2) {{JdbcConnectionSelfTest}} - not included into any suite.

> 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] [Created] (IGNITE-5277) Asynchronously establish connection to all the needed nodes in IgniteH2Indexing.send()

[Sergi Vladykin (JIRA)]

Sergi Vladykin created IGNITE-5277:
--

 Summary: Asynchronously establish connection to all the needed 
nodes in IgniteH2Indexing.send()
 Key: IGNITE-5277
 URL: https://issues.apache.org/jira/browse/IGNITE-5277
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergi Vladykin


it's only a minor optimization until the point when establishing each 
connection takes 3-4 seconds, and we establish 32 of them in sequence.  At that 
point it becomes a serious issue: the customer cannot run SQL queries from 
their development machines



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

[jira] [Created] (IGNITE-5275) Create SQL listener configuration based on OdbcConfiguration

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5275:
---

 Summary: Create SQL listener configuration based on 
OdbcConfiguration
 Key: IGNITE-5275
 URL: https://issues.apache.org/jira/browse/IGNITE-5275
 Project: Ignite
  Issue Type: Task
  Components: odbc, sql
Reporter: Vladimir Ozerov
 Fix For: 2.1


We need to introduce new configuration API which will be applicable for both 
ODBC and JDBC drivers.



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

[jira] [Created] (IGNITE-5274) DLL: use schema for CREATE TABLE and DROP TABLE operations in GridQueryProcessor

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5274:
---

 Summary: DLL: use schema for CREATE TABLE and DROP TABLE 
operations in GridQueryProcessor
 Key: IGNITE-5274
 URL: https://issues.apache.org/jira/browse/IGNITE-5274
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1






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

[jira] [Created] (IGNITE-5273) MemoryMetrics API improvements to be ported to .NET

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5273:
---

 Summary: MemoryMetrics API improvements to be ported to .NET
 Key: IGNITE-5273
 URL: https://issues.apache.org/jira/browse/IGNITE-5273
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Sergey Chugunov


Improvements already made for linked ticket need to be ported on .NET side.



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

[jira] [Commented] (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:comment-tabpanel=16020915#comment-16020915
 ] 

Vladimir Ozerov commented on IGNITE-5052:
-

[~al.psc], my comments:
1) {{H2DynamicTableSelfTest}} - invalid JavaDocs on methods
2) Please confirm that TC state is acceptable.

> 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] [Assigned] (IGNITE-4777) Web Console: Add notification on 'Download project' button

[Vica Abramova (JIRA)]

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

Vica Abramova reassigned IGNITE-4777:
-

Assignee: Alexey Kuznetsov  (was: Vica Abramova)

> Web Console: Add notification on 'Download project' button
> --
>
> Key: IGNITE-4777
> URL: https://issues.apache.org/jira/browse/IGNITE-4777
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Attachments: Attention-alert.png
>
>
> After the configuration user need to download project and run it to get the 
> result. Let's notify about this!
> Also in this task we need to revise tips. And improve instructions for new 
> users.



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

[jira] [Commented] (IGNITE-4777) Web Console: Add notification on 'Download project' button

[Vica Abramova (JIRA)]

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

Vica Abramova commented on IGNITE-4777:
---

[~kuaw26], please give the correct text.

> Web Console: Add notification on 'Download project' button
> --
>
> Key: IGNITE-4777
> URL: https://issues.apache.org/jira/browse/IGNITE-4777
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
> Attachments: Attention-alert.png
>
>
> After the configuration user need to download project and run it to get the 
> result. Let's notify about this!
> Also in this task we need to revise tips. And improve instructions for new 
> users.



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

[jira] [Updated] (IGNITE-4777) Web Console: Add notification on 'Download project' button

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-4777:
--
Attachment: Attention-alert.png

> Web Console: Add notification on 'Download project' button
> --
>
> Key: IGNITE-4777
> URL: https://issues.apache.org/jira/browse/IGNITE-4777
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
> Attachments: Attention-alert.png
>
>
> After the configuration user need to download project and run it to get the 
> result. Let's notify about this!
> Also in this task we need to revise tips. And improve instructions for new 
> users.



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

[jira] [Assigned] (IGNITE-5205) Optimize SQL messaging

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin reassigned IGNITE-5205:
--

Assignee: Sergi Vladykin  (was: Sergey Kalashnikov)

> Optimize SQL messaging
> --
>
> Key: IGNITE-5205
> URL: https://issues.apache.org/jira/browse/IGNITE-5205
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergi Vladykin
>Assignee: Sergi Vladykin
> Fix For: 2.1
>
>
> Currently we create Message object for each H2 Value being sent or received 
> over the wire. Lets write and read them directly without intermediate 
> conversions.



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

[jira] [Closed] (IGNITE-5248) Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk closed IGNITE-5248.


> Best effort check to detect a 32-bit JVM trying to allocate too big amount of 
> memory
> 
>
> Key: IGNITE-5248
> URL: https://issues.apache.org/jira/browse/IGNITE-5248
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Assignee: Wuwei Lin
>  Labels: important, newbie
> Fix For: 2.1
>
>
> A follow-up on the user list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html
> We can catch the IllegalArgumentException and see if the allocated space 
> exceeds 2Gb. In this case, we should suggest that user check that he is 
> running a 64-bit JVM.



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

[jira] [Commented] (IGNITE-5248) Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5248:


Github user asfgit closed the pull request at:

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


> Best effort check to detect a 32-bit JVM trying to allocate too big amount of 
> memory
> 
>
> Key: IGNITE-5248
> URL: https://issues.apache.org/jira/browse/IGNITE-5248
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Assignee: Wuwei Lin
>  Labels: important, newbie
> Fix For: 2.1
>
>
> A follow-up on the user list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html
> We can catch the IllegalArgumentException and see if the allocated space 
> exceeds 2Gb. In this case, we should suggest that user check that he is 
> running a 64-bit JVM.



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

[jira] [Commented] (IGNITE-5248) Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-5248:
--

Thanks, for the contribution, Wuwei! I merged your patch with minor changes.

> Best effort check to detect a 32-bit JVM trying to allocate too big amount of 
> memory
> 
>
> Key: IGNITE-5248
> URL: https://issues.apache.org/jira/browse/IGNITE-5248
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Assignee: Wuwei Lin
>  Labels: important, newbie
> Fix For: 2.1
>
>
> A follow-up on the user list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html
> We can catch the IllegalArgumentException and see if the allocated space 
> exceeds 2Gb. In this case, we should suggest that user check that he is 
> running a 64-bit JVM.



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

[jira] [Commented] (IGNITE-5264) DDL operations must operate on per-schema basis

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5264:


GitHub user devozerov opened a pull request:

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

IGNITE-5264



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

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

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

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


commit e04c785c3ef7426a8aa11658655dfc43511a9836
Author: devozerov 
Date:   2017-05-22T14:26:43Z

Preparing.

commit 03daf6dc305a010b4451d61e7f01a717c67fe8c5
Author: devozerov 
Date:   2017-05-23T07:29:57Z

Removed schema key.

commit a640720c6db52c4d2ea7ddf1523a97cab267fef4
Author: devozerov 
Date:   2017-05-23T08:00:08Z

Finalization.

commit 217ba052f5578b2612bd9525a1095a0bb9b06c43
Author: devozerov 
Date:   2017-05-23T08:30:30Z

WOrks fine.




> DDL operations must operate on per-schema basis
> ---
>
> Key: IGNITE-5264
> URL: https://issues.apache.org/jira/browse/IGNITE-5264
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently we rely on cache name in schema operations. Schema should be used 
> instead:
> 1) Start missing caches in case of "TABLE NOT FOUND" and "INDEX NOT FOUND" 
> errors as well;
> 2) Pass schema name to {{SchemaChangeOperation}} instead of cache name.
> 3) Concurrency control on per-schema basis in {{GridQueryProcessor}}.



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

[jira] [Closed] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-4951.
---

> Discontinue AffintiyKeyMapper interface
> ---
>
> Key: IGNITE-4951
> URL: https://issues.apache.org/jira/browse/IGNITE-4951
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
>




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

[jira] [Updated] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4951:

Fix Version/s: (was: 2.1)
   2.2

> Discontinue AffintiyKeyMapper interface
> ---
>
> Key: IGNITE-4951
> URL: https://issues.apache.org/jira/browse/IGNITE-4951
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
>




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

[jira] [Resolved] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4951.
-
Resolution: Won't Fix

This feature appears to be useful still.

> Discontinue AffintiyKeyMapper interface
> ---
>
> Key: IGNITE-4951
> URL: https://issues.apache.org/jira/browse/IGNITE-4951
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
> Fix For: 2.2
>
>




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