[jira] [Assigned] (IGNITE-5366) Web Console: user notifications

2017-06-07 Thread Andrey Novikov (JIRA) 

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

Andrey Novikov reassigned IGNITE-5366:
--

 Assignee: Pavel Konstantinov  (was: Andrey Novikov)
Fix Version/s: 2.1
Affects Version/s: 2.0

Added editor for user notification.
[~pkonstantinov], can you please check modal dialogs, notification?

> Web Console: user notifications
> ---
>
> Key: IGNITE-5366
> URL: https://issues.apache.org/jira/browse/IGNITE-5366
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.0
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
> Fix For: 2.1
>
>
> Web console needs a way to notify all users, for example about upcoming 
> version updates.
> What to do:
> 1. Add a way for admin to manage notifications.
> 2. Display notifications in app header in style similar to "assummed 
> identity" notification.



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

[jira] [Created] (IGNITE-5445) ServerImpl can't process NodeFailedMessage about itself

2017-06-07 Thread Alexander Belyak (JIRA) 
Alexander Belyak created IGNITE-5445:


 Summary: ServerImpl can't process NodeFailedMessage about itself
 Key: IGNITE-5445
 URL: https://issues.apache.org/jira/browse/IGNITE-5445
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.9
Reporter: Alexander Belyak
Priority: Minor
 Fix For: 2.1


If for some reason (GC pause or heavy load) node get NodeLeft(FAILED) message 
about itself - it can't correctly handle it, because it call 
TcpDiscoveryNodesRing.removeNode with local node id and get assertion error.
I think - node should correctly determine such event and throw something like 
"segmented" event and so on.



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

[jira] [Assigned] (IGNITE-3242) JMX MBean for ignite-cassandra module

2017-06-07 Thread Igor Rudyak (JIRA) 

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

Igor Rudyak reassigned IGNITE-3242:
---

Assignee: Igor Rudyak  (was: Eugene Kirin)

> JMX MBean for ignite-cassandra module
> -
>
> Key: IGNITE-3242
> URL: https://issues.apache.org/jira/browse/IGNITE-3242
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Igor Rudyak
>Assignee: Igor Rudyak
>
> Ignite-Cassandra module should contain JMX MBean, allowing to monitor such 
> custom metrics (for each Ignite cache and summary):
> 1. Size of Cassandra sessions pool
> 2. Number of times establishing/closing Cassandra sessions
> 3. Number of:
>   * Records *READ* from Cassandra
>   * Records *WRITTEN* to Casandra
>   * Failed *READ* operations
>   * Failed *WRITE* operations
> 4. Min/Max/Average number (and percentage) of attempts to retry failed 
> *READ/WRITE/DELETE* operation until it succeed
> 5. Min/Max/Average/Summary sleep time until failed *READ/WRITE/DELETE* 
> operation succeed after several attempts
> 6. Average time of *READ* operation
> 7. Average time of *WRITE* operation



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

[jira] [Commented] (IGNITE-5229) Specify caches when using Redis protocol

2017-06-07 Thread Roman Shtykh (JIRA) 

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

Roman Shtykh commented on IGNITE-5229:
--

[~anovikov] Can you please review this feature?

> Specify caches when using Redis protocol
> 
>
> Key: IGNITE-5229
> URL: https://issues.apache.org/jira/browse/IGNITE-5229
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 2.1
>
>
> Currently there's no way to switch caches -- all requests go to 'default'.
> _Note that this is the switch needed only for a subset of Redis data 
> structures (currently only STRINGs) -- for SETs and HASHTABLEs caches will be 
> specified as keys (see IGNITE-5241)_
> The solution to be implemented:
> 1. A user specifies the cache configuration (template) with predefined name 
> ‘redis-ignite-internal-cache’
> 2. Then issues ‘SELECT n’, and uses ‘redis-ignite-internal-cache-n’.
> Caches are configurable by providing a template.
> http://apache-ignite-developers.2346864.n4.nabble.com/Changing-cache-name-when-using-Redis-protocol-td17727.html



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

[jira] [Resolved] (IGNITE-5428) Failed to build ignite-jta because a dependent library is not downloadable

2017-06-07 Thread Kengo Seki (JIRA) 

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

Kengo Seki resolved IGNITE-5428.

Resolution: Not A Problem

Sorry, it seems that was a temporary problem. Now the build succeeds so I'm 
closing it.

> Failed to build ignite-jta because a dependent library is not downloadable
> --
>
> Key: IGNITE-5428
> URL: https://issues.apache.org/jira/browse/IGNITE-5428
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.0
>Reporter: Kengo Seki
>
> I tried to build the master branch and got the following error. Maven 
> repository ow2.org providing org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018 
> seems down.
> {code}
> $ mvn clean package -DskipTests
> (snip)
> [INFO] 
> 
> [INFO] Building ignite-jta 2.1.0-SNAPSHOT
> [INFO] 
> 
> Downloading: 
> http://maven.ow2.org/maven2/org/jacorb/jacorb/2.2.3-jonas-patch-20071018/jacorb-2.2.3-jonas-patch-20071018.pom
> Downloading: 
> http://maven.ow2.org/maven2/org/jacorb/jacorb-idl/2.2.3-jonas-patch-20071018/jacorb-idl-2.2.3-jonas-patch-20071018.pom
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ignite-apache-license-gen .. SUCCESS [  4.212 
> s]
> [INFO] ignite-tools ... SUCCESS [ 28.157 
> s]
> [INFO] ignite-core  SUCCESS [04:29 
> min]
> [INFO] ignite-log4j ... SUCCESS [  6.677 
> s]
> [INFO] ignite-indexing  SUCCESS [ 27.618 
> s]
> [INFO] ignite-urideploy ... SUCCESS [  7.765 
> s]
> [INFO] ignite-spring .. SUCCESS [  9.357 
> s]
> [INFO] ignite-hadoop .. SUCCESS [ 31.444 
> s]
> [INFO] ignite-extdata-p2p . SUCCESS [  8.357 
> s]
> [INFO] ignite-extdata-uri-dep . SUCCESS [  3.947 
> s]
> [INFO] ignite-extdata-uri . SUCCESS [  1.689 
> s]
> [INFO] ignite-rest-http ... SUCCESS [  6.224 
> s]
> [INFO] ignite-clients . SUCCESS [  3.442 
> s]
> [INFO] ignite-spring-data . SUCCESS [  6.970 
> s]
> [INFO] ignite-web . SUCCESS [  7.636 
> s]
> [INFO] ignite-aop . SUCCESS [  6.271 
> s]
> [INFO] ignite-ssh . SUCCESS [  8.456 
> s]
> [INFO] ignite-jta . FAILURE [ 12.698 
> s]
> [INFO] ignite-aws . SKIPPED
> [INFO] ignite-log4j2 .. SKIPPED
> [INFO] ignite-slf4j ... SKIPPED
> [INFO] ignite-jcl . SKIPPED
> [INFO] ignite-codegen . SKIPPED
> [INFO] ignite-gce . SKIPPED
> [INFO] ignite-cloud ... SKIPPED
> [INFO] ignite-mesos ... SKIPPED
> [INFO] ignite-kafka ... SKIPPED
> [INFO] ignite-flume ... SKIPPED
> [INFO] ignite-yarn  SKIPPED
> [INFO] ignite-jms11 ... SKIPPED
> [INFO] ignite-twitter . SKIPPED
> [INFO] ignite-mqtt  SKIPPED
> [INFO] ignite-zookeeper ... SKIPPED
> [INFO] ignite-hibernate-core .. SKIPPED
> [INFO] ignite-camel ... SKIPPED
> [INFO] ignite-storm ... SKIPPED
> [INFO] ignite-osgi-paxlogging . SKIPPED
> [INFO] ignite-osgi-karaf .. SKIPPED
> [INFO] ignite-osgi  SKIPPED
> [INFO] ignite-appserver-test .. SKIPPED
> [INFO] ignite-websphere-test .. SKIPPED
> [INFO] ignite-cassandra ... SKIPPED
> [INFO] ignite-cassandra-store . SKIPPED
> [INFO] ignite-cassandra-serializers ... SKIPPED
> [INFO] ignite-flink ... SKIPPED
> [INFO] ignite-kubernetes

[jira] [Updated] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller

2017-06-07 Thread Valentin Kulichenko (JIRA) 

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

Valentin Kulichenko updated IGNITE-5444:

Attachment: BinaryObjectSingletonList.java

> Collections.singletonList is not properly serialized by binary marshaller
> -
>
> Key: IGNITE-5444
> URL: https://issues.apache.org/jira/browse/IGNITE-5444
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
> Fix For: 2.1
>
> Attachments: BinaryObjectSingletonList.java
>
>
> Test attached. {{Collections.singletonList}} is apparently serialized by 
> optimized marshaller, because when deserialized, it doesn't return collection 
> of binary objects, but rather collection of deserialized objects.
> Most likely the reason for this is that {{Collections.singletonList}} is not 
> recognized by {{BinaryUtils.knownCollection}} method.



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

[jira] [Created] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller

2017-06-07 Thread Valentin Kulichenko (JIRA) 
Valentin Kulichenko created IGNITE-5444:
---

 Summary: Collections.singletonList is not properly serialized by 
binary marshaller
 Key: IGNITE-5444
 URL: https://issues.apache.org/jira/browse/IGNITE-5444
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.0
Reporter: Valentin Kulichenko
 Fix For: 2.1
 Attachments: BinaryObjectSingletonList.java

