[jira] [Assigned] (IGNITE-2173) Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with if (log.isDebugEnabled())

[Michael Griggs (JIRA)]

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

Michael Griggs reassigned IGNITE-2173:
--

Assignee: Michael Griggs

> Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with 
> if (log.isDebugEnabled())
> --
>
> Key: IGNITE-2173
> URL: https://issues.apache.org/jira/browse/IGNITE-2173
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
>Priority: Minor
> Fix For: 1.6
>
>
> e.g., line 1029
> {code}
> log.debug("Write entries to db one by one using update and insert statements 
> [cache name=" +
> {code}
> A side-effect of this is WARNing messages in your log file when these 
> statements are executed:
> {code}
> 2015-12-15 16:19:26 WARN  CacheJdbcPojoStore:463 - Logging at DEBUG level 
> without checking if DEBUG level is enabled: 
> {code}



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

[jira] [Created] (IGNITE-2173) Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with if (log.isDebugEnabled())

[Michael Griggs (JIRA)]

Michael Griggs created IGNITE-2173:
--

 Summary: Some log.debug() calls in CacheAbstractJdbcStore.java are 
not protected with if (log.isDebugEnabled())
 Key: IGNITE-2173
 URL: https://issues.apache.org/jira/browse/IGNITE-2173
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.5
Reporter: Michael Griggs
Priority: Minor


e.g., line 1029

{code}
log.debug("Write entries to db one by one using update and insert statements 
[cache name=" +
{code}

A side-effect of this is WARNing messages in your log file when these 
statements are executed:

{code}
2015-12-15 16:19:26 WARN  CacheJdbcPojoStore:463 - Logging at DEBUG level 
without checking if DEBUG level is enabled: 
{code}




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

[jira] [Commented] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

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

Michael Griggs commented on IGNITE-2169:


I am going to try and fix this before the 1.5 final is taken later this week.

> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
> Fix For: 1.5
>
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)
> UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2122:


1) What is user supposed to do if he wants a concrete type like HashSet or 
ConcurrentBag?
2) Exactly, and current solution does not have this problem.
3) Looks good, similar to current solution, slightly less versatile, but easier 
to use. Should we agree on this one?

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




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

[jira] [Comment Edited] (IGNITE-2004) Asynchronous execution of ContinuousQuery's remote filter

[Andrey Kornev (JIRA)]

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

Andrey Kornev edited comment on IGNITE-2004 at 12/15/15 4:39 PM:
-

Just wanted to clarify that the same limitation applies to the query listeners 
(unless the term "filter" is used loosely to also include the listeners): they 
are invoked synchronously by the same thread that has caused the cache event.

The JCache's cache listener functionality suffers from the same problem since 
it's implemented on top the CQ feature. Also, 
CacheEntryListenerConfiguration.isSynchronous() property is not respected by 
the current implementation: the listeners are invoked synchronously regardless 
of the value of the property.


was (Author: avk47):
Just wanted to clarify that the same limitation applies for the query listeners 
(unless the term "filter" here is used loosely to also include the listeners): 
they are invoked synchronously by the same thread that has caused the cache 
event.

The JCache's cache listener functionality suffers from the same problem since 
it's implemented on top the CQ feature. Also, 
CacheEntryListenerConfiguration.isSynchronous() property is not respected by 
the current implementation: the listeners are invoked synchronously regardless 
of the value of the property.

> Asynchronous execution of ContinuousQuery's remote filter
> -
>
> Key: IGNITE-2004
> URL: https://issues.apache.org/jira/browse/IGNITE-2004
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Valentin Kulichenko
> Fix For: 1.6
>
>
> Presently remote filters are executed synchronously an entry update. This 
> leads to the limitation when it's disallowed to perform cache related 
> operation in a filter body.
> It's required to add the ability to execute remote filters asynchronously. 
> This will let to execute any kind of operations including cache operations 
> directly in the filter body.
> The solution must be fault-tolerant. At least once execution of a filter in 
> case of a failure works fine. 



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

[jira] [Closed] (IGNITE-1162) Improve documentation for createCache* methods

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk closed IGNITE-1162.


> Improve documentation for createCache* methods
> --
>
> Key: IGNITE-1162
> URL: https://issues.apache.org/jira/browse/IGNITE-1162
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: sprint-7
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Javadoc lacks information about what happens when {{createCache()}} is called 
> and cache with the same name and different configuration already exists. What 
> happens when {{getOrCreateNearCache()}} is called when near cache with 
> different configuration already exists.



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

[jira] [Resolved] (IGNITE-2161) We need to tune Ignite site CSS to make it looks good for printing

[Dmitriyff (JIRA)]

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

Dmitriyff resolved IGNITE-2161.
---
Resolution: Fixed
  Assignee: Alexey Kuznetsov  (was: Dmitriyff)

updated styles to make it looks good on print mode

> We need to tune Ignite site CSS to make it looks good for printing
> --
>
> Key: IGNITE-2161
> URL: https://issues.apache.org/jira/browse/IGNITE-2161
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Open in chrome https://ignite.apache.org/benchmarks/ignite-vs-hazelcast.html
> Click Print -> looks ugly.
> See some ideas here: 
> http://www.creativebloq.com/responsive-web-design/make-your-website-printable-css-3132929



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

[jira] [Updated] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

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

Michael Griggs updated IGNITE-2169:
---
Fix Version/s: (was: 1.6)
   1.5

> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
> Fix For: 1.5
>
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)
> UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Assigned] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

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

Michael Griggs reassigned IGNITE-2169:
--

Assignee: Michael Griggs

> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
> Fix For: 1.6
>
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)
> UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Updated] (IGNITE-2173) Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with if (log.isDebugEnabled())

[Michael Griggs (JIRA)]

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

Michael Griggs updated IGNITE-2173:
---
Fix Version/s: 1.6

> Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with 
> if (log.isDebugEnabled())
> --
>
> Key: IGNITE-2173
> URL: https://issues.apache.org/jira/browse/IGNITE-2173
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Priority: Minor
> Fix For: 1.6
>
>
> e.g., line 1029
> {code}
> log.debug("Write entries to db one by one using update and insert statements 
> [cache name=" +
> {code}
> A side-effect of this is WARNing messages in your log file when these 
> statements are executed:
> {code}
> 2015-12-15 16:19:26 WARN  CacheJdbcPojoStore:463 - Logging at DEBUG level 
> without checking if DEBUG level is enabled: 
> {code}



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

[jira] [Comment Edited] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-2169 at 12/15/15 5:45 PM:


Michael, it seems that fix will be quite simple.
I could review and merge your pull request.
But please, do not delay with your fix - we are going to release soon.


was (Author: kuaw26):
Michael, it seems that fix will be quite simple.
I could review you pull request.
But please, do not delay with your fix - we are going to release soon.

> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
> Fix For: 1.5
>
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)
> UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Commented] (IGNITE-2004) Asynchronous execution of ContinuousQuery's remote filter

[Andrey Kornev (JIRA)]

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

Andrey Kornev commented on IGNITE-2004:
---

Just wanted to clarify that the same limitation applies for the query listeners 
(unless the term "filter" here is used loosely to also include the listeners): 
they are invoked synchronously by the same thread that has caused the cache 
event.

The JCache's cache listener functionality suffers from the same problem since 
it's implemented on top the CQ feature. Also, 
CacheEntryListenerConfiguration.isSynchronous() property is not respected by 
the current implementation: the listeners are invoked synchronously regardless 
of the value of the property.

> Asynchronous execution of ContinuousQuery's remote filter
> -
>
> Key: IGNITE-2004
> URL: https://issues.apache.org/jira/browse/IGNITE-2004
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Valentin Kulichenko
> Fix For: 1.6
>
>
> Presently remote filters are executed synchronously an entry update. This 
> leads to the limitation when it's disallowed to perform cache related 
> operation in a filter body.
> It's required to add the ability to execute remote filters asynchronously. 
> This will let to execute any kind of operations including cache operations 
> directly in the filter body.
> The solution must be fault-tolerant. At least once execution of a filter in 
> case of a failure works fine. 



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

[jira] [Updated] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

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

Michael Griggs updated IGNITE-2169:
---
Fix Version/s: 1.6

> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
> Fix For: 1.6
>
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)
> UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Commented] (IGNITE-2173) Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with if (log.isDebugEnabled())

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-2173:
--

Micael, this was an issue in ignite-1.4 release, but I fixed that in ignite-1.5 
code base.
Could you recheck?
See: 
https://github.com/apache/ignite/blob/ignite-1.5/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheAbstractJdbcStore.java
log.debug() is now protected with log.isDebugEnabled()

> Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with 
> if (log.isDebugEnabled())
> --
>
> Key: IGNITE-2173
> URL: https://issues.apache.org/jira/browse/IGNITE-2173
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
>Priority: Minor
> Fix For: 1.6
>
>
> e.g., line 1029
> {code}
> log.debug("Write entries to db one by one using update and insert statements 
> [cache name=" +
> {code}
> A side-effect of this is WARNing messages in your log file when these 
> statements are executed:
> {code}
> 2015-12-15 16:19:26 WARN  CacheJdbcPojoStore:463 - Logging at DEBUG level 
> without checking if DEBUG level is enabled: 
> {code}



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

[jira] [Comment Edited] (IGNITE-2173) Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with if (log.isDebugEnabled())

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-2173 at 12/15/15 5:40 PM:


Micael, this was an issue in ignite-1.4 release, but I fixed that in ignite-1.5 
code base several weeks ago.
Could you recheck?
See: 
https://github.com/apache/ignite/blob/ignite-1.5/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheAbstractJdbcStore.java
log.debug() is now protected with log.isDebugEnabled()


was (Author: kuaw26):
Micael, this was an issue in ignite-1.4 release, but I fixed that in ignite-1.5 
code base.
Could you recheck?
See: 
https://github.com/apache/ignite/blob/ignite-1.5/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheAbstractJdbcStore.java
log.debug() is now protected with log.isDebugEnabled()

> Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with 
> if (log.isDebugEnabled())
> --
>
> Key: IGNITE-2173
> URL: https://issues.apache.org/jira/browse/IGNITE-2173
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
>Priority: Minor
> Fix For: 1.6
>
>
> e.g., line 1029
> {code}
> log.debug("Write entries to db one by one using update and insert statements 
> [cache name=" +
> {code}
> A side-effect of this is WARNing messages in your log file when these 
> statements are executed:
> {code}
> 2015-12-15 16:19:26 WARN  CacheJdbcPojoStore:463 - Logging at DEBUG level 
> without checking if DEBUG level is enabled: 
> {code}



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

[jira] [Commented] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-2169:
--

Michael, it seems that fix will be quite simple.
I could review you pull request.
But please, do not delay with your fix - we are going to release soon.

> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Michael Griggs
> Fix For: 1.5
>
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)
> UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Assigned] (IGNITE-1996) NPE in case of not valid QueryEntity configuration

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova reassigned IGNITE-1996:
--

Assignee: Pavel Konstantinov  (was: Vasilisa  Sidorova)

Pavel, could you, please, verify this fix? Unfortunately, it takes too many 
time for me.

> NPE in case of not valid QueryEntity configuration
> --
>
> Key: IGNITE-1996
> URL: https://issues.apache.org/jira/browse/IGNITE-1996
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> In case if user specified in xml configuration not existing value for 
> QueryEntity.valueType that GridQueryProcessor failed with NPE, but should 
> throw appropriate exception with name of invalid class name.
> {code}
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$DBTypeEnum.fromClass(IgniteH2Indexing.java:1704)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dbTypeFromClass(IgniteH2Indexing.java:1175)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:1146)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1050)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:253)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:374)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1015)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:786)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:944)
> {code}



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

[jira] [Resolved] (IGNITE-2155) CacheStarSchemaExample isn't clear and it seems the output is wrong

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-2155.
--
Resolution: Fixed
  Assignee: Ilya Suntsov  (was: Alexey Kuznetsov)

ScalarSnowflakeSchemaExample fixed in the same way as for same java examplr in 
ignite-1.5.

Please retest.