Test attached. {{Collections.singletonList}} is apparently serialized by 
optimized marshaller, because when deserialized, it doesn't return collection 
of binary objects, but rather collection of deserialized objects.

Most likely the reason for this is that {{Collections.singletonList}} is not 
recognized by {{BinaryUtils.knownCollection}} method.



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

[jira] [Created] (IGNITE-5443) The bunch of javadoc warnings

2017-06-07 Thread Sergey Kozlov (JIRA) 
Sergey Kozlov created IGNITE-5443:
-

 Summary: The bunch of javadoc warnings
 Key: IGNITE-5443
 URL: https://issues.apache.org/jira/browse/IGNITE-5443
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.1
Reporter: Sergey Kozlov


{noformat}
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2226:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2226:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2253:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2253:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2658:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2658:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2685:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2685:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2172:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2172:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2199:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2199:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING] 
/home/teamcity/buildAgent/work/a239320d84866d7f/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:2604:
 warning - @inheritDoc used but getCacheId(long, int) does not override or 
implement any method.
[11:38:06]W: [org.apache.ignite:ignite-core] [WARNING]

[jira] [Updated] (IGNITE-5442) .NET: LINQ Conditional statement will fail for some types

2017-06-07 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn updated IGNITE-5442:
---
Fix Version/s: 2.1

> .NET: LINQ Conditional statement will fail for some types
> -
>
> Key: IGNITE-5442
> URL: https://issues.apache.org/jira/browse/IGNITE-5442
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Sergey Stronchinskiy
>Priority: Minor
>  Labels: .net, linq
> Fix For: 2.1
>
>
> Next code will fail:
> {code}
> var res = persons.Select(x => new {Foo = x.Key%2 == 0 ? 1 : (int?)null, 
> x.Value}).ToArray();
> {code}
> Fix: strip nullable type in {{SqlTypes}}



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

[jira] [Updated] (IGNITE-5442) .NET: LINQ Conditional statement will fail for some types

2017-06-07 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn updated IGNITE-5442:
---
Summary: .NET: LINQ Conditional statement will fail for some types  (was: 
Linq Conditional statement will fail for some types)

> .NET: LINQ Conditional statement will fail for some types
> -
>
> Key: IGNITE-5442
> URL: https://issues.apache.org/jira/browse/IGNITE-5442
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Sergey Stronchinskiy
>Priority: Minor
>  Labels: .net, linq
> Fix For: 2.1
>
>
> Next code will fail:
> {code}
> var res = persons.Select(x => new {Foo = x.Key%2 == 0 ? 1 : (int?)null, 
> x.Value}).ToArray();
> {code}
> Fix: strip nullable type in {{SqlTypes}}



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

[jira] [Created] (IGNITE-5442) Linq Conditional statement will fail for some types

2017-06-07 Thread Sergey Stronchinskiy (JIRA) 
Sergey Stronchinskiy created IGNITE-5442:


 Summary: Linq Conditional statement will fail for some types
 Key: IGNITE-5442
 URL: https://issues.apache.org/jira/browse/IGNITE-5442
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Reporter: Sergey Stronchinskiy
Priority: Minor


Next code will fail:

{code}
var res = persons.Select(x => new {Foo = x.Key%2 == 0 ? 1 : (int?)null, 
x.Value}).ToArray();
{code}

Fix: strip nullable type in {{SqlTypes}}



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

[jira] [Commented] (IGNITE-4370) ODBC: Implement DML operations with parameters in batch.

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

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

ASF GitHub Bot commented on IGNITE-4370:


GitHub user isapego opened a pull request:

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

IGNITE-4370: Implemented writing of batch of parameters for ODBC.



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

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

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

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


commit 19499050347d18fc2625d1efb881436c42d3916d
Author: Igor Sapego 
Date:   2017-06-05T15:09:50Z

IGNITE-4370: Added SQL_PARAM_ARRAY_ROW_COUNTS param

commit bdc68cca6a939e800323382f69f765ba84d97a8a
Author: Igor Sapego 
Date:   2017-06-05T15:55:20Z

IGNITE-4370: Added SQL_PARAM_ARRAY_SELECTS param

commit ee040b4d9b04233c91853ac4bef2d60b86e828c5
Author: Igor Sapego 
Date:   2017-06-06T16:15:37Z

IGNITE-4370: Parameter refactored

commit cc60a056331d5a9162e710d41f208c86a4b5d27c
Author: Igor Sapego 
Date:   2017-06-06T16:32:43Z

IGNITE-4370: Fix

commit 51a01e2b772c316e2c5e3999014c146cddcde87c
Author: Igor Sapego 
Date:   2017-06-07T08:44:03Z

IGNITE-4370: Offset-related refactoring.

commit 13d217776f26ab2be9a572d46b432175c8ec613e
Author: Igor Sapego 
Date:   2017-06-07T08:53:42Z

IGNITE-4370: Implemented writing of batch of parameters.

commit c1b8b61b8087be5d6dffe2cf4df7be26ecad125f
Author: Igor Sapego 
Date:   2017-06-07T10:01:47Z

IGNITE-4370 refactored Parameter set writing

commit 745619b847d7a5776565042e92eacf0e93df10ab
Author: Igor Sapego 
Date:   2017-06-07T12:46:32Z

IGNITE-4370: OdbcQueryExecuteBatchStartRequest implemented.

commit 3a7dd6044c86bd10c2dcd45907d4dd4b2a6e33b2
Author: Igor Sapego 
Date:   2017-06-07T14:39:13Z

IGNITE-4370: Safe

commit c63120b892e64a6a19ed78d80d099f21a2f97ffa
Author: Igor Sapego 
Date:   2017-06-07T18:36:40Z

IGNITE-4370: Implemented continuation.




> ODBC: Implement DML operations with parameters in batch.
> 
>
> Key: IGNITE-4370
> URL: https://issues.apache.org/jira/browse/IGNITE-4370
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: important
> Fix For: 2.1
>
>
> Currently, if user wants for example to insert 20k records they need to call 
> {{SQLExecute}} for the 20k times. More than that, internally, we transmit and 
> execute the same SQL query 20k times. This is a huge overhead. We should only 
> transfer sql query once, transfer all the parameters in a batch and then 
> execute it once using some fast, possibly internal API.



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

[jira] [Assigned] (IGNITE-5385) Get rid of discovery custom message on exchange completion

2017-06-07 Thread Alexei Scherbakov (JIRA) 

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

Alexei Scherbakov reassigned IGNITE-5385:
-

Assignee: Alexei Scherbakov  (was: Yakov Zhdanov)

> Get rid of discovery custom message on exchange completion
> --
>
> Key: IGNITE-5385
> URL: https://issues.apache.org/jira/browse/IGNITE-5385
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Yakov Zhdanov
>Assignee: Alexei Scherbakov
>Priority: Blocker
>  Labels: performance
> Fix For: 2.1
>
>
> Currently if late affinity assignment is on we send full partition map as a 
> custom message to make sure all nodes get it. With greater number of nodes 
> and caches this can cause significant slowdowns.
> We suggest to move sending to communication. In this case scenario with 
> coordinator failure requires special handling, since in this case some nodes 
> may receive full map, complete exchange and proceed with cache operations, 
> while others may not received full map yet. In this case full map should be 
> resend from new coordinator - it should be recalculated if none has received 
> one from former coordinator or should be requested from one of the lucky 
> receivers to get forwarded to other nodes.



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

[jira] [Created] (IGNITE-5441) .NET: Stack trace is lost for exceptions in ICacheStore

2017-06-07 Thread Pavel Tupitsyn (JIRA) 
Pavel Tupitsyn created IGNITE-5441:
--

 Summary: .NET: Stack trace is lost for exceptions in ICacheStore
 Key: IGNITE-5441
 URL: https://issues.apache.org/jira/browse/IGNITE-5441
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.1


When exception happens during cache store invocation ({{Write}} method in 
particular), Java stack trace is lost, original .NET stack trace is lost, 
exception is quite useless. See {{CheckCustomStoreError}} in {{TestLoadCache}}, 
this test should be improved to make sure we preserve all information.



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

[jira] [Comment Edited] (IGNITE-5170) .NET: Compute peer deployment example

2017-06-07 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn edited comment on IGNITE-5170 at 6/7/17 3:29 PM:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-5170 .NET: Compute peer deployment example



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

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

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

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


was (Author: githubbot):
GitHub user ptupitsyn opened a pull request:

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

IGNITE-5170 .NET: Compute peer deployment example



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

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

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

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


commit ec70aecd30d2ccfcc715b02170ae42f9815c7dd3
Author: Pavel Tupitsyn 
Date:   2017-06-07T13:03:44Z

IGNITE-5170 .NET: Compute peer deployment example - LINQPad

commit e82bbff180d9583beaa71bceb0af3effde2eea0a
Author: Pavel Tupitsyn 
Date:   2017-06-07T13:31:18Z

wip

commit fd7fb38cff047bf9e44e717f5a1817a274158ea0
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:03:00Z

Remove AssemblyFileVersion

commit ce2b29122102b06c7219041dc8693ab53c445eae
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:09:03Z

Make examples 1.0.*

commit 3cd25dc77d4673fc1cd4452f22f3386e1d2f92f9
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:21:16Z

wip

commit eb9db9905711ed0e63ae3905136a6c12f314524b
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:43:04Z

wip

commit db4ce7be8727e053d32f8fffcb8df75ab46bd519
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:44:43Z

wip

commit a09e126b034013f89552f550e220ec059bcf5a47
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:50:04Z

wip

commit 548d607d1292f0c829ce6b3be4df6dd73a8e4302
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:54:10Z

wip

commit e6296d50dea5a5bdaadeefcfb2ab71d8a0098d02
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:57:23Z

Update test

commit 0785ad1407e391fcdaf358c8af5acf4f84e956ea
Author: Pavel Tupitsyn 
Date:   2017-06-07T15:03:38Z

wip

commit da6eabcf138d305a63b4b395f16e07f714114628
Author: Pavel Tupitsyn 
Date:   2017-06-07T15:09:30Z

update docs

commit 94944aa1ad630a1fac02b3181823c9c56f4b62f9
Author: Pavel Tupitsyn 
Date:   2017-06-07T15:12:43Z

cleanup




> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * Add example for IGNITE-2492.
> * Enable peer loading in LINQPad compute example so it works with a 
> standalone node (update docs there), explain how to run Apache.Ignite.exe 
> from NuGet



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

[jira] [Commented] (IGNITE-5170) .NET: Compute peer deployment example

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

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

ASF GitHub Bot commented on IGNITE-5170:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-5170 .NET: Compute peer deployment example



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

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

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

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


commit ec70aecd30d2ccfcc715b02170ae42f9815c7dd3
Author: Pavel Tupitsyn 
Date:   2017-06-07T13:03:44Z

IGNITE-5170 .NET: Compute peer deployment example - LINQPad

commit e82bbff180d9583beaa71bceb0af3effde2eea0a
Author: Pavel Tupitsyn 
Date:   2017-06-07T13:31:18Z

wip

commit fd7fb38cff047bf9e44e717f5a1817a274158ea0
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:03:00Z

Remove AssemblyFileVersion

commit ce2b29122102b06c7219041dc8693ab53c445eae
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:09:03Z

Make examples 1.0.*

commit 3cd25dc77d4673fc1cd4452f22f3386e1d2f92f9
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:21:16Z

wip

commit eb9db9905711ed0e63ae3905136a6c12f314524b
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:43:04Z

wip

commit db4ce7be8727e053d32f8fffcb8df75ab46bd519
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:44:43Z

wip

commit a09e126b034013f89552f550e220ec059bcf5a47
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:50:04Z

wip

commit 548d607d1292f0c829ce6b3be4df6dd73a8e4302
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:54:10Z

wip

commit e6296d50dea5a5bdaadeefcfb2ab71d8a0098d02
Author: Pavel Tupitsyn 
Date:   2017-06-07T14:57:23Z

Update test

commit 0785ad1407e391fcdaf358c8af5acf4f84e956ea
Author: Pavel Tupitsyn 
Date:   2017-06-07T15:03:38Z

wip

commit da6eabcf138d305a63b4b395f16e07f714114628
Author: Pavel Tupitsyn 
Date:   2017-06-07T15:09:30Z

update docs

commit 94944aa1ad630a1fac02b3181823c9c56f4b62f9
Author: Pavel Tupitsyn 
Date:   2017-06-07T15:12:43Z

cleanup




> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * Add example for IGNITE-2492.
> * Enable peer loading in LINQPad compute example so it works with a 
> standalone node (update docs there), explain how to run Apache.Ignite.exe 
> from NuGet



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

[jira] [Updated] (IGNITE-5440) JDBC thin: support SQL escape processing

2017-06-07 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov updated IGNITE-5440:
-
Summary: JDBC thin: support SQL escape processing  (was: JDBC thin: support 
SQL esacpe processing)

> JDBC thin: support SQL escape processing
> 
>
> Key: IGNITE-5440
> URL: https://issues.apache.org/jira/browse/IGNITE-5440
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
> Fix For: 2.2
>
>
> The method {{Statement.setEscapeProcessing}} must be supported.



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

[jira] [Created] (IGNITE-5440) JDBC thin: support SQL esacpe processing

2017-06-07 Thread Taras Ledkov (JIRA) 
Taras Ledkov created IGNITE-5440:


 Summary: JDBC thin: support SQL esacpe processing
 Key: IGNITE-5440
 URL: https://issues.apache.org/jira/browse/IGNITE-5440
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
 Fix For: 2.2


The method {{Statement.setEscapeProcessing}} must be supported.



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

[jira] [Comment Edited] (IGNITE-5170) .NET: Compute peer deployment example

2017-06-07 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn edited comment on IGNITE-5170 at 6/7/17 2:11 PM:


To demonstrate peer deployment we need to make sure that any cnanges that user 
introduces while playing with examples is reflected on remote nodes that are 
kept running
* LINQPad: this just works, since LINQPad generates unique assembly name on 
every build
* VS Examples: we should add {{*}} to the assembly version attribute, so that 
each build has unique version. {{[assembly: AssemblyVersion("1.0.*")]}} won't 
be replaced by Maven release build, since regex expects digits.


was (Author: ptupitsyn):
To demonstrate peer deployment we need to make sure that any cnanges that user 
introduces while playing with examples is reflected on remote nodes that are 
kept running
* LINQPad: this just works, since LINQPad generates unique assembly name on 
every build
* VS Examples: we should add {{*}} to the assembly version attribute, so that 
each build has unique version

> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * Add example for IGNITE-2492.
> * Enable peer loading in LINQPad compute example so it works with a 
> standalone node (update docs there), explain how to run Apache.Ignite.exe 
> from NuGet



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

[jira] [Assigned] (IGNITE-5432) Test IgniteMarshallerCacheClassNameConflictTest failed

2017-06-07 Thread Alexey Ivanov (JIRA) 

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

Alexey Ivanov reassigned IGNITE-5432:
-

Assignee: Alexey Ivanov

>  Test IgniteMarshallerCacheClassNameConflictTest failed
> ---
>
> Key: IGNITE-5432
> URL: https://issues.apache.org/jira/browse/IGNITE-5432
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexey Ivanov
>Assignee: Alexey Ivanov
> Fix For: 2.1
>
>
> Test suit:
> IgniteBinarySimpleNameMapperBasicTestSuite
> Test:
> IgniteMarshallerCacheClassNameConflictTest



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

[jira] [Assigned] (IGNITE-5026) getOrCreateCaches() hangs if any exception in GridDhtPartitionsExchangeFuture.init()

2017-06-07 Thread Alexey Kuznetsov (JIRA) 

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

Alexey Kuznetsov reassigned IGNITE-5026:


Assignee: Alexey Kuznetsov

> getOrCreateCaches() hangs if any exception in 
> GridDhtPartitionsExchangeFuture.init()
> 
>
> Key: IGNITE-5026
> URL: https://issues.apache.org/jira/browse/IGNITE-5026
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9, 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
>
> Any exception has been thrown by {{GridDhtPartitionsExchangeFuture.init()}} 
> causes to wait indefinitely {{GridCompoundFuture}} returned by 
> {{GridCacheProcessor.dynamicStartCaches()}}.
> Reproduced by 
> {{IgniteDynamicCacheStartSelfTest.testGetOrCreateCollectionExceptional()}}



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

[jira] [Created] (IGNITE-5439) JDBC thin: support query cancel

2017-06-07 Thread Taras Ledkov (JIRA) 
Taras Ledkov created IGNITE-5439:


 Summary: JDBC thin: support query cancel
 Key: IGNITE-5439
 URL: https://issues.apache.org/jira/browse/IGNITE-5439
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
 Fix For: 2.2


The JDBC {{Statement.cancel}} method must be supported.



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

[jira] [Commented] (IGNITE-5170) .NET: Compute peer deployment example

2017-06-07 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn commented on IGNITE-5170:


To demonstrate peer deployment we need to make sure that any cnanges that user 
introduces while playing with examples is reflected on remote nodes that are 
kept running
* LINQPad: this just works, since LINQPad generates unique assembly name on 
every build
* VS Examples: we should add {{*}} to the assembly version attribute, so that 
each build has unique version

> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * Add example for IGNITE-2492.
> * Enable peer loading in LINQPad compute example so it works with a 
> standalone node (update docs there), explain how to run Apache.Ignite.exe 
> from NuGet



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

[jira] [Assigned] (IGNITE-5371) Persistence for text indices

2017-06-07 Thread Andrew Mashenkov (JIRA) 

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

Andrew Mashenkov reassigned IGNITE-5371:


Assignee: Andrew Mashenkov

> Persistence for text indices
> 
>
> Key: IGNITE-5371
> URL: https://issues.apache.org/jira/browse/IGNITE-5371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexei Scherbakov
>Assignee: Andrew Mashenkov
> Fix For: 2.2
>
>
> Currently text indices (used with TextQuery) recide in java heap and do not 
> survive node restarts. With the incoming persistence feature in 2.1  this 
> behavior is uncceptable.
> We need to implement LuceneDirectory based on PageMemory to make indices 
> persistable and turn Ignite into full fledged full text search engine.



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

[jira] [Updated] (IGNITE-5438) JDBC thin: support query timeout

2017-06-07 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov updated IGNITE-5438:
-
Summary: JDBC thin: support query timeout  (was: DBC thin: support query 
timeout)

> JDBC thin: support query timeout
> 
>
> Key: IGNITE-5438
> URL: https://issues.apache.org/jira/browse/IGNITE-5438
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
> Fix For: 2.2
>
>
> The {{setQueryTimeout}} method of JDBC {{Statement}} must be supported.



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

[jira] [Updated] (IGNITE-5437) SQL: Incorrect partition is derived from query when argument type differs from column type

2017-06-07 Thread Sergey Kalashnikov (JIRA) 

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