> CacheStarSchemaExample isn't clear and it seems the output is wrong
> ---
>
> Key: IGNITE-2155
> URL: https://issues.apache.org/jira/browse/IGNITE-2155
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Ilya Suntsov
> Fix For: 1.5
>
>
> I run 
> {{org.apache.ignite.examples.datagrid.starschema.CacheStarSchemaExample}} and 
> can't understand what actually it does and what the ouptut means (e.g. why 
> all Ids are negative numbers)?
> {noformat}
> All purchases made at store1:
> FactPurchase [id=-1604674364, productId=-1604674374, storeId=-1604674395, 
> purchasePrice=10.0]
> FactPurchase [id=-1604674362, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=12.0]
> FactPurchase [id=-1604674349, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=25.0]
> FactPurchase [id=-1604674346, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=28.0]
> FactPurchase [id=-1604674343, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=31.0]
> FactPurchase [id=-1604674342, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=32.0]
> FactPurchase [id=-1604674337, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=37.0]
> FactPurchase [id=-1604674332, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=42.0]
> FactPurchase [id=-1604674325, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=49.0]
> FactPurchase [id=-1604674323, productId=-1604674391, storeId=-1604674395, 
> purchasePrice=51.0]
> FactPurchase [id=-1604674317, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=57.0]
> FactPurchase [id=-1604674316, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=58.0]
> FactPurchase [id=-1604674311, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=63.0]
> FactPurchase [id=-1604674305, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=69.0]
> FactPurchase [id=-1604674300, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=74.0]
> FactPurchase [id=-1604674296, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=78.0]
> FactPurchase [id=-1604674295, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=79.0]
> FactPurchase [id=-1604674293, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=81.0]
> FactPurchase [id=-1604674289, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=85.0]
> FactPurchase [id=-1604674285, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=89.0]
> FactPurchase [id=-1604674281, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=93.0]
> FactPurchase [id=-1604674371, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=3.0]
> FactPurchase [id=-1604674370, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=4.0]
> FactPurchase [id=-1604674368, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=6.0]
> FactPurchase [id=-1604674363, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=11.0]
> FactPurchase [id=-1604674357, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=17.0]
> FactPurchase [id=-1604674355, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=19.0]
> FactPurchase [id=-1604674353, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=21.0]
> FactPurchase [id=-1604674348, productId=-1604674376, storeId=-1604674395, 
> purchasePrice=26.0]
> FactPurchase [id=-1604674340, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=34.0]
> FactPurchase [id=-1604674339, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=35.0]
> FactPurchase [id=-1604674336, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=38.0]
> FactPurchase [id=-1604674335, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=39.0]
> FactPurchase [id=-1604674333, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=41.0]
> FactPurchase [id=-1604674331, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=43.0]
> FactPurchase [id=-1604674329, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=45.0]
> FactPurchase [id=-1604674327, productId=-1604674391, storeId=-1604674395, 
> purchasePrice=47.0]
> FactPurchase [id=-1604674322, productId=-1604674385, storeId=-1604674395, 
> 

[jira] [Resolved] (IGNITE-1861) We should not save metadata if it contains incompleted index

[Alexey Kuznetsov (JIRA)]

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

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

Fixed on staging.

> We should not save metadata if it contains incompleted index
> 
>
> Key: IGNITE-1861
> URL: https://issues.apache.org/jira/browse/IGNITE-1861
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> 1)Add new metadata
> 2)Add index but not add the fields in it
> 3)Save
> Observed - successfully saved
> Expected - error that index is incomplete



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

[jira] [Created] (IGNITE-2164) CPP: Namespace/class desciptions are missing in generated docs.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2164:
---

 Summary: CPP: Namespace/class desciptions are missing in generated 
docs.
 Key: IGNITE-2164
 URL: https://issues.apache.org/jira/browse/IGNITE-2164
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.5






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

[jira] [Closed] (IGNITE-2082) Documentation for C++/.Net missed in fabric binary package

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-2082.
---

> Documentation for C++/.Net missed in fabric binary package
> --
>
> Key: IGNITE-2082
> URL: https://issues.apache.org/jira/browse/IGNITE-2082
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Sergey Kozlov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> There's no documentation generated by Doxygen for /platforms/cpp and 
> platforms/dotnet in Apache Ignite fabric binary package



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

[jira] [Updated] (IGNITE-2129) .Net examples need to update xmldoc

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2129:

Component/s: interop

> .Net examples need to update xmldoc
> ---
>
> Key: IGNITE-2129
> URL: https://issues.apache.org/jira/browse/IGNITE-2129
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win7, Apache Ignite 1.5.0-b2 build #103
>Reporter: Vasilisa  Sidorova
>Assignee: Pavel Tupitsyn
> Fix For: 1.5
>
>
> Actual result: all .Net examples have  item:
> {noformat}
> This example can be run with standalone Apache Ignite.NET node:
> /// 1) Run 
> %IGNITE_HOME%/platforms/dotnet/Apache.Ignite/bin/${Platform]/${Configuration}/Apache.Ignite.exe:
> {noformat}
> in xmldoc
> Expected result:  .Net examples should have follow item instead:
> {noformat}
>  This example can be run with standalone Apache Ignite.NET node:
> /// 1) Run %IGNITE_HOME%/platforms/dotnet/bin/Apache.Ignite.exe:
> {noformat}
>  



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

[jira] [Closed] (IGNITE-1486) Revisit newly added Portable API

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-1486.
---

> Revisit newly added Portable API
> 
>
> Key: IGNITE-1486
> URL: https://issues.apache.org/jira/browse/IGNITE-1486
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Dmitriy Setrakyan
>Priority: Critical
> Fix For: 1.5
>
>
> GridGain contributed this API to Apache Ignite project and the API became 
> available for developers several merges ago.
> However, it makes sense to revisit/rework this API removing design issues 
> inherited from the time when it was a part of GridGain. That's why Portable 
> API won't be a part of public API in upcoming 1.4 release.
> Portable API is located in the following packages:
> - org.apache.ignite.marshaller.portable package (contains PortableMarshaller 
> only);
> - org.apache.ignite.portable package (PortableObject, PortableBuilder, 
> PortableMetadata, etc.);
> New methods are added to some existed public interfaces:
> - Ignite.portables();
> - CacheConfiguration.keepPortableInStore();
> - IgniteCache.withKeepPortable()



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

[jira] [Resolved] (IGNITE-2129) .Net examples need to update xmldoc

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-2129.
-
Resolution: Fixed
  Assignee: Vladimir Ozerov  (was: Pavel Tupitsyn)

Fixed.

> .Net examples need to update xmldoc
> ---
>
> Key: IGNITE-2129
> URL: https://issues.apache.org/jira/browse/IGNITE-2129
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win7, Apache Ignite 1.5.0-b2 build #103
>Reporter: Vasilisa  Sidorova
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> Actual result: all .Net examples have  item:
> {noformat}
> This example can be run with standalone Apache Ignite.NET node:
> /// 1) Run 
> %IGNITE_HOME%/platforms/dotnet/Apache.Ignite/bin/${Platform]/${Configuration}/Apache.Ignite.exe:
> {noformat}
> in xmldoc
> Expected result:  .Net examples should have follow item instead:
> {noformat}
>  This example can be run with standalone Apache Ignite.NET node:
> /// 1) Run %IGNITE_HOME%/platforms/dotnet/bin/Apache.Ignite.exe:
> {noformat}
>  



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

[jira] [Updated] (IGNITE-2129) .Net examples need to update xmldoc

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2129:

Assignee: (was: Vladimir Ozerov)

> .Net examples need to update xmldoc
> ---
>
> Key: IGNITE-2129
> URL: https://issues.apache.org/jira/browse/IGNITE-2129
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win7, Apache Ignite 1.5.0-b2 build #103
>Reporter: Vasilisa  Sidorova
> Fix For: 1.5
>
>
> Actual result: all .Net examples have  item:
> {noformat}
> This example can be run with standalone Apache Ignite.NET node:
> /// 1) Run 
> %IGNITE_HOME%/platforms/dotnet/Apache.Ignite/bin/${Platform]/${Configuration}/Apache.Ignite.exe:
> {noformat}
> in xmldoc
> Expected result:  .Net examples should have follow item instead:
> {noformat}
>  This example can be run with standalone Apache Ignite.NET node:
> /// 1) Run %IGNITE_HOME%/platforms/dotnet/bin/Apache.Ignite.exe:
> {noformat}
>  



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

[jira] [Created] (IGNITE-2165) CPP: Tableu displays textual data in wrong locale.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2165:
---

 Summary: CPP: Tableu displays textual data in wrong locale.
 Key: IGNITE-2165
 URL: https://issues.apache.org/jira/browse/IGNITE-2165
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


By some reason Tableu displays strings in wrong locale when using our ODBC 
driver.



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

[jira] [Updated] (IGNITE-2165) CPP: Tableu displays textual data in wrong locale.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2165:

Attachment: screenshot-1.png

> CPP: Tableu displays textual data in wrong locale.
> --
>
> Key: IGNITE-2165
> URL: https://issues.apache.org/jira/browse/IGNITE-2165
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
> Attachments: screenshot-1.png
>
>
> By some reason Tableu displays strings in wrong locale when using our ODBC 
> driver.



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

[jira] [Closed] (IGNITE-1861) We should not save metadata if it contains incompleted index

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> We should not save metadata if it contains incompleted index
> 
>
> Key: IGNITE-1861
> URL: https://issues.apache.org/jira/browse/IGNITE-1861
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> 1)Add new metadata
> 2)Add index but not add the fields in it
> 3)Save
> Observed - successfully saved
> Expected - error that index is incomplete



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

[jira] [Updated] (IGNITE-2159) Platforms examples couldn't be executed under 32-bit OS

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2159:

Fix Version/s: (was: 1.6)
   1.5

> Platforms examples couldn't be executed under 32-bit OS
> ---
>
> Key: IGNITE-2159
> URL: https://issues.apache.org/jira/browse/IGNITE-2159
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
> Environment: Win XP 32-bits, MS VS 2010, MS SDK 7.0, Apache Ignite 
> 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
> Fix For: 1.5
>
> Attachments: ignite_cpp_x86.png
>
>
> -
> DESCRIPTION
> -
> Platforms examples couldn't be executed under 32-bit OS
> -
> STEPS FOR REPRODUCE
> -
> # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite_x86.sln
> # Open and build 
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln (select 
> proper platform  -  x86)
> # Run the solution
> -
> ACTUAL RESULT
> -
> Follow error appears: "The procedure entry point InterlockedCompareExchange64 
> could not be located in the dynamic link library KERNEL32.dll". Look at the 
> attached picture
> -
> EXPECTED RESULT
> -
> Example should be executed
> -
> ADDITIONAL INFO
> -
> # Also reproducible for .Net examples
> # Wasn't reproducible for the same configuration about 4 month ago (near of 
> the Apache Ignite 1.3.3-rc1)



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

[jira] [Updated] (IGNITE-2159) Platforms examples couldn't be executed under 32-bit OS

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2159:

Component/s: interop

> Platforms examples couldn't be executed under 32-bit OS
> ---
>
> Key: IGNITE-2159
> URL: https://issues.apache.org/jira/browse/IGNITE-2159
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win XP 32-bits, MS VS 2010, MS SDK 7.0, Apache Ignite 
> 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
> Fix For: 1.5
>
> Attachments: ignite_cpp_x86.png
>
>
> -
> DESCRIPTION
> -
> Platforms examples couldn't be executed under 32-bit OS
> -
> STEPS FOR REPRODUCE
> -
> # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite_x86.sln
> # Open and build 
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln (select 
> proper platform  -  x86)
> # Run the solution
> -
> ACTUAL RESULT
> -
> Follow error appears: "The procedure entry point InterlockedCompareExchange64 
> could not be located in the dynamic link library KERNEL32.dll". Look at the 
> attached picture
> -
> EXPECTED RESULT
> -
> Example should be executed
> -
> ADDITIONAL INFO
> -
> # Also reproducible for .Net examples
> # Wasn't reproducible for the same configuration about 4 month ago (near of 
> the Apache Ignite 1.3.3-rc1)



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

[jira] [Updated] (IGNITE-2138) Add toBuilder() method on BinaryObject interface

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2138:

Component/s: interop
 general

> Add toBuilder() method on BinaryObject interface
> 
>
> Key: IGNITE-2138
> URL: https://issues.apache.org/jira/browse/IGNITE-2138
> Project: Ignite
>  Issue Type: Improvement
>  Components: general, interop
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Creating this ticket as per this devlist thread:
> http://apache-ignite-developers.2346864.n4.nabble.com/BinaryObjectBuilder-in-EntryProcessor-td5743.html



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

[jira] [Updated] (IGNITE-2065) Need to get rid of 'Portable' word in internals

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2065:

Component/s: interop
 general

> Need to get rid of 'Portable' word in internals
> ---
>
> Key: IGNITE-2065
> URL: https://issues.apache.org/jira/browse/IGNITE-2065
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Artem Shutak
> Fix For: 1.5
>
>
> Currently there is a bunch of objects that were kept from Portable objects 
> migration, such as PortableContext and portable package. Need to rename them 
> to Binary*.



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

[jira] [Updated] (IGNITE-2163) CPP: ODBC driver supported version should be upgraded to 3.x

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2163:

Component/s: odbc

> CPP: ODBC driver supported version should be upgraded to 3.x
> 
>
> Key: IGNITE-2163
> URL: https://issues.apache.org/jira/browse/IGNITE-2163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Currently our implementation of the ODBC driver states that it supports ODBC 
> standard version 2.0. It seems that many features that Tablue uses are not 
> supported in this version of the ODBC. So we need to set our version to 3.x 
> and make sure it works.



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

[jira] [Created] (IGNITE-2163) CPP: ODBC driver supported version should be upgraded to 3.x

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2163:
---

 Summary: CPP: ODBC driver supported version should be upgraded to 
3.x
 Key: IGNITE-2163
 URL: https://issues.apache.org/jira/browse/IGNITE-2163
 Project: Ignite
  Issue Type: Task
Reporter: Igor Sapego
Assignee: Igor Sapego


Currently our implementation of the ODBC driver states that it supports ODBC 
standard version 2.0. It seems that many features that Tablue uses are not 
supported in this version of the ODBC. So we need to set our version to 3.x and 
make sure it works.



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

[jira] [Updated] (IGNITE-2163) CPP: ODBC driver supported version should be upgraded to 3.x

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2163:

Fix Version/s: 1.6