Sergey Kalashnikov updated IGNITE-5437:
---
Attachment: BugReproducer5437.java

> SQL: Incorrect partition is derived from query when argument type differs 
> from column type
> --
>
> Key: IGNITE-5437
> URL: https://issues.apache.org/jira/browse/IGNITE-5437
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Sergey Kalashnikov
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
> Attachments: BugReproducer5437.java
>
>
> Ignite SQL attempts to derive partition from the query in certain cases and 
> sends the map queries only to nodes which have those calculated partitions.
> Such queries are limited to contain equality conditions over key or affinity 
> key columns at the left and constant or parameter at the right.
> When the type of argument does not match the column type, the calculation 
> leads to wrong result.
> For example, the following query produces incomplete results when _key column 
> is INTEGER and the argument is CHAR. 
> select * from test where _key = ?
> However, this is valid and resultive query for H2, which does implicit 
> conversion in such cases.



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

[jira] [Assigned] (IGNITE-5437) SQL: Incorrect partition is derived from query when argument type differs from column type

2017-06-07 Thread Sergey Kalashnikov (JIRA) 

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

Sergey Kalashnikov reassigned IGNITE-5437:
--

Assignee: Sergey Kalashnikov

> SQL: Incorrect partition is derived from query when argument type differs 
> from column type
> --
>
> Key: IGNITE-5437
> URL: https://issues.apache.org/jira/browse/IGNITE-5437
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Sergey Kalashnikov
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
>
> Ignite SQL attempts to derive partition from the query in certain cases and 
> sends the map queries only to nodes which have those calculated partitions.
> Such queries are limited to contain equality conditions over key or affinity 
> key columns at the left and constant or parameter at the right.
> When the type of argument does not match the column type, the calculation 
> leads to wrong result.
> For example, the following query produces incomplete results when _key column 
> is INTEGER and the argument is CHAR. 
> select * from test where _key = ?
> However, this is valid and resultive query for H2, which does implicit 
> conversion in such cases.



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

[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-5434:

Labels: important  (was: )

> Yardstick sql benchmarks broken on Ignite-5267 branch
> -
>
> Key: IGNITE-5434
> URL: https://issues.apache.org/jira/browse/IGNITE-5434
> Project: Ignite
>  Issue Type: Bug
>  Components: sql, yardstick
>Affects Versions: 2.1
>Reporter: Aleksey Chetaev
>Priority: Critical
>  Labels: important
> Fix For: 2.1
>
>
> Yardstick benchmarks:
> * sql-query
> * sql-query-join
> * sql-query-put 
> broken in  Ignite-5267 branch, in master all ok. 
> Exception:
> <00:39:22> Starting warmup.  
>   
>   
>   
>  
> Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] 
>   
>   
>   
>  
> ERROR: Shutting down benchmark driver to unexpected exception.
>   
>   
>   
>  
> Type '--help' for usage.  
>   
>   
>   
>  
> javax.cache.CacheException: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
> "query"."Person" WHERE salary >= ? and salary <= ?
>   
>
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807)
>   
>   
>  
> at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90)
>   
>   
>
> at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64)
>   
>   
>
> at 
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)   
>   
>   
>   
>   
> at java.lang.Thread.run(Thread.java:745)  
>   
>   
>   
>  
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
> "query"."Person" WHERE salary >= ? and salary <= ?
>   
> 
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291)
>   
>

[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-5434:

Fix Version/s: 2.1

> Yardstick sql benchmarks broken on Ignite-5267 branch
> -
>
> Key: IGNITE-5434
> URL: https://issues.apache.org/jira/browse/IGNITE-5434
> Project: Ignite
>  Issue Type: Bug
>  Components: sql, yardstick
>Affects Versions: 2.1
>Reporter: Aleksey Chetaev
>Priority: Critical
>  Labels: important
> Fix For: 2.1
>
>
> Yardstick benchmarks:
> * sql-query
> * sql-query-join
> * sql-query-put 
> broken in  Ignite-5267 branch, in master all ok. 
> Exception:
> <00:39:22> Starting warmup.  
>   
>   
>   
>  
> Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] 
>   
>   
>   
>  
> ERROR: Shutting down benchmark driver to unexpected exception.
>   
>   
>   
>  
> Type '--help' for usage.  
>   
>   
>   
>  
> javax.cache.CacheException: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
> "query"."Person" WHERE salary >= ? and salary <= ?
>   
>
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807)
>   
>   
>  
> at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90)
>   
>   
>
> at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64)
>   
>   
>
> at 
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)   
>   
>   
>   
>   
> at java.lang.Thread.run(Thread.java:745)  
>   
>   
>   
>  
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
> "query"."Person" WHERE salary >= ? and salary <= ?
>   
> 
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291)
>   
>

[jira] [Created] (IGNITE-5436) .NET: CacheConfiguration.GroupName

2017-06-07 Thread Pavel Tupitsyn (JIRA) 
Pavel Tupitsyn created IGNITE-5436:
--

 Summary: .NET: CacheConfiguration.GroupName
 Key: IGNITE-5436
 URL: https://issues.apache.org/jira/browse/IGNITE-5436
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.1


Propagate {{CacheConfiguration.GroupName}} configuration property.

Caches within the same group underneath use single physical Ignite cache.



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

[jira] [Updated] (IGNITE-5341) .NET: DatabaseConfiguration

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-5341:

Description: 
Configure page memory store from .NET
+ make sure that metrics API is up to date with Java.

  was:Configure page memory store from .NET


> .NET: DatabaseConfiguration
> ---
>
> Key: IGNITE-5341
> URL: https://issues.apache.org/jira/browse/IGNITE-5341
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, important
> Fix For: 2.1
>
>
> Configure page memory store from .NET
> + make sure that metrics API is up to date with Java.



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

[jira] [Commented] (IGNITE-5397) JDBC thin driver: clear server cursor automatically when last result piece is transmitted

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

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

ASF GitHub Bot commented on IGNITE-5397:


Github user asfgit closed the pull request at:

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


> JDBC thin driver: clear server cursor automatically when last result piece is 
> transmitted
> -
>
> Key: IGNITE-5397
> URL: https://issues.apache.org/jira/browse/IGNITE-5397
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
>  Labels: performance
> Fix For: 2.1
>
>
> When last part of result set is sent from the server, we should do the 
> following:
> 1) Clear server-side cursor
> 2) Set special marker on the client side that "cursor" close request is not 
> needed. This way we will save two network hops for typical DML request.



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

[jira] [Created] (IGNITE-5435) JDBC thin: support statement close on completion

2017-06-07 Thread Taras Ledkov (JIRA) 
Taras Ledkov created IGNITE-5435:


 Summary: JDBC thin: support statement close on completion
 Key: IGNITE-5435
 URL: https://issues.apache.org/jira/browse/IGNITE-5435
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
 Fix For: 2.2


The methods of JDBC {Statement} must be supported:
- {{closeOnCompletion(boolean)}};
- {{isCloseOnCompletion}};



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

[jira] [Commented] (IGNITE-5397) JDBC thin driver: clear server cursor automatically when last result piece is transmitted

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov commented on IGNITE-5397:
-

[~skalashnikov], looks good to me. I did minor changes, will merge after 
another test run.

> JDBC thin driver: clear server cursor automatically when last result piece is 
> transmitted
> -
>
> Key: IGNITE-5397
> URL: https://issues.apache.org/jira/browse/IGNITE-5397
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
>  Labels: performance
> Fix For: 2.1
>
>
> When last part of result set is sent from the server, we should do the 
> following:
> 1) Clear server-side cursor
> 2) Set special marker on the client side that "cursor" close request is not 
> needed. This way we will save two network hops for typical DML request.



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

[jira] [Closed] (IGNITE-5411) Persist affinity key on disk

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-5411.
---

> Persist affinity key on disk
> 
>
> Key: IGNITE-5411
> URL: https://issues.apache.org/jira/browse/IGNITE-5411
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
> Fix For: 2.1
>
>
> Currently binary metadata is not persisted on a disk anyhow. It means that 
> after full cluster restart we will loose all runtime metadata (except of 
> those configured explicitly in {{IgniteConfiguration.binaryConfiguration}}.
> In future releases we will store metadata in separate storage. For now I 
> propose only to store typeId -> affinityKey mapping on disk to improve value 
> of {{CREATE TABLE}} feature where affinity key is essential for data 
> co-location.



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

[jira] [Assigned] (IGNITE-5411) Persist affinity key on disk

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov reassigned IGNITE-5411:
---

Assignee: (was: Konstantin Dudkov)

> Persist affinity key on disk
> 
>
> Key: IGNITE-5411
> URL: https://issues.apache.org/jira/browse/IGNITE-5411
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently binary metadata is not persisted on a disk anyhow. It means that 
> after full cluster restart we will loose all runtime metadata (except of 
> those configured explicitly in {{IgniteConfiguration.binaryConfiguration}}.
> In future releases we will store metadata in separate storage. For now I 
> propose only to store typeId -> affinityKey mapping on disk to improve value 
> of {{CREATE TABLE}} feature where affinity key is essential for data 
> co-location.



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

[jira] [Resolved] (IGNITE-5411) Persist affinity key on disk

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

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

With final design from IGNITE-5188, this ticket is no longer relevant.

> Persist affinity key on disk
> 
>
> Key: IGNITE-5411
> URL: https://issues.apache.org/jira/browse/IGNITE-5411
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
> Fix For: 2.1
>
>
> Currently binary metadata is not persisted on a disk anyhow. It means that 
> after full cluster restart we will loose all runtime metadata (except of 
> those configured explicitly in {{IgniteConfiguration.binaryConfiguration}}.
> In future releases we will store metadata in separate storage. For now I 
> propose only to store typeId -> affinityKey mapping on disk to improve value 
> of {{CREATE TABLE}} feature where affinity key is essential for data 
> co-location.



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

[jira] [Commented] (IGNITE-5431) Better exception message when SQL cache flag doesn't match

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

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

ASF GitHub Bot commented on IGNITE-5431:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-5431 Better handling of cache SQL flag incompatibility.



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

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

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

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


commit c334090835e204ec4f3fa7c3931a34cc93aa20a3
Author: Alexander Paschenko 
Date:   2017-06-07T11:31:26Z

IGNITE-5431 Better handling of cache SQL flag incompatibility.




> Better exception message when SQL cache flag doesn't match
> --
>
> Key: IGNITE-5431
> URL: https://issues.apache.org/jira/browse/IGNITE-5431
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> SQL flag configuration check is performed in 
> {{ClusterCachesInfo>checkCache}}. Default validation mechanics is used and 
> the following error message appears: 
> {code}
> SQL flag mismatch (fix sql flag in cache configuration or set 
> -DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property) 
> [cacheName=SQL_PUBLIC_Person, localSql=false, remoteSql=true, 
> rmtNodeId=b975316b-ad6a-4f64-b8a4-9eaac642]
> {code}
> Apparently, it is misleading because there is no such config property. Need 
> to fix that and make sure that 
> {{DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK}} has no effect on this check.



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

[jira] [Commented] (IGNITE-4841) Improve TEXT Query Documentation

2017-06-07 Thread Andrew Mashenkov (JIRA) 

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

Andrew Mashenkov commented on IGNITE-4841:
--

1. Syntax is classic query parser syntax
2. StandardAnalyzer is used and there is no way to change it. Feel free to 
start a thread on dev list and suggest a proposal.
3. For now it is 3.5.0, but seems it will be upgraded up to 5.5.2 in 
ignite-2.1. See IGNITE-3562 issue and [1] for more information.
4. Likely, it is because of internal class. I think we should provide correct 
javadoc for \@QueryTextField annotation.

Seems, FullTextSearch feature is rarely used, so this is why it is not 
developing actively.

[1] 
http://apache-ignite-developers.2346864.n4.nabble.com/Upgrade-dependency-to-outdated-Lucene-3-5-0-td17952.html



> Improve TEXT Query Documentation
> 
>
> Key: IGNITE-4841
> URL: https://issues.apache.org/jira/browse/IGNITE-4841
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 1.9
>Reporter: Daniel Siviter
>
> The documentation for Full TEXT Queries is thin at best:
> * What syntax does it use?
> * ...is it the full [Lucene Classic Query Parser 
> Syntax|https://lucene.apache.org/core/6_3_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html]?
> * ...if so how does the syntax map to the {{@QueryTextField}} annotation?
> * How is Lucene analyser customisation performed?
> * What version is supported? (looks like 3.5.0 which is pretty old, latest is 
> 6.4.1)
> * The 
> [{{@QueryTextField}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/annotations/QueryTextField.html]
>  JavaDoc refers to 
> [{{CacheQuery}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/internal/processors/cache/query/CacheQuery.html]
>  but strangely this doesn't even appear in the official JavaDoc. It is 
> because it's an 'internal' class?
> It's mentioned multiple times as a feature, but doesn't look like much of 
> Lucene can actually be utilised so clarifications would help greatly.



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

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

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

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

ASF GitHub Bot commented on IGNITE-5196:


GitHub user gvvinblade opened a pull request:

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

IGNITE-5196 Ignite JDBC Driver fix



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

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

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

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


commit 8ddd4713fb12d23adf87e4b78ca5b808b6688ffe
Author: Igor Seliverstov 
Date:   2017-06-07T11:24:24Z

Ignite JDBC Driver fix




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



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

[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch

2017-06-07 Thread Aleksey Chetaev (JIRA) 

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

Aleksey Chetaev updated IGNITE-5434:

Description: 
Yardstick benchmarks:
* sql-query
* sql-query-join
* sql-query-put 

broken in  Ignite-5267 branch, in master all ok. 

Exception:
<00:39:22> Starting warmup.



 
Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017]   



 
ERROR: Shutting down benchmark driver to unexpected exception.  



 
Type '--help' for usage.



 
javax.cache.CacheException: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  
   
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807)


 
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90)


   
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64)


   
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) 



  
at java.lang.Thread.run(Thread.java:745)



 
Caused by: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  


at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291)


 
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196)


   
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$8.applyx(GridQueryProcessor.java:1947)

[jira] [Created] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch

2017-06-07 Thread Aleksey Chetaev (JIRA) 
Aleksey Chetaev created IGNITE-5434:
---

 Summary: Yardstick sql benchmarks broken on Ignite-5267 branch
 Key: IGNITE-5434
 URL: https://issues.apache.org/jira/browse/IGNITE-5434
 Project: Ignite
  Issue Type: Bug
  Components: sql, yardstick
Affects Versions: 2.1
Reporter: Aleksey Chetaev
Priority: Critical


Yardstick benchmarks:
*sql-query
*sql-query-join
*sql-query-put 
broken in  Ignite-5267 branch, in master all ok. 

Exception:
<00:39:22> Starting warmup.



 
Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017]   



 
ERROR: Shutting down benchmark driver to unexpected exception.  



 
Type '--help' for usage.



 
javax.cache.CacheException: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  
   
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807)


 
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90)


   
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64)


   
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) 



  
at java.lang.Thread.run(Thread.java:745)



 
Caused by: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  


at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291)


 
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196)

[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch

2017-06-07 Thread Aleksey Chetaev (JIRA) 

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

Aleksey Chetaev updated IGNITE-5434:

Description: 
Yardstick benchmarks:
* sql-query
* sql-query-join
* sql-query-put 
broken in  Ignite-5267 branch, in master all ok. 

Exception:
<00:39:22> Starting warmup.



 
Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017]   



 
ERROR: Shutting down benchmark driver to unexpected exception.  



 
Type '--help' for usage.



 
javax.cache.CacheException: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  
   
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807)


 
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90)


   
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64)


   
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) 



  
at java.lang.Thread.run(Thread.java:745)



 
Caused by: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  


at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291)


 
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196)


   
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$8.applyx(GridQueryProcessor.java:1947)

[jira] [Commented] (IGNITE-5430) Mask cache name for CREATE TABLE operation

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

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

ASF GitHub Bot commented on IGNITE-5430:


Github user devozerov closed the pull request at:

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


> Mask cache name for CREATE TABLE operation
> --
>
> Key: IGNITE-5430
> URL: https://issues.apache.org/jira/browse/IGNITE-5430
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Masked name should be: {{sql_schemaName_tableName}}.



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

[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch

2017-06-07 Thread Aleksey Chetaev (JIRA) 

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

Aleksey Chetaev updated IGNITE-5434:

Description: 
Yardstick benchmarks:
* sql-query
* sql-query-join
* sql-query-put 

broken in  Ignite-5267 branch, in master all ok. 

Exception:
<00:39:22> Starting warmup.



 
Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017]   



 
ERROR: Shutting down benchmark driver to unexpected exception.  



 
Type '--help' for usage.



 
javax.cache.CacheException: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  
   
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807)


 
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90)


   
at 
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64)


   
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) 



  
at java.lang.Thread.run(Thread.java:745)



 
Caused by: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM 
"query"."Person" WHERE salary >= ? and salary <= ?  


at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291)


 
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196)


   
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$8.applyx(GridQueryProcessor.java:1947)

[jira] [Updated] (IGNITE-5359) Non-collocated SQL subqueries return wrong results.

2017-06-07 Thread Andrew Mashenkov (JIRA) 

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

Andrew Mashenkov updated IGNITE-5359:
-
Summary: Non-collocated SQL subqueries return wrong results.  (was: SQL 
subquery with aggregates return wrong results.)

> Non-collocated SQL subqueries return wrong results.
> ---
>
> Key: IGNITE-5359
> URL: https://issues.apache.org/jira/browse/IGNITE-5359
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
>Priority: Critical
> Fix For: 2.1
>
> Attachments: JoinWithAggr.java
>
>
> PFA repro attached.



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

[jira] [Updated] (IGNITE-5105) Simplify binary read/write routines

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-5105:

Fix Version/s: (was: 2.1)
   2.2

> Simplify binary read/write routines
> ---
>
> Key: IGNITE-5105
> URL: https://issues.apache.org/jira/browse/IGNITE-5105
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.2
>
>
> Currently binary read/write routines are excessively complex. There are code 
> duplicates and unnecessary null checks in several places. 
> We need to refactor them to common form.



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

[jira] [Assigned] (IGNITE-5271) Web Console: light basic/advanced configuration

2017-06-07 Thread Ilya Borisov (JIRA) 

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

Ilya Borisov reassigned IGNITE-5271:


Assignee: Andrey Novikov  (was: Ilya Borisov)

[~Dmitriyff] all fixed. [~anovikov], please review.