> CPP: ODBC driver supported version should be upgraded to 3.x
> 
>
> Key: IGNITE-2163
> URL: https://issues.apache.org/jira/browse/IGNITE-2163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Currently our implementation of the ODBC driver states that it supports ODBC 
> standard version 2.0. It seems that many features that Tablue uses are not 
> supported in this version of the ODBC. So we need to set our version to 3.x 
> and make sure it works.



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

[jira] [Commented] (IGNITE-2082) Documentation for C++/.Net missed in fabric binary package

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2082:
-

Fixed CPP project name. Another problem - missing namespace and class 
descriptions. To be addressed in a separate ticket.

> Documentation for C++/.Net missed in fabric binary package
> --
>
> Key: IGNITE-2082
> URL: https://issues.apache.org/jira/browse/IGNITE-2082
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Sergey Kozlov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> There's no documentation generated by Doxygen for /platforms/cpp and 
> platforms/dotnet in Apache Ignite fabric binary package



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

[jira] [Updated] (IGNITE-2159) Platforms examples couldn't be executed under 32-bit OS

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2159:

Priority: Critical  (was: Major)

> Platforms examples couldn't be executed under 32-bit OS
> ---
>
> Key: IGNITE-2159
> URL: https://issues.apache.org/jira/browse/IGNITE-2159
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win XP 32-bits, MS VS 2010, MS SDK 7.0, Apache Ignite 
> 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ignite_cpp_x86.png
>
>
> -
> DESCRIPTION
> -
> Platforms examples couldn't be executed under 32-bit OS
> -
> STEPS FOR REPRODUCE
> -
> # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite_x86.sln
> # Open and build 
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln (select 
> proper platform  -  x86)
> # Run the solution
> -
> ACTUAL RESULT
> -
> Follow error appears: "The procedure entry point InterlockedCompareExchange64 
> could not be located in the dynamic link library KERNEL32.dll". Look at the 
> attached picture
> -
> EXPECTED RESULT
> -
> Example should be executed
> -
> ADDITIONAL INFO
> -
> # Also reproducible for .Net examples
> # Wasn't reproducible for the same configuration about 4 month ago (near of 
> the Apache Ignite 1.3.3-rc1)



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

[jira] [Assigned] (IGNITE-2159) Platforms examples couldn't be executed under 32-bit OS

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-2159:
---

Assignee: Igor Sapego

> Platforms examples couldn't be executed under 32-bit OS
> ---
>
> Key: IGNITE-2159
> URL: https://issues.apache.org/jira/browse/IGNITE-2159
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win XP 32-bits, MS VS 2010, MS SDK 7.0, Apache Ignite 
> 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ignite_cpp_x86.png
>
>
> -
> DESCRIPTION
> -
> Platforms examples couldn't be executed under 32-bit OS
> -
> STEPS FOR REPRODUCE
> -
> # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite_x86.sln
> # Open and build 
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln (select 
> proper platform  -  x86)
> # Run the solution
> -
> ACTUAL RESULT
> -
> Follow error appears: "The procedure entry point InterlockedCompareExchange64 
> could not be located in the dynamic link library KERNEL32.dll". Look at the 
> attached picture
> -
> EXPECTED RESULT
> -
> Example should be executed
> -
> ADDITIONAL INFO
> -
> # Also reproducible for .Net examples
> # Wasn't reproducible for the same configuration about 4 month ago (near of 
> the Apache Ignite 1.3.3-rc1)



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

[jira] [Reopened] (IGNITE-2162) Add vendor jdbc prefix to JDBC url in 'secret.properties' file

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reopened IGNITE-2162:

  Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Add vendor jdbc prefix to JDBC url in 'secret.properties' file
> --
>
> Key: IGNITE-2162
> URL: https://issues.apache.org/jira/browse/IGNITE-2162
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 1.6
>
>
> Currently for example for DB2 we generate the following secret.properties 
> body:
> {code}
> ds.jdbc.url=YOUR_JDBC_URL
> {code}
> This will be a bit better if template for JDBC URL will be inserted:
> {code}
> ds.jdbc.url=jdbc:oracle:thin:@[host]:[port]:[database]
> {code}



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

[jira] [Commented] (IGNITE-2162) Add vendor jdbc prefix to JDBC url in 'secret.properties' file

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2162:


Unused property:
{code}
postgres.jdbc.url=jdbc:postgresql://[host]:[port]/[database]
{code}

> Add vendor jdbc prefix to JDBC url in 'secret.properties' file
> --
>
> Key: IGNITE-2162
> URL: https://issues.apache.org/jira/browse/IGNITE-2162
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> Currently for example for DB2 we generate the following secret.properties 
> body:
> {code}
> ds.jdbc.url=YOUR_JDBC_URL
> {code}
> This will be a bit better if template for JDBC URL will be inserted:
> {code}
> ds.jdbc.url=jdbc:oracle:thin:@[host]:[port]:[database]
> {code}



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

[jira] [Closed] (IGNITE-2154) .NET: doxygen docs generation must be included into Maven build process.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-2154.
---

> .NET: doxygen docs generation must be included into Maven build process.
> 
>
> Key: IGNITE-2154
> URL: https://issues.apache.org/jira/browse/IGNITE-2154
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




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

[jira] [Resolved] (IGNITE-2162) Add vendor jdbc prefix to JDBC url in 'secret.properties' file

[Alexey Kuznetsov (JIRA)]

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

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

> Add vendor jdbc prefix to JDBC url in 'secret.properties' file
> --
>
> Key: IGNITE-2162
> URL: https://issues.apache.org/jira/browse/IGNITE-2162
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> Currently for example for DB2 we generate the following secret.properties 
> body:
> {code}
> ds.jdbc.url=YOUR_JDBC_URL
> {code}
> This will be a bit better if template for JDBC URL will be inserted:
> {code}
> ds.jdbc.url=jdbc:oracle:thin:@[host]:[port]:[database]
> {code}



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

[jira] [Commented] (IGNITE-2162) Add vendor jdbc prefix to JDBC url in 'secret.properties' file

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-2162:
--

Fixed

> Add vendor jdbc prefix to JDBC url in 'secret.properties' file
> --
>
> Key: IGNITE-2162
> URL: https://issues.apache.org/jira/browse/IGNITE-2162
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 1.6
>
>
> Currently for example for DB2 we generate the following secret.properties 
> body:
> {code}
> ds.jdbc.url=YOUR_JDBC_URL
> {code}
> This will be a bit better if template for JDBC URL will be inserted:
> {code}
> ds.jdbc.url=jdbc:oracle:thin:@[host]:[port]:[database]
> {code}



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

[jira] [Commented] (IGNITE-2065) Need to get rid of 'Portable' word in internals

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-2065:
--

Finished with renaming. Will check on tests that I can affect in process of 
renaming.

> Need to get rid of 'Portable' word in internals
> ---
>
> Key: IGNITE-2065
> URL: https://issues.apache.org/jira/browse/IGNITE-2065
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Artem Shutak
> Fix For: 1.5
>
>
> Currently there is a bunch of objects that were kept from Portable objects 
> migration, such as PortableContext and portable package. Need to rename them 
> to Binary*.



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

[jira] [Commented] (IGNITE-2158) Null values in output of CacheDummyStoreExample, CacheJdbcStoreExample and CacheSpringStoreExample

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-2158:
---

It is so that CacheDummyStoreExample, CacheJdbcStoreExample and 
CacheSpringStoreExample cannot work in distributed cluster since each node 
starts its own store and this prevents us from demonstrating clear() and 
withSkipStore(). 

Examples should be fixed to use single store instance or removed from project.

I tried modifying 
org.apache.ignite.examples.datagrid.store.dummy.CacheDummyStoreExample#executeTransaction
 in the following manner.

{code}
private static void executeTransaction(IgniteCache cache) {
try (Transaction tx = Ignition.ignite().transactions().txStart()) {
Person val = cache.get(id);
System.out.println("Read value: " + val);
val = cache.getAndPut(id, new Person(id, "Isaac", "Newton"));
System.out.println("Overwrote old value: " + val);
val = cache.get(id);
System.out.println("Read value: " + val);
tx.commit();
}
System.out.println("Read value after commit: " + cache.get(id));
// Clear entry from memory, but keep it in store.
cache.clear(id);
// Operations on this cache will not affect store.
IgniteCache cacheSkipStore = cache.withSkipStore();
System.out.println("Read value skipping store (expecting null): " + 
cacheSkipStore.get(id));
System.out.println("Read value with store lookup (expecting NOT null): 
" + cache.get(id));
// Expecting not null, since entry should be in memory since last call.
System.out.println("Read value skipping store (expecting NOT null): " + 
cacheSkipStore.get(id));
}
{code}

Then I started 3 remote nodes with {{ExampleNodeStartup}}

And output was:
{code}
>>> Cache store example started.
>>> Store loadCache for entry count: 10
>>> Loaded 10 keys with backups in 1639ms.
Read value: null
Overwrote old value: null
Read value: Person [id=8653755053717283485, orgId=null, lastName=Newton, 
firstName=Isaac, salary=0.0, resume=null]
>>> Store put [key=8653755053717283485, val=Person [id=8653755053717283485, 
>>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null], 
>>> xid=3d32135a151-03acc8a8--0006--0151a530c95b]
Read value after commit: Person [id=8653755053717283485, orgId=null, 
lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
Read value skipping store (expecting null): null
Read value with store lookup (expecting NOT null): null
Read value skipping store (expecting NOT null): null
{code}

> Null values in output of CacheDummyStoreExample, CacheJdbcStoreExample and 
> CacheSpringStoreExample
> --
>
> Key: IGNITE-2158
> URL: https://issues.apache.org/jira/browse/IGNITE-2158
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: OS X 10.10.2
> jdk 1.7
>Reporter: Ilya Suntsov
> Fix For: 1.5
>
>
> In output of the following examples there are fields that have 'null' or zero 
> values (salary, orgId, resume ):
> 1.CacheDummyStoreExample
> {noformat}
> [16:48:47] Ignite node started OK (id=64a079ad)
> [16:48:47] Topology snapshot [ver=9, servers=3, clients=0, CPUs=8, heap=8.0GB]
> >>> Cache store example started.
> >>> Store loadCache for entry count: 10
> >>> Loaded 10 keys with backups in 971ms.
> Read value: null
> Overwrote old value: null
> Read value: Person [id=7754401276845136764, orgId=null, lastName=Newton, 
> firstName=Isaac, salary=0.0, resume=null]
> >>> Store put [key=7754401276845136764, val=Person [id=7754401276845136764, 
> >>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null], 
> >>> xid=ab2b0c0a151-03aba62c--0009--0151a0c0307a]
> Read value after commit: Person [id=7754401276845136764, orgId=null, 
> lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
> [16:48:48] Ignite node stopped OK [uptime=00:00:01:38]
> {noformat}
> 2. CacheJdbcStoreExample
> {noformat}
> [16:49:36] Ignite node started OK (id=f662db78)
> [16:49:36] Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, 
> heap=8.0GB]
> >>> Cache store example started.
> >>> Loaded 0 values into cache.
> >>> Loaded 1 keys with backups in 26ms.
> >>> Store load [key=8980561285181288706]
> Read value: null
> Overwrote old value: null
> Read value: Person [id=8980561285181288706, orgId=null, lastName=Newton, 
> firstName=Isaac, salary=0.0, resume=null]
> >>> Store write [key=8980561285181288706, val=Person [id=8980561285181288706, 
> >>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null]]
> Read value after commit: 

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2122:


1) Ok
2) Then we should only keep non-generic methods without adders. Which is the 
best approach, probably. There is no point in providing half-baked generic 
support, user can simply call OfType<>() on a non-generic ICollection and be 
done with it.

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




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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2016:
-

Roman, thanks for the contribution! Someone from the community will review your 
changes soon.

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Created] (IGNITE-2167) Create cross-platform example

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2167:
---

 Summary: Create cross-platform example
 Key: IGNITE-2167
 URL: https://issues.apache.org/jira/browse/IGNITE-2167
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


We might want to introduce a new example demonstrating cross-platform 
communication between Java, CPP and .NET.



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

[jira] [Commented] (IGNITE-2159) Platforms examples couldn't be executed under 32-bit OS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2159:


GitHub user isapego opened a pull request:

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

IGNITE-2159: Implemented 64-bit atomics with supported functions.



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

$ git pull https://github.com/isapego/ignite ignite-2159

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

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


commit 19abcd547ba1d35fc28719726f1e4881c02e9cda
Author: isapego 
Date:   2015-12-15T10:24:34Z

IGNITE-2159: IMplemented 64-bit atomics with supported functions.




> Platforms examples couldn't be executed under 32-bit OS
> ---
>
> Key: IGNITE-2159
> URL: https://issues.apache.org/jira/browse/IGNITE-2159
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win XP 32-bits, MS VS 2010, MS SDK 7.0, Apache Ignite 
> 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ignite_cpp_x86.png
>
>
> -
> DESCRIPTION
> -
> Platforms examples couldn't be executed under 32-bit OS
> -
> STEPS FOR REPRODUCE
> -
> # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite_x86.sln
> # Open and build 
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln (select 
> proper platform  -  x86)
> # Run the solution
> -
> ACTUAL RESULT
> -
> Follow error appears: "The procedure entry point InterlockedCompareExchange64 
> could not be located in the dynamic link library KERNEL32.dll". Look at the 
> attached picture
> -
> EXPECTED RESULT
> -
> Example should be executed
> -
> ADDITIONAL INFO
> -
> # Also reproducible for .Net examples
> # Wasn't reproducible for the same configuration about 4 month ago (near of 
> the Apache Ignite 1.3.3-rc1)



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