> Web Console: light basic/advanced configuration
> ---
>
> Key: IGNITE-5271
> URL: https://issues.apache.org/jira/browse/IGNITE-5271
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
> Attachments: simple basic configuration.png
>
>
> Implement light version of basic/advanced configuration. "Light version" 
> implies old form styles/components, new basic form and redesigned tabbed 
> navigation. Advanced section remains the same as current configuration screen.
> Basic configuration form should:
> 1. Notify user that he has no/some clusters. Use these messages: "You have no 
> clusters. Let’s configure your first and associate it with caches and 
> in-memory file systems!" and "You have N cluster(s). You can create a new one 
> on this tab or *edit existing ones* (link to advanced.clusters)".
> 2. Be able to add new cluster or edit existing one.
> 3. Be able to add new caches or choose and edit existing ones.
> 4. Have "Save and Download" button, which saves caches/cluster and then 
> download that cluster configuration.
> Parent configuration state should:
> 1. On state enter, check amount of clusters user has. If there are none, 
> redirect to basic config screen, otherwise redirect to advanced config screen.



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

[jira] [Updated] (IGNITE-5432) Test IgniteMarshallerCacheClassNameConflictTest failed

2017-06-07 Thread Alexey Ivanov (JIRA) 

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

Alexey Ivanov updated IGNITE-5432:
--
Affects Version/s: 2.1
  Environment: (was: 
)
Fix Version/s: 2.1

>  Test IgniteMarshallerCacheClassNameConflictTest failed
> ---
>
> Key: IGNITE-5432
> URL: https://issues.apache.org/jira/browse/IGNITE-5432
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexey Ivanov
> Fix For: 2.1
>
>
> Test suit:
> IgniteBinarySimpleNameMapperBasicTestSuite
> Test:
> IgniteMarshallerCacheClassNameConflictTest



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

[jira] [Created] (IGNITE-5433) Incorrect warning when "default" memory policy is used

2017-06-07 Thread Ksenia Rybakova (JIRA) 
Ksenia Rybakova created IGNITE-5433:
---

 Summary: Incorrect warning when "default" memory policy is used
 Key: IGNITE-5433
 URL: https://issues.apache.org/jira/browse/IGNITE-5433
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ksenia Rybakova
Priority: Minor
 Fix For: 2.1


The following memory config is used:
{noformat}





{noformat}
No any additional memory policies are configured.

Server RAM is 98Gb (at least 50Gb is free). Default memory policy should use 
80% of it.

But warning in log is:
{noformat}
[WARN ][main][IgniteCacheDatabaseSharedManager] No user-defined default 
MemoryPolicy found; system default of 1GB size will be used.



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

[jira] [Updated] (IGNITE-5433) Incorrect warning when "default" memory policy is used

2017-06-07 Thread Ksenia Rybakova (JIRA) 

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

Ksenia Rybakova updated IGNITE-5433:

Description: 
The following memory config is used:
{noformat}





{noformat}
No any additional memory policies are configured.

Server RAM is 98Gb (at least 50Gb is free). Default memory policy should use 
80% of it.

But warning in log is:
{noformat}
[WARN ][main][IgniteCacheDatabaseSharedManager] No user-defined default 
MemoryPolicy found; system default of 1GB size will be used.
{noformat}

  was:
The following memory config is used:
{noformat}





{noformat}
No any additional memory policies are configured.

Server RAM is 98Gb (at least 50Gb is free). Default memory policy should use 
80% of it.

But warning in log is:
{noformat}
[WARN ][main][IgniteCacheDatabaseSharedManager] No user-defined default 
MemoryPolicy found; system default of 1GB size will be used.


> Incorrect warning when "default" memory policy is used
> --
>
> Key: IGNITE-5433
> URL: https://issues.apache.org/jira/browse/IGNITE-5433
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ksenia Rybakova
>Priority: Minor
> Fix For: 2.1
>
>
> The following memory config is used:
> {noformat}
> 
> 
> 
> 
> 
> {noformat}
> No any additional memory policies are configured.
> Server RAM is 98Gb (at least 50Gb is free). Default memory policy should use 
> 80% of it.
> But warning in log is:
> {noformat}
> [WARN ][main][IgniteCacheDatabaseSharedManager] No user-defined default 
> MemoryPolicy found; system default of 1GB size will be used.
> {noformat}



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

[jira] [Created] (IGNITE-5432) Test IgniteMarshallerCacheClassNameConflictTest failed

2017-06-07 Thread Alexey Ivanov (JIRA) 
Alexey Ivanov created IGNITE-5432:
-

 Summary:  Test IgniteMarshallerCacheClassNameConflictTest failed
 Key: IGNITE-5432
 URL: https://issues.apache.org/jira/browse/IGNITE-5432
 Project: Ignite
  Issue Type: Bug
 Environment: 

Reporter: Alexey Ivanov


Test suit:
IgniteBinarySimpleNameMapperBasicTestSuite

Test:
IgniteMarshallerCacheClassNameConflictTest



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

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

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov commented on IGNITE-5188:
-

[~al.psc], my comments:
1) I made some changes to mapper to avoid unnecessary calls to potentially 
expensive methods of binary API.
2) Please confirm that we have tests for all parsing negative tests cases: aff 
field is not a key field, bad quotes, aff field is not found, etc..

> Support AFFINITY KEY keyword for CREATE TABLE command
> -
>
> Key: IGNITE-5188
> URL: https://issues.apache.org/jira/browse/IGNITE-5188
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> We need to be able to specify affinity key for cache created through {{CREATE 
> TABLE}} command to support data co-location properly. It seems that correct 
> way to support this is as follows:
> 1) We need to define special SQL affinity mapper which will accept type name 
> and field name.
> 2) Mapper logic: if type name matches, then get affinity field. Otherwise 
> return the whole object. 
> 3) Performance consideration: we should avoid string comparisons. Instead, we 
> should resolve type name to type ID on first access, and then compare only 
> IDs.
> 4) We should fix on how we obtain affinity key for type descriptor in 
> {{QueryUtils.typeForQueryEntity}} - we should try consulting to special SQL 
> mapper first, if it is defined.
> 5) Last (hopefully), we should make sure that affinity routing is not broken. 
> See {{GridH2Table.ctor}} - here we should rely on existing affinity column 
> from SQL mapper if one is defined.
>  



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

[jira] [Assigned] (IGNITE-5375) New PersistentStoreMetrics, MemoryMetrics interface improvements

2017-06-07 Thread Alexey Goncharuk (JIRA) 

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

Alexey Goncharuk reassigned IGNITE-5375:


Assignee: Alexey Goncharuk  (was: Sergey Chugunov)

> New PersistentStoreMetrics, MemoryMetrics interface improvements
> 
>
> Key: IGNITE-5375
> URL: https://issues.apache.org/jira/browse/IGNITE-5375
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Sergey Chugunov
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
>
> h2. Notes
> Original discussions on dev list: on [Persistent Store 
> Metrics|http://apache-ignite-developers.2346864.n4.nabble.com/Persistent-Distributed-Store-Metrics-tt17730.html];
>  on a new way of thinking of Memory Policies as [virtual 
> memory|http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-memory-gt-virtual-memory-tt18291.html].
> Existing {{MemoryMetrics}} interface will be enhanced with additional methods 
> for monitoring persistence activities (only new methods are listed):
> {code}
> public interface MemoryMetrics {
> ...
> public long getDirtyPages();
> public float getPagesReplaceRate();
> public long getPhysicalMemoryPages();
> }
> {code}
> Proposed interface for Persistent Store Metrics:
> {code}
> public interface PersistentStoreMetrics {
> public float getWalLoggingRate();
> public int getWalArchiveSegments();
> public float getWalFsyncTime();
> public float getCheckpointingTime();
> public float getCheckpointingFsyncTime();
> public long getCheckpointingTotalPagesNumber();
> public long[] getCheckpointingPagesByTypeNumber();
> public long getCheckpointingCopiedOnWritePagesNumber();
> }
> {code}
> h2. Acceptance Criteria
> # MemoryMetrics interface is expanded with new methods
> # Persistent Store Metrics are implemented according to the proposed interface
> # Semantics of existing method {{MemoryMetrics::getTotalAllocatedPages}} is 
> changed to return not only pages residing in memory, but total amount of 
> paged including ones on disk. 
> For amount of pages in RAM new method {{getPhysicalMemoryPages}} is added.



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

[jira] [Resolved] (IGNITE-5375) New PersistentStoreMetrics, MemoryMetrics interface improvements

2017-06-07 Thread Alexey Goncharuk (JIRA) 

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

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

Merged to ignite-5267 branch.

> New PersistentStoreMetrics, MemoryMetrics interface improvements
> 
>
> Key: IGNITE-5375
> URL: https://issues.apache.org/jira/browse/IGNITE-5375
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Sergey Chugunov
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
>
> h2. Notes
> Original discussions on dev list: on [Persistent Store 
> Metrics|http://apache-ignite-developers.2346864.n4.nabble.com/Persistent-Distributed-Store-Metrics-tt17730.html];
>  on a new way of thinking of Memory Policies as [virtual 
> memory|http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-memory-gt-virtual-memory-tt18291.html].
> Existing {{MemoryMetrics}} interface will be enhanced with additional methods 
> for monitoring persistence activities (only new methods are listed):
> {code}
> public interface MemoryMetrics {
> ...
> public long getDirtyPages();
> public float getPagesReplaceRate();
> public long getPhysicalMemoryPages();
> }
> {code}
> Proposed interface for Persistent Store Metrics:
> {code}
> public interface PersistentStoreMetrics {
> public float getWalLoggingRate();
> public int getWalArchiveSegments();
> public float getWalFsyncTime();
> public float getCheckpointingTime();
> public float getCheckpointingFsyncTime();
> public long getCheckpointingTotalPagesNumber();
> public long[] getCheckpointingPagesByTypeNumber();
> public long getCheckpointingCopiedOnWritePagesNumber();
> }
> {code}
> h2. Acceptance Criteria
> # MemoryMetrics interface is expanded with new methods
> # Persistent Store Metrics are implemented according to the proposed interface
> # Semantics of existing method {{MemoryMetrics::getTotalAllocatedPages}} is 
> changed to return not only pages residing in memory, but total amount of 
> paged including ones on disk. 
> For amount of pages in RAM new method {{getPhysicalMemoryPages}} is added.



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

[jira] [Commented] (IGNITE-5430) Mask cache name for CREATE TABLE operation

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

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

ASF GitHub Bot commented on IGNITE-5430:


GitHub user devozerov opened a pull request:

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

IGNITE-5430



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

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

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

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


commit 53f0958792919d72483f8a2a83ec5ba22b2d393c
Author: devozerov 
Date:   2017-06-07T09:57:00Z

Done.




> Mask cache name for CREATE TABLE operation
> --
>
> Key: IGNITE-5430
> URL: https://issues.apache.org/jira/browse/IGNITE-5430
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Masked name should be: {{sql_schemaName_tableName}}.



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

[jira] [Commented] (IGNITE-5422) CREATE TABLE command should support all-key fields case

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

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

ASF GitHub Bot commented on IGNITE-5422:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-5422



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

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

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

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


commit 7698dd35c39bd636e9386e25e29a108acd815886
Author: Alexander Paschenko 
Date:   2017-06-07T09:51:48Z

IGNITE-5422 CREATE TABLE with no value columns.

commit f481f9e73ec3278df7d8cb91017414b042682433
Author: Alexander Paschenko 
Date:   2017-06-07T09:52:25Z

Merge remote-tracking branch 'apache/master' into ignite-5422




> CREATE TABLE command should support all-key fields case
> ---
>
> Key: IGNITE-5422
> URL: https://issues.apache.org/jira/browse/IGNITE-5422
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.2
>
>
> Currently it is impossible to create a table containing only {{PRIMARY KEY}} 
> columns:
> {code}
> CREATE TABLE PersonProject {
> person_id BIGINT,
> project_id BIGINT,
> PRIMARY KEY (person_id, project_id);
> };
> {code}
> The reason for this limitation is that we have nothing to be saved as cache 
> value and {{null}} values are restricted because they are indistinguishable 
> from removal.
> We should allow this case somehow. Possible solutions:
> 1) Save empty object of table type: 
> {{IgniteBinary.builder("PersonProject").build()}}
> 2) Save {{false}} as it is done in Java in Map-to-Set conversion
> Note that DML processing should be adjusted accordingly.



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

[jira] [Commented] (IGNITE-5414) Web Console: Model import should use unique indexes if no PK found

2017-06-07 Thread Pavel Konstantinov (JIRA) 

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

Pavel Konstantinov commented on IGNITE-5414:


I created two unique indeces
the first one contains 1 field (id1)
the second - 3 fields (id1,id2,id3)
Second index was imported w\o id1 field

> Web Console: Model import should use unique indexes if no PK found
> --
>
> Key: IGNITE-5414
> URL: https://issues.apache.org/jira/browse/IGNITE-5414
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
>
> When import model from RDBMS some tables without primary key could have 
> unique index that could be used for key fields generation.



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

[jira] [Created] (IGNITE-5431) Better exception message when SQL cache flag doesn't match

2017-06-07 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-5431:
---

 Summary: Better exception message when SQL cache flag doesn't match
 Key: IGNITE-5431
 URL: https://issues.apache.org/jira/browse/IGNITE-5431
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


SQL flag configuration check is performed in {{ClusterCachesInfo>checkCache}}. 
Default validation mechanics is used and the following error message appears: 
{code}
SQL flag mismatch (fix sql flag in cache configuration or set 
-DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property) 
[cacheName=SQL_PUBLIC_Person, localSql=false, remoteSql=true, 
rmtNodeId=b975316b-ad6a-4f64-b8a4-9eaac642]
{code}

Apparently, it is misleading because there is no such config property. Need to 
fix that and make sure that {{DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK}} 
has no effect on this check.



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

[jira] [Commented] (IGNITE-5400) .NET: IgniteConfiguration.SqlConnectorConfiguration

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

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

ASF GitHub Bot commented on IGNITE-5400:


Github user asfgit closed the pull request at:

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


> .NET: IgniteConfiguration.SqlConnectorConfiguration
> ---
>
> Key: IGNITE-5400
> URL: https://issues.apache.org/jira/browse/IGNITE-5400
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> We should move new SQL server configuration to .NET once IGNITE-5275 is ready.



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

[jira] [Resolved] (IGNITE-5400) .NET: IgniteConfiguration.SqlConnectorConfiguration

2017-06-07 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn resolved IGNITE-5400.

Resolution: Fixed

> .NET: IgniteConfiguration.SqlConnectorConfiguration
> ---
>
> Key: IGNITE-5400
> URL: https://issues.apache.org/jira/browse/IGNITE-5400
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> We should move new SQL server configuration to .NET once IGNITE-5275 is ready.



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

[jira] [Commented] (IGNITE-5383) Do not perform cache key validation when BinaryMarshaller is used

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov commented on IGNITE-5383:
-

[~daradurvs], thank you for contribution. Will review it shortly.

> Do not perform cache key validation when BinaryMarshaller is used
> -
>
> Key: IGNITE-5383
> URL: https://issues.apache.org/jira/browse/IGNITE-5383
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important
> Fix For: 2.1
>
>
> Currently whenever cache operation is performed, we invoke 
> {{GridCacheAdapter.validateCacheKey}} to make sure that key overrides 
> {{equals}} and {{hashCode}}. 
> This check should not be performed when {{BinaryMarshaller}} is set, since we 
> do not use these methods in binary mode. 



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

[jira] [Commented] (IGNITE-5400) .NET: IgniteConfiguration.SqlConnectorConfiguration

2017-06-07 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn commented on IGNITE-5400:


Merged to master: {{86d0049b7a248cf6f9fe2532b63d0e22baaa659e}}

> .NET: IgniteConfiguration.SqlConnectorConfiguration
> ---
>
> Key: IGNITE-5400
> URL: https://issues.apache.org/jira/browse/IGNITE-5400
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> We should move new SQL server configuration to .NET once IGNITE-5275 is ready.



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

[jira] [Updated] (IGNITE-5383) Do not perform cache key validation when BinaryMarshaller is used

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-5383:

Fix Version/s: (was: 2.2)
   2.1

> Do not perform cache key validation when BinaryMarshaller is used
> -
>
> Key: IGNITE-5383
> URL: https://issues.apache.org/jira/browse/IGNITE-5383
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important
> Fix For: 2.1
>
>
> Currently whenever cache operation is performed, we invoke 
> {{GridCacheAdapter.validateCacheKey}} to make sure that key overrides 
> {{equals}} and {{hashCode}}. 
> This check should not be performed when {{BinaryMarshaller}} is set, since we 
> do not use these methods in binary mode. 



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

[jira] [Assigned] (IGNITE-5383) Do not perform cache key validation when BinaryMarshaller is used

2017-06-07 Thread Vyacheslav Daradur (JIRA) 

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

Vyacheslav Daradur reassigned IGNITE-5383:
--

Assignee: Vyacheslav Daradur

> Do not perform cache key validation when BinaryMarshaller is used
> -
>
> Key: IGNITE-5383
> URL: https://issues.apache.org/jira/browse/IGNITE-5383
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important
> Fix For: 2.2
>
>
> Currently whenever cache operation is performed, we invoke 
> {{GridCacheAdapter.validateCacheKey}} to make sure that key overrides 
> {{equals}} and {{hashCode}}. 
> This check should not be performed when {{BinaryMarshaller}} is set, since we 
> do not use these methods in binary mode. 



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

[jira] [Assigned] (IGNITE-5271) Web Console: light basic/advanced configuration

2017-06-07 Thread Dmitriy Shabalin (JIRA) 

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

Dmitriy Shabalin reassigned IGNITE-5271:


Assignee: Ilya Borisov  (was: Dmitriy Shabalin)

[~Klaster_1] pls add redirect to configuration/basic as default after sign in, 
and send to finally review to [~anovikov]

> Web Console: light basic/advanced configuration
> ---
>
> Key: IGNITE-5271
> URL: https://issues.apache.org/jira/browse/IGNITE-5271
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
> Attachments: simple basic configuration.png
>
>
> Implement light version of basic/advanced configuration. "Light version" 
> implies old form styles/components, new basic form and redesigned tabbed 
> navigation. Advanced section remains the same as current configuration screen.
> Basic configuration form should:
> 1. Notify user that he has no/some clusters. Use these messages: "You have no 
> clusters. Let’s configure your first and associate it with caches and 
> in-memory file systems!" and "You have N cluster(s). You can create a new one 
> on this tab or *edit existing ones* (link to advanced.clusters)".
> 2. Be able to add new cluster or edit existing one.
> 3. Be able to add new caches or choose and edit existing ones.
> 4. Have "Save and Download" button, which saves caches/cluster and then 
> download that cluster configuration.
> Parent configuration state should:
> 1. On state enter, check amount of clusters user has. If there are none, 
> redirect to basic config screen, otherwise redirect to advanced config screen.



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

[jira] [Created] (IGNITE-5430) Mask cache name for CREATE TABLE operation

2017-06-07 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-5430:
---

 Summary: Mask cache name for CREATE TABLE operation
 Key: IGNITE-5430
 URL: https://issues.apache.org/jira/browse/IGNITE-5430
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.1