[jira] [Commented] (IGNITE-2164) CPP: Namespace/class descriptions are missing in generated docs.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2164:


GitHub user isapego opened a pull request:

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

IGNITE-2164: Added documentation brief description auto generation.



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

$ git pull https://github.com/isapego/ignite ignite-2164

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

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


commit 2962d92002e08717abcd1fe3e9f97017ed5a3a41
Author: isapego 
Date:   2015-12-15T10:51:33Z

IGNITE-2164: Added documentation brief description autogeneration.




> CPP: Namespace/class descriptions are missing in generated docs.
> 
>
> Key: IGNITE-2164
> URL: https://issues.apache.org/jira/browse/IGNITE-2164
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Fix For: 1.5
>
>




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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2122:
-

1) Split - separate methods for generic and non-generic collections.
2) IEnumerable is not needed in value objects. I can hardly imagine a situation 
where user operates on IEnumetables inside a class which is going to be passed 
over wire. So we should use ICollection as a most expected use case.
3) No need for any filtering or any other logic. This is collection write 
method. Any filtering must be done before user call this method.

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




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

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

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov closed IGNITE-2087.


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



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

[jira] [Commented] (IGNITE-1994) .Net: CrossPlatformExample looks unnecessary

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1994:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1994 .Net: CrossPlatformExample looks unnecessary



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

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

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

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


commit 98c73e6073e64b31e24fa277dafcd7d7692dfd64
Author: Pavel Tupitsyn 
Date:   2015-12-15T12:13:21Z

IGNITE-1994 .Net: CrossPlatformExample looks unnecessary




> .Net: CrossPlatformExample looks unnecessary
> 
>
> Key: IGNITE-1994
> URL: https://issues.apache.org/jira/browse/IGNITE-1994
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win7, Apache Ignite 1.5.0 build #82
>Reporter: Vasilisa  Sidorova
>Assignee: Pavel Tupitsyn
> Fix For: 1.5
>
>
> # At this moment there isn't Java and/or cpp CrossPlatform examples in the 
> project. So .Net CrossPlatformExample looks unnecessary
> # More over there isn't config 'bin\ignite.bat 
> examples\config\example-server.xml' in project so this example will fails 
> when user try to run it with remote node
> Proposal: delete example from project or, at least, update example's 
> description



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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2122:
-

Why are we going to force user using casts or OfType<> conversions if in 99% he 
will operate on generic collection? The most common case must require minimal 
actions from user. This is why we need to separate generic and non-generic 
cases.

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




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

[jira] [Closed] (IGNITE-2162) Add vendor jdbc prefix to JDBC url in 'secret.properties' file

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Add vendor jdbc prefix to JDBC url in 'secret.properties' file
> --
>
> Key: IGNITE-2162
> URL: https://issues.apache.org/jira/browse/IGNITE-2162
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> Currently for example for DB2 we generate the following secret.properties 
> body:
> {code}
> ds.jdbc.url=YOUR_JDBC_URL
> {code}
> This will be a bit better if template for JDBC URL will be inserted:
> {code}
> ds.jdbc.url=jdbc:oracle:thin:@[host]:[port]:[database]
> {code}



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

[jira] [Assigned] (IGNITE-2164) CPP: Namespace/class descriptions are missing in generated docs.

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-2164:
---

Assignee: Igor Sapego

> CPP: Namespace/class descriptions are missing in generated docs.
> 
>
> Key: IGNITE-2164
> URL: https://issues.apache.org/jira/browse/IGNITE-2164
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Fix For: 1.5
>
>




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

[jira] [Updated] (IGNITE-2168) SpringBeanExample fails after CacheBinaryAutoStoreExample

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-2168:
--
Description: 
1. Start remote node with examples/config/example-ignite.xml
2. Run DbH2ServerStartup
3. Run CacheBinaryAutoStoreExample ()
4. Run SpringBeanExample and get the following exception: 
{noformat}
>>> Spring bean example started.
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
[14:22:00]__   
[14:22:00]   /  _/ ___/ |/ /  _/_  __/ __/ 
[14:22:00]  _/ // (7 7// /  / / / _/   
[14:22:00] /___/\___/_/|_/___/ /_/ /___/  
[14:22:00] 
[14:22:00] ver. 1.5.0-b2#20151215-sha1:0c550aaa
[14:22:00] 2015 Copyright(C) Apache Software Foundation
[14:22:00] 
[14:22:00] Ignite documentation: http://ignite.apache.org
[14:22:00] 
[14:22:00] Quiet mode.
[14:22:00]   ^-- Logging to file 
'C:\Work\apache-ignite-fabric-1.5.0-b2-bin\work\log\ignite-0b6a932b.log'
[14:22:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[14:22:00] 
[14:22:00] OS: Windows 7 6.1 amd64
[14:22:00] VM information: Java(TM) SE Runtime Environment 1.7.0_80-b15 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 24.80-b11
[14:22:00] Initial heap size is 254MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[14:22:01] Configured plugins:
[14:22:01]   ^-- None
[14:22:01] 
[14:22:02] Security status [authentication=off, tls/ssl=off]
[14:22:03,911][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
class org.apache.ignite.IgniteException: Failed to load bean in application 
context [beanName=h2-example-db, 
igniteConfig=org.springframework.context.support.ClassPathXmlApplicationContext@7a64f150:
 startup date [Tue Dec 15 14:21:59 MSK 2015]; root of context hierarchy]
at 
org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:168)
at 
org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:96)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1243)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:774)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:945)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1659)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1518)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:974)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
at 
org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1627)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1564)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:540)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:302)
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:229)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:298)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:725)
at 
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480)
at 
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
at 
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
at 
org.apache.ignite.examples.misc.springbean.SpringBeanExample.main(Spring

[jira] [Created] (IGNITE-2168) SpringBeanExample fails after CacheBinaryAutoStoreExample

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2168:
-

 Summary: SpringBeanExample fails after CacheBinaryAutoStoreExample
 Key: IGNITE-2168
 URL: https://issues.apache.org/jira/browse/IGNITE-2168
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
 Fix For: 1.5


1. Start remote node with examples/config/example-ignite.xml
2. Run DbH2ServerStartup
3. Run CacheBinaryAutoStoreExample ()
4. Run SpringBeanExample: one failed: 
{noformat}
>>> Spring bean example started.
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
[14:22:00]__   
[14:22:00]   /  _/ ___/ |/ /  _/_  __/ __/ 
[14:22:00]  _/ // (7 7// /  / / / _/   
[14:22:00] /___/\___/_/|_/___/ /_/ /___/  
[14:22:00] 
[14:22:00] ver. 1.5.0-b2#20151215-sha1:0c550aaa
[14:22:00] 2015 Copyright(C) Apache Software Foundation
[14:22:00] 
[14:22:00] Ignite documentation: http://ignite.apache.org
[14:22:00] 
[14:22:00] Quiet mode.
[14:22:00]   ^-- Logging to file 
'C:\Work\apache-ignite-fabric-1.5.0-b2-bin\work\log\ignite-0b6a932b.log'
[14:22:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[14:22:00] 
[14:22:00] OS: Windows 7 6.1 amd64
[14:22:00] VM information: Java(TM) SE Runtime Environment 1.7.0_80-b15 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 24.80-b11
[14:22:00] Initial heap size is 254MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[14:22:01] Configured plugins:
[14:22:01]   ^-- None
[14:22:01] 
[14:22:02] Security status [authentication=off, tls/ssl=off]
[14:22:03,911][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
class org.apache.ignite.IgniteException: Failed to load bean in application 
context [beanName=h2-example-db, 
igniteConfig=org.springframework.context.support.ClassPathXmlApplicationContext@7a64f150:
 startup date [Tue Dec 15 14:21:59 MSK 2015]; root of context hierarchy]
at 
org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:168)
at 
org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:96)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1243)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:774)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:945)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1659)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1518)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:974)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
at 
org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1627)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1564)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:540)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:302)
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:229)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:298)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:725)
at 
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480)
at 
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicat

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2122:


1) What is the advantage?
2) I can easily imagine such situations, moreover, I've been there. You can 
never expect where "enterprisey" code takes you. Good API should accept the 
most general type possible. There is no single reason to restrict user to 
ICollection there. Especially when it is so easy to support on our side.
3) We are talking about read methods. Write methods do not have adders. 

Another example: user may operate on a Person set in his business logic, but 
use PersonDto to write/read them.
{code}
class Department
{
  MyCollection Persons {get;set;}

  void WriteBinary(..)
  {
writer.WriteCollection(Persons.Select(p => p.ToPersonDto()));
  }

  void ReadBinary(..)
  {
Persons = reader.ReadCollection(cnt => new MyCollection(cnt), 
(col, dto) => col.Insert(new Person(dto)));
  }
}

{code}

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




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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2122:


1) What do you mean by "split"? Rename?
2) We should not do this. Accepting IEnumerable in writer is very important, it 
is not a specific case. LINQ and yield-style enumerators return IEnumerable, we 
should not force the user to do an extra memory copy if we can easily write 
lazy enumeration directly to a stream.
3) Not sure about this either, current API avoids all possible casts on the 
user side, allows any kind of custom collection/dictionary, allows filtering 
and other processing in the adder. And it provides a simple overload without 
adder/factory.

Imagine that user wants to read collection into HashSet. Current API 
provides the most efficient way of doing this in one line. What you suggest 
will require allocating extra collection.

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




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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2122:
-

1) Advantage - no adders for generic collections. Only factory func is needed.
2) Our goal is to support the most common use cases. Any non-trivial stuff will 
be handled by user manually.
3) Ok.

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




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

[jira] [Assigned] (IGNITE-2158) Null values in output of CacheDummyStoreExample, CacheJdbcStoreExample and CacheSpringStoreExample

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov reassigned IGNITE-2158:
-

Assignee: Yakov Zhdanov

> Null values in output of CacheDummyStoreExample, CacheJdbcStoreExample and 
> CacheSpringStoreExample
> --
>
> Key: IGNITE-2158
> URL: https://issues.apache.org/jira/browse/IGNITE-2158
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: OS X 10.10.2
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Yakov Zhdanov
> Fix For: 1.5
>
>
> In output of the following examples there are fields that have 'null' or zero 
> values (salary, orgId, resume ):
> 1.CacheDummyStoreExample
> {noformat}
> [16:48:47] Ignite node started OK (id=64a079ad)
> [16:48:47] Topology snapshot [ver=9, servers=3, clients=0, CPUs=8, heap=8.0GB]
> >>> Cache store example started.
> >>> Store loadCache for entry count: 10
> >>> Loaded 10 keys with backups in 971ms.
> Read value: null
> Overwrote old value: null
> Read value: Person [id=7754401276845136764, orgId=null, lastName=Newton, 
> firstName=Isaac, salary=0.0, resume=null]
> >>> Store put [key=7754401276845136764, val=Person [id=7754401276845136764, 
> >>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null], 
> >>> xid=ab2b0c0a151-03aba62c--0009--0151a0c0307a]
> Read value after commit: Person [id=7754401276845136764, orgId=null, 
> lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
> [16:48:48] Ignite node stopped OK [uptime=00:00:01:38]
> {noformat}
> 2. CacheJdbcStoreExample
> {noformat}
> [16:49:36] Ignite node started OK (id=f662db78)
> [16:49:36] Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, 
> heap=8.0GB]
> >>> Cache store example started.
> >>> Loaded 0 values into cache.
> >>> Loaded 1 keys with backups in 26ms.
> >>> Store load [key=8980561285181288706]
> Read value: null
> Overwrote old value: null
> Read value: Person [id=8980561285181288706, orgId=null, lastName=Newton, 
> firstName=Isaac, salary=0.0, resume=null]
> >>> Store write [key=8980561285181288706, val=Person [id=8980561285181288706, 
> >>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null]]
> Read value after commit: Person [id=8980561285181288706, orgId=null, 
> lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
> [16:49:36] Ignite node stopped OK [uptime=00:00:00:182]
> {noformat}
> 3. CacheSpringStoreExample
> {noformat}
> [16:50:16] Ignite node started OK (id=670dd40a)
> [16:50:16] Topology snapshot [ver=13, servers=3, clients=0, CPUs=8, 
> heap=8.0GB]
> >>> Cache store example started.
> >>> Loaded 0 values into cache.
> >>> Loaded 0 keys with backups in 33ms.
> Read value: null
> Overwrote old value: null
> Read value: Person [id=8312945083421167351, orgId=null, lastName=Newton, 
> firstName=Isaac, salary=0.0, resume=null]
> >>> Store write [key=8312945083421167351, val=Person [id=8312945083421167351, 
> >>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null]]
> Read value after commit: Person [id=8312945083421167351, orgId=null, 
> lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
> [16:50:16] Ignite node stopped OK [uptime=00:00:00:469]
> {noformat}



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

[jira] [Commented] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2030:


I've checked all *.bat files, but I'm was not be able to reproduce this one "I 
just found that the node prints out the error below. As side-effect of this two 
nodes started via bat file and in IDEA with same configuration can't create a 
topology". Sergey, could you please check it?

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Commented] (IGNITE-2155) CacheStarSchemaExample isn't clear and it seems the output is wrong

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov commented on IGNITE-2155:
--

For 
{noformat}examples/src/main/java/org/apache/ignite/examples/datagrid/starschema/CacheStarSchemaExample.java
 {noformat}
fix confirmed but I observerd the same behavior for:
{noformat}examples/src/main/scala/org/apache/ignite/scalar/examples/ScalarSnowflakeSchemaExample.scala{noformat}

> CacheStarSchemaExample isn't clear and it seems the output is wrong
> ---
>
> Key: IGNITE-2155
> URL: https://issues.apache.org/jira/browse/IGNITE-2155
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Ilya Suntsov
> Fix For: 1.5
>
>
> I run 
> {{org.apache.ignite.examples.datagrid.starschema.CacheStarSchemaExample}} and 
> can't understand what actually it does and what the ouptut means (e.g. why 
> all Ids are negative numbers)?
> {noformat}
> All purchases made at store1:
> FactPurchase [id=-1604674364, productId=-1604674374, storeId=-1604674395, 
> purchasePrice=10.0]
> FactPurchase [id=-1604674362, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=12.0]
> FactPurchase [id=-1604674349, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=25.0]
> FactPurchase [id=-1604674346, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=28.0]
> FactPurchase [id=-1604674343, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=31.0]
> FactPurchase [id=-1604674342, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=32.0]
> FactPurchase [id=-1604674337, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=37.0]
> FactPurchase [id=-1604674332, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=42.0]
> FactPurchase [id=-1604674325, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=49.0]
> FactPurchase [id=-1604674323, productId=-1604674391, storeId=-1604674395, 
> purchasePrice=51.0]
> FactPurchase [id=-1604674317, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=57.0]
> FactPurchase [id=-1604674316, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=58.0]
> FactPurchase [id=-1604674311, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=63.0]
> FactPurchase [id=-1604674305, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=69.0]
> FactPurchase [id=-1604674300, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=74.0]
> FactPurchase [id=-1604674296, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=78.0]
> FactPurchase [id=-1604674295, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=79.0]
> FactPurchase [id=-1604674293, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=81.0]
> FactPurchase [id=-1604674289, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=85.0]
> FactPurchase [id=-1604674285, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=89.0]
> FactPurchase [id=-1604674281, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=93.0]
> FactPurchase [id=-1604674371, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=3.0]
> FactPurchase [id=-1604674370, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=4.0]
> FactPurchase [id=-1604674368, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=6.0]
> FactPurchase [id=-1604674363, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=11.0]
> FactPurchase [id=-1604674357, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=17.0]
> FactPurchase [id=-1604674355, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=19.0]
> FactPurchase [id=-1604674353, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=21.0]
> FactPurchase [id=-1604674348, productId=-1604674376, storeId=-1604674395, 
> purchasePrice=26.0]
> FactPurchase [id=-1604674340, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=34.0]
> FactPurchase [id=-1604674339, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=35.0]
> FactPurchase [id=-1604674336, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=38.0]
> FactPurchase [id=-1604674335, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=39.0]
> FactPurchase [id=-1604674333, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=41.0]
> FactPurchase [id=-1604674331, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=43.0]
> FactPurchase [id=-1604674329, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=45.0]
> FactPurchase [id=-1604674327, 

[jira] [Assigned] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov reassigned IGNITE-2030:
-

Assignee: Sergey Kozlov  (was: Vladimir Ershov)

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Updated] (IGNITE-2146) Service deployment using a cache-accessing-predicate in node filter sometimes causes a deadlock

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2146:
--
Fix Version/s: 1.5

> Service deployment using a cache-accessing-predicate in node filter sometimes 
> causes a deadlock
> ---
>
> Key: IGNITE-2146
> URL: https://issues.apache.org/jira/browse/IGNITE-2146
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4, 1.5
> Environment: Mac OS X 10.11
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Ignite 1.4.0 + Ignite-1.5.0-b1
>Reporter: Noam Liran
> Fix For: 1.5
>
> Attachments: stacktrace.txt
>
>
> We're deploying a service on a cluster group. The cluster group is filtered 
> using a predicate. The predicate accesses a cache key to determine if it 
> should return true for a node or not.
> If a new node joins the cluster while the predicate is running a deadlock is 
> encountered: cache functions do not return and the node does not finish 
> joining the cluster.
> I've created a sample program to reproduce this on 1.4.0 and also tried to 
> reproduce it on 1.5.0-b1;
> On 1.4.0 the deadlock is usually reproduced, on 1.5.0-b1 it might take a few 
> tries (I'm guessing it's a timing issue.. I tried to improve the odds of 
> reproduction by using a countdown latch).
> Code:
> {code:title=Main.java}
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.cluster.ClusterGroup;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> import java.util.concurrent.CountDownLatch;
> /**
>  * Created by noliran on 08/12/2015.
>  */
> public class Main {
> public static IgniteCache cache1;
> public static CountDownLatch latch = new CountDownLatch(1);
> public static CacheConfiguration CACHE_CONFIG = new 
> CacheConfiguration()
> .setName("testCache")
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
> .setCacheMode(CacheMode.REPLICATED)
> 
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.PRIMARY);
> public static void main(String[] args) throws InterruptedException {
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
> Ignite ignite1 = 
> Ignition.start(igniteConfiguration.setGridName("grid1"));
> System.out.println("Creating cache");
> cache1 = ignite1.getOrCreateCache(CACHE_CONFIG);
> ClusterGroup group = ignite1.cluster().forPredicate(node -> {
> System.out.println("predicate: starting");
> latch.countDown();
> try {
> System.out.println("predicate: before sleep");
> Thread.sleep(10_000);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> System.out.println("predicate: before containsKey");
> boolean b1 = cache1.containsKey(node.id().toString());
> System.out.println("predicate: returning");
> return b1;
> });
> System.out.println("Deploying service with cache-based predicate");
> new Thread(() -> {
> ignite1.services(group).deployNodeSingleton("testService", new 
> TestService());
> }).start();
> System.out.println("Service in deployment.");
> latch.await();
> System.out.println("Starting second Ignite instance..");
> Ignite ignite2 = 
> Ignition.start(igniteConfiguration.setGridName("grid2"));
> System.out.println("Second Ignite instance started successfully!"); 
> // This isn't going to be printed.
> }
> public static class TestService implements Service
> {
> public void execute(ServiceContext ctx) throws Exception { 
> System.out.println("execute()"); }
> public void init(ServiceContext ctx) throws Exception { 
> System.out.println("init()"); }
> public void cancel(ServiceContext ctx) { 
> System.out.println("cancel()"); }
> }
> }
> {code}
> Output:
> {noformat}
> [16:27:01]__   
> [16:27:01]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [16:27:01]  _/ 

[jira] [Resolved] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov resolved IGNITE-2030.
-

Fixed issue with visor. Please, check 

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-2122 at 12/15/15 12:37 PM:
---

With your approach of "ICollection ReadCollection" without factory/adder 
there WILL be additional action from the user 99% of the time, because, most 
likely, user needs some specific collection, like List<>, and we give him 
ICollection<>:
* List persons = reader.ReadCollection().ToList();
* List persons = reader.ReadGenericCollection().ToList()

This kind of generic support is rarely useful and will only confuse users.


was (Author: ptupitsyn):
With your approach of "ICollection ReadCollection" without factory/adder 
there WILL be additional action from the user 99% of the time, because, most 
likely, user needs some specific collection, like List<>, and we give him 
ICollection<>:
* List persons = reader.ReadCollection().ToList();
* List persons = reader.ReadGenericCollection().ToList()
This kind of generic support is rarely useful and will only confuse users.

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




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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2122:


With your approach of "ICollection ReadCollection" without factory/adder 
there WILL be additional action from the user 99% of the time, because, most 
likely, user needs some specific collection, like List<>, and we give him 
ICollection<>:
* List persons = reader.ReadCollection().ToList();
* List persons = reader.ReadGenericCollection().ToList()
This kind of generic support is rarely useful and will only confuse users.

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




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

[jira] [Updated] (IGNITE-2146) Service deployment using a cache-accessing-predicate in node filter sometimes causes a deadlock

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2146:
--
Assignee: Semen Boikov

> Service deployment using a cache-accessing-predicate in node filter sometimes 
> causes a deadlock
> ---
>
> Key: IGNITE-2146
> URL: https://issues.apache.org/jira/browse/IGNITE-2146
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4, 1.5
> Environment: Mac OS X 10.11
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Ignite 1.4.0 + Ignite-1.5.0-b1
>Reporter: Noam Liran
>Assignee: Semen Boikov
> Fix For: 1.5
>
> Attachments: stacktrace.txt
>
>
> We're deploying a service on a cluster group. The cluster group is filtered 
> using a predicate. The predicate accesses a cache key to determine if it 
> should return true for a node or not.
> If a new node joins the cluster while the predicate is running a deadlock is 
> encountered: cache functions do not return and the node does not finish 
> joining the cluster.
> I've created a sample program to reproduce this on 1.4.0 and also tried to 
> reproduce it on 1.5.0-b1;
> On 1.4.0 the deadlock is usually reproduced, on 1.5.0-b1 it might take a few 
> tries (I'm guessing it's a timing issue.. I tried to improve the odds of 
> reproduction by using a countdown latch).
> Code:
> {code:title=Main.java}
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.cluster.ClusterGroup;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> import java.util.concurrent.CountDownLatch;
> /**
>  * Created by noliran on 08/12/2015.
>  */
> public class Main {
> public static IgniteCache cache1;
> public static CountDownLatch latch = new CountDownLatch(1);
> public static CacheConfiguration CACHE_CONFIG = new 
> CacheConfiguration()
> .setName("testCache")
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
> .setCacheMode(CacheMode.REPLICATED)
> 
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.PRIMARY);
> public static void main(String[] args) throws InterruptedException {
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
> Ignite ignite1 = 
> Ignition.start(igniteConfiguration.setGridName("grid1"));
> System.out.println("Creating cache");
> cache1 = ignite1.getOrCreateCache(CACHE_CONFIG);
> ClusterGroup group = ignite1.cluster().forPredicate(node -> {
> System.out.println("predicate: starting");
> latch.countDown();
> try {
> System.out.println("predicate: before sleep");
> Thread.sleep(10_000);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> System.out.println("predicate: before containsKey");
> boolean b1 = cache1.containsKey(node.id().toString());
> System.out.println("predicate: returning");
> return b1;
> });
> System.out.println("Deploying service with cache-based predicate");
> new Thread(() -> {
> ignite1.services(group).deployNodeSingleton("testService", new 
> TestService());
> }).start();
> System.out.println("Service in deployment.");
> latch.await();
> System.out.println("Starting second Ignite instance..");
> Ignite ignite2 = 
> Ignition.start(igniteConfiguration.setGridName("grid2"));
> System.out.println("Second Ignite instance started successfully!"); 
> // This isn't going to be printed.
> }
> public static class TestService implements Service
> {
> public void execute(ServiceContext ctx) throws Exception { 
> System.out.println("execute()"); }
> public void init(ServiceContext ctx) throws Exception { 
> System.out.println("init()"); }
> public void cancel(ServiceContext ctx) { 
> System.out.println("cancel()"); }
> }
> }
> {code}
> Output:
> {noformat}
> [16:27:01]__   
> [16:27:01]   /  _/ 

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2122:
-

My concerns:
1) Users are not supposed to use concrete types when using "ReadCollection()" 
method. Concrete types are expected only with factories.
2) ToList() produces garbage. At the very least it is a collection and 
enumerator. Plus copying.
3) What about having the following interface. No casts, no copying:
{code}
T ReadCollection factory) where T : ICollection;
{code}

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




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

[jira] [Assigned] (IGNITE-2155) CacheStarSchemaExample isn't clear and it seems the output is wrong

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov reassigned IGNITE-2155:


Assignee: Alexey Kuznetsov  (was: Ilya Suntsov)

Alexey, please fix problem with negative ids in 
ScalarSnowflakeSchemaExample.scala