Masked name should be: {{sql_schemaName_tableName}}.



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

[jira] [Updated] (IGNITE-3939) Compact long zero values binary representation

2017-06-07 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-3939:

Fix Version/s: (was: 2.1)
   2.2

> Compact long zero values binary representation
> --
>
> Key: IGNITE-3939
> URL: https://issues.apache.org/jira/browse/IGNITE-3939
> Project: Ignite
>  Issue Type: Improvement
>  Components: binary
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Taras Ledkov
>  Labels: important, performance
> Fix For: 2.2
>
>
> We can use separate type for Long zero values and exclude 8-byte value from 
> binary representation. This will reduce memory footprint and network load.
> Compatibility with previous versions MUST be preserved.



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

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

2017-06-07 Thread Semen Boikov (JIRA) 

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

Semen Boikov resolved IGNITE-5196.
--
Resolution: Fixed

Thanks Igor! Merged into master.

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



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

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

2017-06-07 Thread Igor Seliverstov (JIRA) 

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

Igor Seliverstov commented on IGNITE-5196:
--

[~sboikov], I've fixed the issue. 

Checking each test separately I forgot to run all of them together.

Master is merged, tests are passed (checked twice).

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



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

[jira] [Commented] (IGNITE-5383) Do not perform cache key validation when BinaryMarshaller is used

2017-06-07 Thread Vyacheslav Daradur (JIRA) 

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

Vyacheslav Daradur commented on IGNITE-5383:


All subclasses of GridCacheAdapter use the non-static methods 
{{validateCacheKey}} and {{validateCacheKeys}} which are controlled by the flag 
{{keyCheck}}.
I propose to check in the conctructor of {{GridCacheAdapter}} if 
{{BinaryMarshaller}} is used then set {{keyCheck}} to {{false}}.

[~vozerov], please, review the solution. 
([ci.tests|http://ci.ignite.apache.org/viewLog.html?buildId=652028=buildResultsDiv=IgniteTests_RunAll])

> Do not perform cache key validation when BinaryMarshaller is used
> -
>
> Key: IGNITE-5383
> URL: https://issues.apache.org/jira/browse/IGNITE-5383
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: important
> Fix For: 2.2
>
>
> Currently whenever cache operation is performed, we invoke 
> {{GridCacheAdapter.validateCacheKey}} to make sure that key overrides 
> {{equals}} and {{hashCode}}. 
> This check should not be performed when {{BinaryMarshaller}} is set, since we 
> do not use these methods in binary mode. 



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

[jira] [Closed] (IGNITE-5406) VisorExecutorConfiguration and VisorGridConfiguration should use IgniteConfiguration.sqlConnectorConfiguration insread of IgniteConfiguration.odbcConfiguration

2017-06-07 Thread Alexey Kuznetsov (JIRA) 

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

Alexey Kuznetsov closed IGNITE-5406.


Merged to master.

> VisorExecutorConfiguration and VisorGridConfiguration should use 
> IgniteConfiguration.sqlConnectorConfiguration insread of 
> IgniteConfiguration.odbcConfiguration
> ---
>
> Key: IGNITE-5406
> URL: https://issues.apache.org/jira/browse/IGNITE-5406
> Project: Ignite
>  Issue Type: Bug
>  Components: sql, visor
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
>




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

[jira] [Resolved] (IGNITE-5406) VisorExecutorConfiguration and VisorGridConfiguration should use IgniteConfiguration.sqlConnectorConfiguration insread of IgniteConfiguration.odbcConfiguration

2017-06-07 Thread Alexey Kuznetsov (JIRA) 

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

Alexey Kuznetsov resolved IGNITE-5406.
--
Resolution: Fixed

> VisorExecutorConfiguration and VisorGridConfiguration should use 
> IgniteConfiguration.sqlConnectorConfiguration insread of 
> IgniteConfiguration.odbcConfiguration
> ---
>
> Key: IGNITE-5406
> URL: https://issues.apache.org/jira/browse/IGNITE-5406
> Project: Ignite
>  Issue Type: Bug
>  Components: sql, visor
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
>




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

[jira] [Created] (IGNITE-5429) Affinity run: optimize partition reservations for caches in the same group

2017-06-07 Thread Semen Boikov (JIRA) 
Semen Boikov created IGNITE-5429:


 Summary: Affinity run: optimize partition reservations for caches 
in the same group
 Key: IGNITE-5429
 URL: https://issues.apache.org/jira/browse/IGNITE-5429
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Semen Boikov
 Fix For: 2.1


For affinityRun we reserve partitions per-cache 
(GridJobProcessor.PartitionsReservation), it can be optimzied if caches belong 
to the same group.

Also need add corresponding tests.



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

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

2017-06-07 Thread Semen Boikov (JIRA) 

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

Semen Boikov edited comment on IGNITE-5196 at 6/7/17 6:52 AM:
--

Please always merge from master before sending for review. 
And your test fails, please fix:
{noformat}
09:49:53,590][ERROR][main][root] Test failed.
org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache 
with the same name is already started): cache0
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:3647)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2480)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2419)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createFromTemplate(GridCacheProcessor.java:2280)
at 
org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2780)
at 
org.apache.ignite.internal.ClusterGroupSelfTest$3.run(ClusterGroupSelfTest.java:331)
at 
org.apache.ignite.testframework.GridTestUtils$9.call(GridTestUtils.java:1208)
at 
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
Suppressed: org.apache.ignite.cache.CacheExistsException: Failed to 
start cache (a cache with the same name is already started): cache12
... 8 more
Suppressed: org.apache.ignite.cache.CacheExistsException: Failed to 
start cache (a cache with the same name is already started): cache8
... 8 more
Suppressed: org.apache.ignite.cache.CacheExistsException: Failed to 
start cache (a cache with the same name is already started): cache4
... 8 more
{noformat}



was (Author: sboikov):
Test fails:
{noformat}
09:49:53,590][ERROR][main][root] Test failed.
org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache 
with the same name is already started): cache0
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:3647)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2480)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2419)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createFromTemplate(GridCacheProcessor.java:2280)
at 
org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2780)
at 
org.apache.ignite.internal.ClusterGroupSelfTest$3.run(ClusterGroupSelfTest.java:331)
at 
org.apache.ignite.testframework.GridTestUtils$9.call(GridTestUtils.java:1208)
at 
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
Suppressed: org.apache.ignite.cache.CacheExistsException: Failed to 
start cache (a cache with the same name is already started): cache12
... 8 more
Suppressed: org.apache.ignite.cache.CacheExistsException: Failed to 
start cache (a cache with the same name is already started): cache8
... 8 more
Suppressed: org.apache.ignite.cache.CacheExistsException: Failed to 
start cache (a cache with the same name is already started): cache4
... 8 more
{noformat}


> Concurrent modification in .GridDiscoveryManager.nodeCaches
> ---
>
> Key: IGNITE-5196
> URL: https://issues.apache.org/jira/browse/IGNITE-5196
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
>
> {noformat}
> ./grid149.tar.gz:org.apache.ignite.IgniteCheckedException: null
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7281) 
> ~[ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:171)
>  [ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-1.10.3.ea6.jar:2.0.0-SNAPSHOT]
> ./grid149.tar.gz:   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_121]
> ./grid149.tar.gz:   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_121]
> ./grid149.tar.gz:   at java.lang.Thread.run(Thread.java:745) 
> [na:1.8.0_121]
> ./grid149.tar.gz:Caused by: java.util.ConcurrentModificationException: null
> ./grid149.tar.gz:   at 
>

[jira] [Commented] (IGNITE-5424) GridServiceProxy does not unwraps exception message from InvocationTargetException

2017-06-07 Thread Ben (JIRA) 

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

Ben commented on IGNITE-5424:
-

See https://issues.apache.org/jira/browse/IGNITE-4298

> GridServiceProxy does not unwraps exception message from 
> InvocationTargetException
> --
>
> Key: IGNITE-5424
> URL: https://issues.apache.org/jira/browse/IGNITE-5424
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 2.1
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.2
>
>
> Instead of correct message 'null' passed.
> {noformat}
> class org.apache.ignite.IgniteException: null
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProxy.invokeMethod(GridServiceProxy.java:208)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProxy$ProxyInvocationHandler.invoke(GridServiceProxy.java:356)
>   at org.apache.ignite.internal.processors.service.$Proxy25.go(Unknown 
> Source)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessorProxySelfTest.testException(GridServiceProcessorProxySelfTest.java:78)
>   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:1979)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:130)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1894)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7262)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:189)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProxy.invokeMethod(GridServiceProxy.java:197)
>   ... 12 more
> Caused by: java.lang.reflect.InvocationTargetException
>   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 
> org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:417)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1847)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6641)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1907)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1550)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1178)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   ... 1 more
> Caused by: java.lang.Exception: Test exception
>   at 
>

[jira] [Assigned] (IGNITE-2698) CacheKeyConfiguration is used only with BinaryMarshaller

2017-06-07 Thread Semen Boikov (JIRA) 

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

Semen Boikov reassigned IGNITE-2698:


Assignee: (was: Semen Boikov)

> CacheKeyConfiguration is used only with BinaryMarshaller
> 
>
> Key: IGNITE-2698
> URL: https://issues.apache.org/jira/browse/IGNITE-2698
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
> Fix For: 2.2
>
>
> Now if CacheKeyConfiguration is specified it is used only with 
> BinaryMarshaller. Need to take it into account with others marshallers as 
> well or update documentation.



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