> CacheStarSchemaExample isn't clear and it seems the output is wrong
> ---
>
> Key: IGNITE-2155
> URL: https://issues.apache.org/jira/browse/IGNITE-2155
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Alexey Kuznetsov
> Fix For: 1.5
>
>
> I run 
> {{org.apache.ignite.examples.datagrid.starschema.CacheStarSchemaExample}} and 
> can't understand what actually it does and what the ouptut means (e.g. why 
> all Ids are negative numbers)?
> {noformat}
> All purchases made at store1:
> FactPurchase [id=-1604674364, productId=-1604674374, storeId=-1604674395, 
> purchasePrice=10.0]
> FactPurchase [id=-1604674362, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=12.0]
> FactPurchase [id=-1604674349, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=25.0]
> FactPurchase [id=-1604674346, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=28.0]
> FactPurchase [id=-1604674343, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=31.0]
> FactPurchase [id=-1604674342, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=32.0]
> FactPurchase [id=-1604674337, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=37.0]
> FactPurchase [id=-1604674332, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=42.0]
> FactPurchase [id=-1604674325, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=49.0]
> FactPurchase [id=-1604674323, productId=-1604674391, storeId=-1604674395, 
> purchasePrice=51.0]
> FactPurchase [id=-1604674317, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=57.0]
> FactPurchase [id=-1604674316, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=58.0]
> FactPurchase [id=-1604674311, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=63.0]
> FactPurchase [id=-1604674305, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=69.0]
> FactPurchase [id=-1604674300, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=74.0]
> FactPurchase [id=-1604674296, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=78.0]
> FactPurchase [id=-1604674295, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=79.0]
> FactPurchase [id=-1604674293, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=81.0]
> FactPurchase [id=-1604674289, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=85.0]
> FactPurchase [id=-1604674285, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=89.0]
> FactPurchase [id=-1604674281, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=93.0]
> FactPurchase [id=-1604674371, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=3.0]
> FactPurchase [id=-1604674370, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=4.0]
> FactPurchase [id=-1604674368, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=6.0]
> FactPurchase [id=-1604674363, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=11.0]
> FactPurchase [id=-1604674357, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=17.0]
> FactPurchase [id=-1604674355, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=19.0]
> FactPurchase [id=-1604674353, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=21.0]
> FactPurchase [id=-1604674348, productId=-1604674376, storeId=-1604674395, 
> purchasePrice=26.0]
> FactPurchase [id=-1604674340, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=34.0]
> FactPurchase [id=-1604674339, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=35.0]
> FactPurchase [id=-1604674336, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=38.0]
> FactPurchase [id=-1604674335, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=39.0]
> FactPurchase [id=-1604674333, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=41.0]
> FactPurchase [id=-1604674331, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=43.0]
> FactPurchase [id=-1604674329, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=45.0]
> FactPurchase [id=-1604674327, productId=-1604674391, storeId=-1604674395, 
> purchasePrice=47.0]
> FactPurchase [id=-1604674322, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=52.0]
> FactPurchase 

[jira] [Reopened] (IGNITE-2155) CacheStarSchemaExample isn't clear and it seems the output is wrong

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov reopened IGNITE-2155:
--

> CacheStarSchemaExample isn't clear and it seems the output is wrong
> ---
>
> Key: IGNITE-2155
> URL: https://issues.apache.org/jira/browse/IGNITE-2155
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Alexey Kuznetsov
> Fix For: 1.5
>
>
> I run 
> {{org.apache.ignite.examples.datagrid.starschema.CacheStarSchemaExample}} and 
> can't understand what actually it does and what the ouptut means (e.g. why 
> all Ids are negative numbers)?
> {noformat}
> All purchases made at store1:
> FactPurchase [id=-1604674364, productId=-1604674374, storeId=-1604674395, 
> purchasePrice=10.0]
> FactPurchase [id=-1604674362, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=12.0]
> FactPurchase [id=-1604674349, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=25.0]
> FactPurchase [id=-1604674346, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=28.0]
> FactPurchase [id=-1604674343, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=31.0]
> FactPurchase [id=-1604674342, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=32.0]
> FactPurchase [id=-1604674337, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=37.0]
> FactPurchase [id=-1604674332, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=42.0]
> FactPurchase [id=-1604674325, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=49.0]
> FactPurchase [id=-1604674323, productId=-1604674391, storeId=-1604674395, 
> purchasePrice=51.0]
> FactPurchase [id=-1604674317, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=57.0]
> FactPurchase [id=-1604674316, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=58.0]
> FactPurchase [id=-1604674311, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=63.0]
> FactPurchase [id=-1604674305, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=69.0]
> FactPurchase [id=-1604674300, productId=-1604674382, storeId=-1604674395, 
> purchasePrice=74.0]
> FactPurchase [id=-1604674296, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=78.0]
> FactPurchase [id=-1604674295, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=79.0]
> FactPurchase [id=-1604674293, productId=-1604674377, storeId=-1604674395, 
> purchasePrice=81.0]
> FactPurchase [id=-1604674289, productId=-1604674378, storeId=-1604674395, 
> purchasePrice=85.0]
> FactPurchase [id=-1604674285, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=89.0]
> FactPurchase [id=-1604674281, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=93.0]
> FactPurchase [id=-1604674371, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=3.0]
> FactPurchase [id=-1604674370, productId=-1604674392, storeId=-1604674395, 
> purchasePrice=4.0]
> FactPurchase [id=-1604674368, productId=-1604674389, storeId=-1604674395, 
> purchasePrice=6.0]
> FactPurchase [id=-1604674363, productId=-1604674375, storeId=-1604674395, 
> purchasePrice=11.0]
> FactPurchase [id=-1604674357, productId=-1604674393, storeId=-1604674395, 
> purchasePrice=17.0]
> FactPurchase [id=-1604674355, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=19.0]
> FactPurchase [id=-1604674353, productId=-1604674384, storeId=-1604674395, 
> purchasePrice=21.0]
> FactPurchase [id=-1604674348, productId=-1604674376, storeId=-1604674395, 
> purchasePrice=26.0]
> FactPurchase [id=-1604674340, productId=-1604674383, storeId=-1604674395, 
> purchasePrice=34.0]
> FactPurchase [id=-1604674339, productId=-1604674379, storeId=-1604674395, 
> purchasePrice=35.0]
> FactPurchase [id=-1604674336, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=38.0]
> FactPurchase [id=-1604674335, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=39.0]
> FactPurchase [id=-1604674333, productId=-1604674390, storeId=-1604674395, 
> purchasePrice=41.0]
> FactPurchase [id=-1604674331, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=43.0]
> FactPurchase [id=-1604674329, productId=-1604674388, storeId=-1604674395, 
> purchasePrice=45.0]
> FactPurchase [id=-1604674327, productId=-1604674391, storeId=-1604674395, 
> purchasePrice=47.0]
> FactPurchase [id=-1604674322, productId=-1604674385, storeId=-1604674395, 
> purchasePrice=52.0]
> FactPurchase [id=-1604674321, productId=-1604674380, storeId=-1604674395, 
> purchasePrice=53.0]
> FactPurchase [id=-1604674319, productId=-1604674386, 

[jira] [Assigned] (IGNITE-2123) Need to add EntryProcessorExample to cache examples

[Roman Shtykh (JIRA)]

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

Roman Shtykh reassigned IGNITE-2123:


Assignee: Roman Shtykh

> Need to add EntryProcessorExample to cache examples
> ---
>
> Key: IGNITE-2123
> URL: https://issues.apache.org/jira/browse/IGNITE-2123
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Roman Shtykh
>
> One can take {{CacheAffinityExample}} as an example.
> # call entry processors in a loop, if entry is null then create it in entry 
> processor
> # do gets in a loop and show that entries are in cache
> # call entry processors in a loop and modify existing entries
> # do gets in a loop and show the results of modification



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

[jira] [Updated] (IGNITE-2168) Examples should destroy created caches: SpringBeanExample fails after CacheBinaryAutoStoreExample

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2168:
--
Fix Version/s: (was: 1.5)
   1.6

> Examples should destroy created caches: SpringBeanExample fails after 
> CacheBinaryAutoStoreExample
> -
>
> Key: IGNITE-2168
> URL: https://issues.apache.org/jira/browse/IGNITE-2168
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> 1. Start remote node with examples/config/example-ignite.xml
> 2. Run DbH2ServerStartup
> 3. Run CacheBinaryAutoStoreExample ()
> 4. Run SpringBeanExample and get the following exception: 
> {noformat}
> >>> Spring bean example started.
> log4j:WARN No appenders could be found for logger 
> (org.springframework.core.env.StandardEnvironment).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> [14:22:00]__   
> [14:22:00]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [14:22:00]  _/ // (7 7// /  / / / _/   
> [14:22:00] /___/\___/_/|_/___/ /_/ /___/  
> [14:22:00] 
> [14:22:00] ver. 1.5.0-b2#20151215-sha1:0c550aaa
> [14:22:00] 2015 Copyright(C) Apache Software Foundation
> [14:22:00] 
> [14:22:00] Ignite documentation: http://ignite.apache.org
> [14:22:00] 
> [14:22:00] Quiet mode.
> [14:22:00]   ^-- Logging to file 
> 'C:\Work\apache-ignite-fabric-1.5.0-b2-bin\work\log\ignite-0b6a932b.log'
> [14:22:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [14:22:00] 
> [14:22:00] OS: Windows 7 6.1 amd64
> [14:22:00] VM information: Java(TM) SE Runtime Environment 1.7.0_80-b15 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.80-b11
> [14:22:00] Initial heap size is 254MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [14:22:01] Configured plugins:
> [14:22:01]   ^-- None
> [14:22:01] 
> [14:22:02] Security status [authentication=off, tls/ssl=off]
> [14:22:03,911][ERROR][main][IgniteKernal] Got exception while starting (will 
> rollback startup routine).
> class org.apache.ignite.IgniteException: Failed to load bean in application 
> context [beanName=h2-example-db, 
> igniteConfig=org.springframework.context.support.ClassPathXmlApplicationContext@7a64f150:
>  startup date [Tue Dec 15 14:21:59 MSK 2015]; root of context hierarchy]
>   at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:168)
>   at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:96)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1243)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:774)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:945)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1659)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1518)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:974)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
>   at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
>   at 
> org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1627)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1564)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:540)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
>   at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:302)
>   at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.

[jira] [Updated] (IGNITE-2168) Examples should destroy created caches: SpringBeanExample fails after CacheBinaryAutoStoreExample

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2168:
--
Summary: Examples should destroy created caches: SpringBeanExample fails 
after CacheBinaryAutoStoreExample  (was: SpringBeanExample fails after 
CacheBinaryAutoStoreExample)

> Examples should destroy created caches: SpringBeanExample fails after 
> CacheBinaryAutoStoreExample
> -
>
> Key: IGNITE-2168
> URL: https://issues.apache.org/jira/browse/IGNITE-2168
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> 1. Start remote node with examples/config/example-ignite.xml
> 2. Run DbH2ServerStartup
> 3. Run CacheBinaryAutoStoreExample ()
> 4. Run SpringBeanExample and get the following exception: 
> {noformat}
> >>> Spring bean example started.
> log4j:WARN No appenders could be found for logger 
> (org.springframework.core.env.StandardEnvironment).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> [14:22:00]__   
> [14:22:00]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [14:22:00]  _/ // (7 7// /  / / / _/   
> [14:22:00] /___/\___/_/|_/___/ /_/ /___/  
> [14:22:00] 
> [14:22:00] ver. 1.5.0-b2#20151215-sha1:0c550aaa
> [14:22:00] 2015 Copyright(C) Apache Software Foundation
> [14:22:00] 
> [14:22:00] Ignite documentation: http://ignite.apache.org
> [14:22:00] 
> [14:22:00] Quiet mode.
> [14:22:00]   ^-- Logging to file 
> 'C:\Work\apache-ignite-fabric-1.5.0-b2-bin\work\log\ignite-0b6a932b.log'
> [14:22:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [14:22:00] 
> [14:22:00] OS: Windows 7 6.1 amd64
> [14:22:00] VM information: Java(TM) SE Runtime Environment 1.7.0_80-b15 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.80-b11
> [14:22:00] Initial heap size is 254MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [14:22:01] Configured plugins:
> [14:22:01]   ^-- None
> [14:22:01] 
> [14:22:02] Security status [authentication=off, tls/ssl=off]
> [14:22:03,911][ERROR][main][IgniteKernal] Got exception while starting (will 
> rollback startup routine).
> class org.apache.ignite.IgniteException: Failed to load bean in application 
> context [beanName=h2-example-db, 
> igniteConfig=org.springframework.context.support.ClassPathXmlApplicationContext@7a64f150:
>  startup date [Tue Dec 15 14:21:59 MSK 2015]; root of context hierarchy]
>   at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:168)
>   at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:96)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1243)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:774)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:945)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1659)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1518)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:974)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
>   at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
>   at 
> org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1627)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1564)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:540)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
>   at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:302)
>   at 
> org.springframework.beans.factory.support.

[jira] [Created] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

Michael Griggs created IGNITE-2169:
--

 Summary: Ignite-import-schema tool generates incorrect null schema 
for JDBC
 Key: IGNITE-2169
 URL: https://issues.apache.org/jira/browse/IGNITE-2169
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 1.5
Reporter: Michael Griggs


Given a SQLite database file that contains tables that are not inside a schema, 
i.e.:

{{
sqlite> .schema
CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
aDate datetime, PRIMARY KEY(aType, aCode));
}}

The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
following schema:
{{
type.setDatabaseSchema("null");
}}

When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
performs the following check:
{{
fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
}}

and generates the following {{insQuery}} and {{updQuery}}

{{

INSERT INTO null.INTEREST_LIST(type,code,EAGER_LOAD,SUBSCRIBE_DATE) 
VALUES(?,?,?,?)

UPDATE null.INTEREST_LIST SET EAGER_LOAD=?,SUBSCRIBE_DATE=? WHERE (type=? AND 
code=?)

}}

This is incorrect, and the code generated in CacheConfig.java should be:

{{

type.setDatabaseSchema(null);

}}

i.e., *without* quotes.  Then the {{ F#isEmpty(schema) }} call returns the 
correct value.

Right now, the code generated by ignite-import-schema.sh is not usable without 
finding this problem one's self, and fixing it.  



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

[jira] [Commented] (IGNITE-2164) CPP: Namespace/class descriptions are missing in generated docs.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-2164:
-

Fixed

> CPP: Namespace/class descriptions are missing in generated docs.
> 
>
> Key: IGNITE-2164
> URL: https://issues.apache.org/jira/browse/IGNITE-2164
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Fix For: 1.5
>
>




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

[jira] [Comment Edited] (IGNITE-2164) CPP: Namespace/class descriptions are missing in generated docs.

[Igor Sapego (JIRA)]

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

Igor Sapego edited comment on IGNITE-2164 at 12/15/15 2:15 PM:
---

Fixed. Added file modules/platforms/core/impl/doxygen.h that contains general 
project description and namespaces description.


was (Author: isapego):
Fixed

> CPP: Namespace/class descriptions are missing in generated docs.
> 
>
> Key: IGNITE-2164
> URL: https://issues.apache.org/jira/browse/IGNITE-2164
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Fix For: 1.5
>
>




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

[jira] [Updated] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

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

Michael Griggs updated IGNITE-2169:
---
Description: 
Given a SQLite database file that contains tables that are not inside a schema, 
i.e.:

{code}

sqlite> .schema
CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
aDate datetime, PRIMARY KEY(aType, aCode));

{code}

The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
following schema:
{code}
type.setDatabaseSchema("null");
{code}

When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
performs the following check:
{code}
fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
{code}

and generates the following {{insQuery}} and {{updQuery}}

{code}

INSERT INTO null.INTEREST_LIST(type,code,EAGER_LOAD,SUBSCRIBE_DATE) 
VALUES(?,?,?,?)

UPDATE null.INTEREST_LIST SET EAGER_LOAD=?,SUBSCRIBE_DATE=? WHERE (type=? AND 
code=?)

{code}

This is incorrect, and the code generated in CacheConfig.java should be:

{code}

type.setDatabaseSchema(null);

{code}

i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
correct value.

*Right now, the code generated by ignite-import-schema.sh is not usable without 
finding this problem one's self, and fixing it.*  

  was:
Given a SQLite database file that contains tables that are not inside a schema, 
i.e.:

{{
sqlite> .schema
CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
aDate datetime, PRIMARY KEY(aType, aCode));
}}

The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
following schema:
{{
type.setDatabaseSchema("null");
}}

When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
performs the following check:
{{
fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
}}

and generates the following {{insQuery}} and {{updQuery}}

{{

INSERT INTO null.INTEREST_LIST(type,code,EAGER_LOAD,SUBSCRIBE_DATE) 
VALUES(?,?,?,?)

UPDATE null.INTEREST_LIST SET EAGER_LOAD=?,SUBSCRIBE_DATE=? WHERE (type=? AND 
code=?)

}}

This is incorrect, and the code generated in CacheConfig.java should be:

{{

type.setDatabaseSchema(null);

}}

i.e., *without* quotes.  Then the {{ F#isEmpty(schema) }} call returns the 
correct value.

Right now, the code generated by ignite-import-schema.sh is not usable without 
finding this problem one's self, and fixing it.  


> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INTEREST_LIST(type,code,EAGER_LOAD,SUBSCRIBE_DATE) 
> VALUES(?,?,?,?)
> UPDATE null.INTEREST_LIST SET EAGER_LOAD=?,SUBSCRIBE_DATE=? WHERE (type=? AND 
> code=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Commented] (IGNITE-2146) Service deployment using a cache-accessing-predicate in node filter sometimes causes a deadlock

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-2146:
--

There are two issues:
- service node filter is executed inside tx on system cache which is not safe.
- if cache 'get' is executed while lock is held it can hang if topology 
changes. It is already handled for cache update operations, need do the same 
for 'get'.


> Service deployment using a cache-accessing-predicate in node filter sometimes 
> causes a deadlock
> ---
>
> Key: IGNITE-2146
> URL: https://issues.apache.org/jira/browse/IGNITE-2146
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4, 1.5
> Environment: Mac OS X 10.11
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Ignite 1.4.0 + Ignite-1.5.0-b1
>Reporter: Noam Liran
>Assignee: Semen Boikov
> Fix For: 1.5
>
> Attachments: stacktrace.txt
>
>
> We're deploying a service on a cluster group. The cluster group is filtered 
> using a predicate. The predicate accesses a cache key to determine if it 
> should return true for a node or not.
> If a new node joins the cluster while the predicate is running a deadlock is 
> encountered: cache functions do not return and the node does not finish 
> joining the cluster.
> I've created a sample program to reproduce this on 1.4.0 and also tried to 
> reproduce it on 1.5.0-b1;
> On 1.4.0 the deadlock is usually reproduced, on 1.5.0-b1 it might take a few 
> tries (I'm guessing it's a timing issue.. I tried to improve the odds of 
> reproduction by using a countdown latch).
> Code:
> {code:title=Main.java}
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.cluster.ClusterGroup;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> import java.util.concurrent.CountDownLatch;
> /**
>  * Created by noliran on 08/12/2015.
>  */
> public class Main {
> public static IgniteCache cache1;
> public static CountDownLatch latch = new CountDownLatch(1);
> public static CacheConfiguration CACHE_CONFIG = new 
> CacheConfiguration()
> .setName("testCache")
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
> .setCacheMode(CacheMode.REPLICATED)
> 
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.PRIMARY);
> public static void main(String[] args) throws InterruptedException {
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
> Ignite ignite1 = 
> Ignition.start(igniteConfiguration.setGridName("grid1"));
> System.out.println("Creating cache");
> cache1 = ignite1.getOrCreateCache(CACHE_CONFIG);
> ClusterGroup group = ignite1.cluster().forPredicate(node -> {
> System.out.println("predicate: starting");
> latch.countDown();
> try {
> System.out.println("predicate: before sleep");
> Thread.sleep(10_000);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> System.out.println("predicate: before containsKey");
> boolean b1 = cache1.containsKey(node.id().toString());
> System.out.println("predicate: returning");
> return b1;
> });
> System.out.println("Deploying service with cache-based predicate");
> new Thread(() -> {
> ignite1.services(group).deployNodeSingleton("testService", new 
> TestService());
> }).start();
> System.out.println("Service in deployment.");
> latch.await();
> System.out.println("Starting second Ignite instance..");
> Ignite ignite2 = 
> Ignition.start(igniteConfiguration.setGridName("grid2"));
> System.out.println("Second Ignite instance started successfully!"); 
> // This isn't going to be printed.
> }
> public static class TestService implements Service
> {
> public void execute(ServiceContext ctx) throws Exception { 
> System.out.println("execute()"); }
> public void 

[jira] [Updated] (IGNITE-2168) Examples should destroy created caches: SpringBeanExample fails after CacheBinaryAutoStoreExample

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2168:
--
Assignee: Vladimir Ershov  (was: Yakov Zhdanov)

> Examples should destroy created caches: SpringBeanExample fails after 
> CacheBinaryAutoStoreExample
> -
>
> Key: IGNITE-2168
> URL: https://issues.apache.org/jira/browse/IGNITE-2168
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Vladimir Ershov
> Fix For: 1.6
>
>
> 1. Start remote node with examples/config/example-ignite.xml
> 2. Run DbH2ServerStartup
> 3. Run CacheBinaryAutoStoreExample ()
> 4. Run SpringBeanExample and get the following exception: 
> {noformat}
> >>> Spring bean example started.
> log4j:WARN No appenders could be found for logger 
> (org.springframework.core.env.StandardEnvironment).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> [14:22:00]__   
> [14:22:00]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [14:22:00]  _/ // (7 7// /  / / / _/   
> [14:22:00] /___/\___/_/|_/___/ /_/ /___/  
> [14:22:00] 
> [14:22:00] ver. 1.5.0-b2#20151215-sha1:0c550aaa
> [14:22:00] 2015 Copyright(C) Apache Software Foundation
> [14:22:00] 
> [14:22:00] Ignite documentation: http://ignite.apache.org
> [14:22:00] 
> [14:22:00] Quiet mode.
> [14:22:00]   ^-- Logging to file 
> 'C:\Work\apache-ignite-fabric-1.5.0-b2-bin\work\log\ignite-0b6a932b.log'
> [14:22:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [14:22:00] 
> [14:22:00] OS: Windows 7 6.1 amd64
> [14:22:00] VM information: Java(TM) SE Runtime Environment 1.7.0_80-b15 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.80-b11
> [14:22:00] Initial heap size is 254MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [14:22:01] Configured plugins:
> [14:22:01]   ^-- None
> [14:22:01] 
> [14:22:02] Security status [authentication=off, tls/ssl=off]
> [14:22:03,911][ERROR][main][IgniteKernal] Got exception while starting (will 
> rollback startup routine).
> class org.apache.ignite.IgniteException: Failed to load bean in application 
> context [beanName=h2-example-db, 
> igniteConfig=org.springframework.context.support.ClassPathXmlApplicationContext@7a64f150:
>  startup date [Tue Dec 15 14:21:59 MSK 2015]; root of context hierarchy]
>   at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:168)
>   at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:96)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1243)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:774)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:945)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1659)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1518)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:974)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
>   at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
>   at 
> org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1627)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1564)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:540)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
>   at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:302)
>   at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:229)
>   at 
> org.springframework.beans.factory.sup

[jira] [Commented] (IGNITE-2159) Platforms examples couldn't be executed under 32-bit OS

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-2159:
-

Vladimir,
We are using Visual Studio 2010 toolchain so we should look at this page 
instead: https://msdn.microsoft.com/en-us/library/26td21ds(v=vs.100).aspx
As you can see, 64-bit versions of atomic increment and decrement functions are 
not available in our case.

Also, I have added specific pragmas to be sure that intrinsics and not a 
functions are used.

> Platforms examples couldn't be executed under 32-bit OS
> ---
>
> Key: IGNITE-2159
> URL: https://issues.apache.org/jira/browse/IGNITE-2159
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
> Environment: Win XP 32-bits, MS VS 2010, MS SDK 7.0, Apache Ignite 
> 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ignite_cpp_x86.png
>
>
> -
> DESCRIPTION
> -
> Platforms examples couldn't be executed under 32-bit OS
> -
> STEPS FOR REPRODUCE
> -
> # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite_x86.sln
> # Open and build 
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln (select 
> proper platform  -  x86)
> # Run the solution
> -
> ACTUAL RESULT
> -
> Follow error appears: "The procedure entry point InterlockedCompareExchange64 
> could not be located in the dynamic link library KERNEL32.dll". Look at the 
> attached picture
> -
> EXPECTED RESULT
> -
> Example should be executed
> -
> ADDITIONAL INFO
> -
> # Also reproducible for .Net examples
> # Wasn't reproducible for the same configuration about 4 month ago (near of 
> the Apache Ignite 1.3.3-rc1)



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

[jira] [Updated] (IGNITE-2165) CPP: Tableau displays textual data in wrong locale.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2165:

Description: By some reason Tableau displays strings in wrong locale when 
using our ODBC driver.  (was: By some reason Tableu displays strings in wrong 
locale when using our ODBC driver.)

> CPP: Tableau displays textual data in wrong locale.
> ---
>
> Key: IGNITE-2165
> URL: https://issues.apache.org/jira/browse/IGNITE-2165
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
> Attachments: screenshot-1.png
>
>
> By some reason Tableau displays strings in wrong locale when using our ODBC 
> driver.



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

[jira] [Updated] (IGNITE-2165) CPP: Tableau displays textual data in wrong locale.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2165:

Summary: CPP: Tableau displays textual data in wrong locale.  (was: CPP: 
Tableu displays textual data in wrong locale.)

> CPP: Tableau displays textual data in wrong locale.
> ---
>
> Key: IGNITE-2165
> URL: https://issues.apache.org/jira/browse/IGNITE-2165
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
> Attachments: screenshot-1.png
>
>
> By some reason Tableu displays strings in wrong locale when using our ODBC 
> driver.



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

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

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov updated IGNITE-2175:
-
Description: 
Steps for reproduce:
1. Start one node form IDEA and one more from terminal
2. Run StreamVisitorExample.
Exception:
{noformat}
16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
update job.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
at 
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
... 13 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:274)
at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1443)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:116)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:145)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:132)
at 
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1748)
at 

[jira] [Commented] (IGNITE-2146) Service deployment using a cache-accessing-predicate in node filter sometimes causes a deadlock

[Noam Liran (JIRA)]

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

Noam Liran commented on IGNITE-2146:


Hi Semyon, 
Glad to help! I think we might be hitting the second issue from time to time in 
our cluster.. sometimes when nodes join/leave the topology, a deadlock that 
involves some cache operations occurs. We haven't been able to pinpoint the 
issue but this might be it.
We're looking forward to see this fixed in 1.5 as we already have some pending 
issues that 1.5 will solve :)
Best Regards
Noam

> Service deployment using a cache-accessing-predicate in node filter sometimes 
> causes a deadlock
> ---
>
> Key: IGNITE-2146
> URL: https://issues.apache.org/jira/browse/IGNITE-2146
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4, 1.5
> Environment: Mac OS X 10.11
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Ignite 1.4.0 + Ignite-1.5.0-b1
>Reporter: Noam Liran
>Assignee: Semen Boikov
> Fix For: 1.5
>
> Attachments: stacktrace.txt
>
>
> We're deploying a service on a cluster group. The cluster group is filtered 
> using a predicate. The predicate accesses a cache key to determine if it 
> should return true for a node or not.
> If a new node joins the cluster while the predicate is running a deadlock is 
> encountered: cache functions do not return and the node does not finish 
> joining the cluster.
> I've created a sample program to reproduce this on 1.4.0 and also tried to 
> reproduce it on 1.5.0-b1;
> On 1.4.0 the deadlock is usually reproduced, on 1.5.0-b1 it might take a few 
> tries (I'm guessing it's a timing issue.. I tried to improve the odds of 
> reproduction by using a countdown latch).
> Code:
> {code:title=Main.java}
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.cluster.ClusterGroup;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> import java.util.concurrent.CountDownLatch;
> /**
>  * Created by noliran on 08/12/2015.
>  */
> public class Main {
> public static IgniteCache cache1;
> public static CountDownLatch latch = new CountDownLatch(1);
> public static CacheConfiguration CACHE_CONFIG = new 
> CacheConfiguration()
> .setName("testCache")
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
> .setCacheMode(CacheMode.REPLICATED)
> 
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.PRIMARY);
> public static void main(String[] args) throws InterruptedException {
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
> Ignite ignite1 = 
> Ignition.start(igniteConfiguration.setGridName("grid1"));
> System.out.println("Creating cache");
> cache1 = ignite1.getOrCreateCache(CACHE_CONFIG);
> ClusterGroup group = ignite1.cluster().forPredicate(node -> {
> System.out.println("predicate: starting");
> latch.countDown();
> try {
> System.out.println("predicate: before sleep");
> Thread.sleep(10_000);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> System.out.println("predicate: before containsKey");
> boolean b1 = cache1.containsKey(node.id().toString());
> System.out.println("predicate: returning");
> return b1;
> });
> System.out.println("Deploying service with cache-based predicate");
> new Thread(() -> {
> ignite1.services(group).deployNodeSingleton("testService", new 
> TestService());
> }).start();
> System.out.println("Service in deployment.");
> latch.await();
> System.out.println("Starting second Ignite instance..");
> Ignite ignite2 = 
> Ignition.start(igniteConfiguration.setGridName("grid2"));
> System.out.println("Second Ignite instance started successfully!"); 
> // This isn't going to be printed.
> }
> public static class TestService implements Service
> 

[jira] [Commented] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

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

Michael Griggs commented on IGNITE-2169:


src/modules/schema-import/src/main/java/org/apache/ignite/schema/generator/CodeGenerator.java
 line 609 requires a conditional check for null:

{code}
add2(src, "jdbcType.setDatabaseSchema(pojo. \"" + pojo.schema() + "\");");
{code}

> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INTEREST_LIST(type,code,EAGER_LOAD,SUBSCRIBE_DATE) 
> VALUES(?,?,?,?)
> UPDATE null.INTEREST_LIST SET EAGER_LOAD=?,SUBSCRIBE_DATE=? WHERE (type=? AND 
> code=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Updated] (IGNITE-2169) Ignite-import-schema tool generates incorrect null schema for JDBC

[Michael Griggs (JIRA)]

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

Michael Griggs updated IGNITE-2169:
---
Description: 
Given a SQLite database file that contains tables that are not inside a schema, 
i.e.:

{code}

sqlite> .schema
CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
aDate datetime, PRIMARY KEY(aType, aCode));

{code}

The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
following schema:
{code}
type.setDatabaseSchema("null");
{code}

When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
performs the following check:
{code}
fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
{code}

and generates the following {{insQuery}} and {{updQuery}}

{code}

INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)

UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)

{code}

This is incorrect, and the code generated in CacheConfig.java should be:

{code}

type.setDatabaseSchema(null);

{code}

i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
correct value.

*Right now, the code generated by ignite-import-schema.sh is not usable without 
finding this problem one's self, and fixing it.*  

  was:
Given a SQLite database file that contains tables that are not inside a schema, 
i.e.:

{code}

sqlite> .schema
CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
aDate datetime, PRIMARY KEY(aType, aCode));

{code}

The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
following schema:
{code}
type.setDatabaseSchema("null");
{code}

When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
performs the following check:
{code}
fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
{code}

and generates the following {{insQuery}} and {{updQuery}}

{code}

INSERT INTO null.INTEREST_LIST(type,code,EAGER_LOAD,SUBSCRIBE_DATE) 
VALUES(?,?,?,?)

UPDATE null.INTEREST_LIST SET EAGER_LOAD=?,SUBSCRIBE_DATE=? WHERE (type=? AND 
code=?)

{code}

This is incorrect, and the code generated in CacheConfig.java should be:

{code}

type.setDatabaseSchema(null);

{code}

i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
correct value.

*Right now, the code generated by ignite-import-schema.sh is not usable without 
finding this problem one's self, and fixing it.*  


> Ignite-import-schema tool generates incorrect null schema for JDBC
> --
>
> Key: IGNITE-2169
> URL: https://issues.apache.org/jira/browse/IGNITE-2169
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Michael Griggs
>
> Given a SQLite database file that contains tables that are not inside a 
> schema, i.e.:
> {code}
> sqlite> .schema
> CREATE TABLE INFO_LIST(aType varchar(64), aCode varchar(128), aInt INTEGER, 
> aDate datetime, PRIMARY KEY(aType, aCode));
> {code}
> The ignite-import-schema.sh tool generates a {{CacheConfig.java}} with the 
> following schema:
> {code}
> type.setDatabaseSchema("null");
> {code}
> When the {{CacheAbstractJdbcStore#EntryMapping}} class is instantiated, it 
> performs the following check:
> {code}
> fullTblName = F.isEmpty(schema) ? tblName : schema + "." + tblName;
> {code}
> and generates the following {{insQuery}} and {{updQuery}}
> {code}
> INSERT INTO null.INFO_LIST(aType,aCode,aInt,aDate) VALUES(?,?,?,?)
> UPDATE null.INFO_LIST SET aInt=?,aDate=? WHERE (aType=? AND aCode=?)
> {code}
> This is incorrect, and the code generated in CacheConfig.java should be:
> {code}
> type.setDatabaseSchema(null);
> {code}
> i.e., *without* quotes.  Then the {{F#isEmpty(schema)}} call returns the 
> correct value.
> *Right now, the code generated by ignite-import-schema.sh is not usable 
> without finding this problem one's self, and fixing it.*  



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

[jira] [Updated] (IGNITE-2157) CacheClientBinaryPutGetExample javadoc should be updated

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-2157:
---
Description: 
Javadoc for CacheClientBinaryPutGetExample is obsoleted. It contains:
{noformat}
* 
* Remote nodes should always be started with special configuration file which
 * enables the binary marshaller: {@code 'ignite.{sh|bat} 
examples/config/binary/example-ignite-binary.xml'}.
 * 
{noformat}

Instead:
{noformat}
* 
* Remote nodes should always be started with the following command:
* {@code 'ignite.{sh|bat} examples/config/example-ignite.xml'}.
* 
{noformat}
Please, fix it.

  was:
Javadoc for CacheClientBinaryPutGetExample is obsoleted. It contains:
{noformat}
* 
* Remote nodes should always be started with special configuration file which
 * enables the binary marshaller: {@code 'ignite.{sh|bat} 
examples/config/binary/example-ignite-binary.xml'}.
 * 
{noformat}

Instead:
* 
* Remote nodes should always be started with the following command:
* {@code 'ignite.{sh|bat} examples/config/example-ignite.xml'}.
* 
Please, fix it.


> CacheClientBinaryPutGetExample javadoc should be updated
> 
>
> Key: IGNITE-2157
> URL: https://issues.apache.org/jira/browse/IGNITE-2157
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.5
> Environment: Apache Ignite 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
>Assignee: Vasilisa  Sidorova
>Priority: Trivial
> Fix For: 1.5
>
>
> Javadoc for CacheClientBinaryPutGetExample is obsoleted. It contains:
> {noformat}
> * 
> * Remote nodes should always be started with special configuration file which
>  * enables the binary marshaller: {@code 'ignite.{sh|bat} 
> examples/config/binary/example-ignite-binary.xml'}.
>  * 
> {noformat}
> Instead:
> {noformat}
> * 
> * Remote nodes should always be started with the following command:
> * {@code 'ignite.{sh|bat} examples/config/example-ignite.xml'}.
> * 
> {noformat}
> Please, fix it.



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

[jira] [Closed] (IGNITE-2157) CacheClientBinaryPutGetExample javadoc should be updated

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova closed IGNITE-2157.
--
Assignee: (was: Vasilisa  Sidorova)

Fix verified for Apache Ignite 1.5.0-b2 build #110

> CacheClientBinaryPutGetExample javadoc should be updated
> 
>
> Key: IGNITE-2157
> URL: https://issues.apache.org/jira/browse/IGNITE-2157
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.5
> Environment: Apache Ignite 1.5.0-b2 build #105
>Reporter: Vasilisa  Sidorova
>Priority: Trivial
> Fix For: 1.5
>
>
> Javadoc for CacheClientBinaryPutGetExample is obsoleted. It contains:
> {noformat}
> * 
> * Remote nodes should always be started with special configuration file which
>  * enables the binary marshaller: {@code 'ignite.{sh|bat} 
> examples/config/binary/example-ignite-binary.xml'}.
>  * 
> {noformat}
> Instead:
> {noformat}
> * 
> * Remote nodes should always be started with the following command:
> * {@code 'ignite.{sh|bat} examples/config/example-ignite.xml'}.
> * 
> {noformat}
> Please, fix it.



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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Vishal Garg (JIRA)]

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

Vishal Garg commented on IGNITE-2016:
-

Thanks [~roman_s]

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Created] (IGNITE-2171) ComputeExecutionRejectedException not handled when JobStealingCollisionSpi is used

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-2171:
-

 Summary: ComputeExecutionRejectedException not handled when 
JobStealingCollisionSpi is used
 Key: IGNITE-2171
 URL: https://issues.apache.org/jira/browse/IGNITE-2171
 Project: Ignite
  Issue Type: Task
Reporter: Yakov Zhdanov


http://stackoverflow.com/questions/26583400/gridcomputeexecutionrejectedexception-not-handled-when-gridjobstealingcollisions
(GG-9365)



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

[jira] [Created] (IGNITE-2170) DHT preloader: response to partitions request may be sent bypassing waits for ops to finish

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-2170:
-

 Summary: DHT preloader: response to partitions request may be sent 
bypassing waits for ops to finish
 Key: IGNITE-2170
 URL: https://issues.apache.org/jira/browse/IGNITE-2170
 Project: Ignite
  Issue Type: Task
Reporter: Yakov Zhdanov


When topology changes, new oldest node may request partitions from other nodes. 
Other nodes reply immediately, disregarding locks and ongoing TXs. They should 
reply only after ongoing stuff is finished.
Please check if this is correct.
See 
org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPreloader#processSinglePartitionRequest
We reply directly. It seems that we should go through exchange future and reply 
only when initFut of exch fut is done.

(GG-7284)




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

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

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2175:


 Summary: Not valid exceptions in case when example can't works 
with remote node started with server classpath (Java 7)
 Key: IGNITE-2175
 URL: https://issues.apache.org/jira/browse/IGNITE-2175
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
 Environment: jdk 1.7
OS X 10.10.2
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


Steps for reproduce:
1. Start one node form IDEA and one more from terminal
2. Run StreamVisitorExample.
Got exception:
{noformat}
16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
update job.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
at 
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
... 13 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:274)
at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1443)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:116)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280)
at 

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

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2176:


 Summary: Not valid exceptions in case when example can't works 
with remote node started with server classpath (Java 8)
 Key: IGNITE-2176
 URL: https://issues.apache.org/jira/browse/IGNITE-2176
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
 Environment: jdk 1.7
OS X 10.10.2
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


Steps for reproduce:
1. Start one node from IDEA and one more from terminal
2. Run StreamVisitorExample (Java 8):
Exception:
{noformat}
Exception in thread "pub-#2%null%" class 
org.apache.ignite.binary.BinaryInvalidTypeException: 
org.apache.ignite.examples.java8.streaming.StreamVisitorExample
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.java8.streaming.StreamVisitorExample
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
... 22 more
{noformat}
3. Run StreamTransformerExample (Java 8)
Exception:
{noformat}
Exception in thread "pub-#2%null%" class 
org.apache.ignite.binary.BinaryInvalidTypeException: 
org.apache.ignite.examples.java8.streaming.StreamTransformerExample
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
at 

[jira] [Commented] (IGNITE-2152) .NET: Introduction page is missing.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2152:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2152 .NET: Introduction page is missing.



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

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

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

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


commit 1b2d64d2000282c85fdcad4b8f75601cd96fdbc5
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:46:06Z

IGNITE-2152 .NET: Introduction page is missing.

commit 30657ac100f761a0c77bd26359c921850ca9980d
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:49:21Z

wip

commit f49e7028e79770d780f6f3dc6065ce68acfc1ca2
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:52:19Z

wip




> .NET: Introduction page is missing.
> ---
>
> Key: IGNITE-2152
> URL: https://issues.apache.org/jira/browse/IGNITE-2152
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 1.5
>
>




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

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

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko edited comment on IGNITE-2087 at 12/16/15 7:50 AM:
---

We should also set class loader for non-default URI.

This can be achieved by passing the loader to {{IgnitionEx}} and setting it to 
{{IgniteConfiguration}} after it's loaded from the XML.

UPD: I think {{IgniteConfiguration.setClassLoader}} should not be called if the 
class loader is already explicitly set.


was (Author: vkulichenko):
We should also set class loader for non-default URI.

This can be achieved by passing the loader to {{IgnitionEx}} and setting it to 
{{IgniteConfiguration}} after it's loaded from the XML.

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



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