[jira] [Comment Edited] (IGNITE-3172) Ignite-Cassandra serializers

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-3172 at 8/31/16 4:25 AM:
---

Igor, as far as I know in maven exists special test-jar for 
testfor dependencies like this. Could you check - will it work 
for you?
Also about *IllegalStateException* my only concern that if anybody already used 
ignite-cassandra module he may has *try{}cacth{}* block for *IgniteException*
and both *IgniteException* and *IllegalStateException* are runtime exceptions 
and compiler will not raise error.
What do you think?


was (Author: kuaw26):
Igor, as far as I know in maven exists special test-jar for 
testfor dependencies like this. Could you check - will it work 
for you?
Also about *IllegalStateException* my only concern that if anybody already used 
ignite-cassandra module he may have *try{}cacth{}* block for *IgniteException*
and both *IgniteException* and *IllegalStateException* are runtime exceptions 
and compiler will not raise error.
What do you think?

> Ignite-Cassandra serializers
> 
>
> Key: IGNITE-3172
> URL: https://issues.apache.org/jira/browse/IGNITE-3172
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Igor Rudyak
>Assignee: Igor Rudyak
>
> Ignite-Cassandra module should contain only "standard" serializer based on 
> Java serialization mechanism. 
> It should be a separate module in Ignite project for all other alternative 
> implementations of serializers (based on Kryo, providing compression, 
> encryption and etc.)



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

[jira] [Commented] (IGNITE-3172) Ignite-Cassandra serializers

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-3172:
--

Igor, as far as I know in maven exists special test-jar for 
testfor dependencies like this. Could you check - will it work 
for you?
Also about *IllegalStateException* my only concern that if anybody already used 
ignite-cassandra module he may have *try{}cacth{}* block for *IgniteException*
and both *IgniteException* and *IllegalStateException* are runtime exceptions 
and compiler will not raise error.
What do you think?

> Ignite-Cassandra serializers
> 
>
> Key: IGNITE-3172
> URL: https://issues.apache.org/jira/browse/IGNITE-3172
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Igor Rudyak
>Assignee: Igor Rudyak
>
> Ignite-Cassandra module should contain only "standard" serializer based on 
> Java serialization mechanism. 
> It should be a separate module in Ignite project for all other alternative 
> implementations of serializers (based on Kryo, providing compression, 
> encryption and etc.)



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

[jira] [Commented] (IGNITE-3314) Implement Serializable in org.apache.ignite.cache.store.cassandra.datasource.DataSource

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-3314:
--

I think you could serialize strings and enums with IgniteUtils and serialize 
other fields with ObjectOutput.writeObject.
Also you need to set 
/** */
private static final long serialVersionUID = 0L;

to DataSource because of  special logic in Ignite optimized marshaller.

Other than that looks good and once you updated PR I will merge to master.

> Implement Serializable in 
> org.apache.ignite.cache.store.cassandra.datasource.DataSource
> ---
>
> Key: IGNITE-3314
> URL: https://issues.apache.org/jira/browse/IGNITE-3314
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Igor Rudyak
>Assignee: Igor Rudyak
>Priority: Minor
> Fix For: 1.8
>
>
> Current implementation of 
> org.apache.ignite.cache.store.cassandra.utils.datasource.DataSource doesn't 
> implement Serializable, thus for distributed Ignite clusters, 
> CassandraCacheStoreFactory could only be setup through Spring XML file, but 
> not from code. 
> New version of 
> org.apache.ignite.cache.store.cassandra.utils.datasource.DataSource should  
> implement Serializable



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

[jira] [Comment Edited] (IGNITE-3314) Implement Serializable in org.apache.ignite.cache.store.cassandra.datasource.DataSource

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-3314 at 8/31/16 4:13 AM:
---

I think you could serialize strings and enums with IgniteUtils and serialize 
other fields with ObjectOutput.writeObject.
Also you need to set 
/** */
private static final long serialVersionUID = 0L;

to DataSource because of  special logic in Ignite optimized marshaller.

Other than that looks good and once you add tests and updated PR I will merge 
to master.


was (Author: kuaw26):
I think you could serialize strings and enums with IgniteUtils and serialize 
other fields with ObjectOutput.writeObject.
Also you need to set 
/** */
private static final long serialVersionUID = 0L;

to DataSource because of  special logic in Ignite optimized marshaller.

Other than that looks good and once you updated PR I will merge to master.

> Implement Serializable in 
> org.apache.ignite.cache.store.cassandra.datasource.DataSource
> ---
>
> Key: IGNITE-3314
> URL: https://issues.apache.org/jira/browse/IGNITE-3314
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Igor Rudyak
>Assignee: Igor Rudyak
>Priority: Minor
> Fix For: 1.8
>
>
> Current implementation of 
> org.apache.ignite.cache.store.cassandra.utils.datasource.DataSource doesn't 
> implement Serializable, thus for distributed Ignite clusters, 
> CassandraCacheStoreFactory could only be setup through Spring XML file, but 
> not from code. 
> New version of 
> org.apache.ignite.cache.store.cassandra.utils.datasource.DataSource should  
> implement Serializable



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

[jira] [Created] (IGNITE-3811) CacheJdbcPojoStore invalid query for merge operation with complex key on SQL Server

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-3811:
--

 Summary: CacheJdbcPojoStore invalid query for merge operation with 
complex key on SQL Server
 Key: IGNITE-3811
 URL: https://issues.apache.org/jira/browse/IGNITE-3811
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Andrey Novikov
Assignee: Andrey Novikov
 Fix For: 1.8






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

[jira] [Commented] (IGNITE-3742) ODBC: Escape sequences: Support OUTER JOIN escape sequence.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3742:


Github user asfgit closed the pull request at:

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


> ODBC: Escape sequences: Support OUTER JOIN escape sequence. 
> 
>
> Key: IGNITE-3742
> URL: https://issues.apache.org/jira/browse/IGNITE-3742
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> See https://msdn.microsoft.com/en-us/library/ms710299(v=vs.85).aspx



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

[jira] [Commented] (IGNITE-3798) ODBC: Escape sequences: Ensure that escape sequences are parsed correctly irrespective of delimiter chars inside literals.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3798:


Github user asfgit closed the pull request at:

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


> ODBC: Escape sequences: Ensure that escape sequences are parsed correctly 
> irrespective of delimiter chars inside literals.
> --
>
> Key: IGNITE-3798
> URL: https://issues.apache.org/jira/browse/IGNITE-3798
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> Example: {noformat} "SELECT * FROM t1 WHERE t1.col1 = '{smth}'; {noformat} 
> Parser should not try literal _'\{smth\}'_ as escape sequence.



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

[jira] [Commented] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3699:


GitHub user amirakhmedov opened a pull request:

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

`IGNITE-3699: CreatedExpiryPolicy doesn't work if entry is loaded from…

… store

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

$ git pull https://github.com/amirakhmedov/ignite IGNITE-3699

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

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


commit 431bdb068604f1809573bb6526fbdfb09af01cdd
Author: Amir Akhmedov 
Date:   2016-08-31T01:37:44Z

IGNITE-3699: CreatedExpiryPolicy doesn't work if entry is loaded from store




> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --
>
> Key: IGNITE-3699
> URL: https://issues.apache.org/jira/browse/IGNITE-3699
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
> Fix For: 1.8
>
> Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be 
> triggered on {{get()}} operation if the entry is loaded from the store. 
> Currently this is not happening.
> Test reproducing the issue is attached.



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

[jira] [Comment Edited] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Yujue Li (JIRA)]

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

Yujue Li edited comment on IGNITE-3727 at 8/31/16 12:58 AM:


Even if there is only one node, I want send and receive to work on different 
threads, because it is very useful for the development environment.
Since the withAsync() method is provided, so no matter how many nodes, the 
implementation of the two models should be different.


was (Author: liyuj):
Even if there is only one node, I want send and receive to work on different 
threads, because it is very useful for the development environment.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Yujue Li (JIRA)]

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

Yujue Li commented on IGNITE-3727:
--

Even if there is only one node, I want send and receive to work on different 
threads, because it is very useful for the development environment.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3633) Throw an exception when binary object without explicitly set hash code is used as a key

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-3633:
-

Alexander, looks good to me. Please ask another contributor to merge your 
changes.

> Throw an exception when binary object without explicitly set hash code is 
> used as a key
> ---
>
> Key: IGNITE-3633
> URL: https://issues.apache.org/jira/browse/IGNITE-3633
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> New binary built keys erroneously get put to cache as having cache code of 0. 
> We want to force user to set hash code explicitly by throwing an exception 
> when they do not do so.
> Proposed solution by Denis Magda:
> http://apache-ignite-developers.2346864.n4.nabble.com/All-BinaryObjects-created-by-BinaryObjectBuilder-stored-at-the-same-partition-by-default-td8042i20.html



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

[jira] [Updated] (IGNITE-3810) FileSwapSpaceSpi can hang when large value is written

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-3810:

Attachment: SwapSpaceTest.java

> FileSwapSpaceSpi can hang when large value is written
> -
>
> Key: IGNITE-3810
> URL: https://issues.apache.org/jira/browse/IGNITE-3810
> Project: Ignite
>  Issue Type: Bug
>  Components: swap
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
> Fix For: 1.8
>
> Attachments: SwapSpaceTest.java
>
>
> Test reproducing the issue is attached.
> Weirdly, the value of size {{1024 * 1024 - 48}} is successfully written, but 
> when it is only one byte bigger, the swap space hangs.



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

[jira] [Created] (IGNITE-3810) FileSwapSpaceSpi can hang when large value is written

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-3810:
---

 Summary: FileSwapSpaceSpi can hang when large value is written
 Key: IGNITE-3810
 URL: https://issues.apache.org/jira/browse/IGNITE-3810
 Project: Ignite
  Issue Type: Bug
  Components: swap
Affects Versions: 1.7
Reporter: Valentin Kulichenko
 Fix For: 1.8


Test reproducing the issue is attached.

Weirdly, the value of size {{1024 * 1024 - 48}} is successfully written, but 
when it is only one byte bigger, the swap space hangs.



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

[jira] [Created] (IGNITE-3809) ArrayIndexOutOfBoundsException in GridUnsafeLru

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-3809:
---

 Summary: ArrayIndexOutOfBoundsException in GridUnsafeLru
 Key: IGNITE-3809
 URL: https://issues.apache.org/jira/browse/IGNITE-3809
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Valentin Kulichenko
 Fix For: 1.8


{{GridUnsafeLru.offer(..)}} method uses atomic integer as a counter. In case of 
integer overflow this method will throw {{ArrayIndexOutOfBoundsException}}.

We should use {{abs}} to avoid this. For example, like this:
{code}
return lrus[U.safeAbs(addIdx.getAndIncrement()) % cnt].offer(part, addr, hash);
{code}



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

[jira] [Commented] (IGNITE-3633) Throw an exception when binary object without explicitly set hash code is used as a key

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-3633:
-

Denis,

Sorry for bugging you, but could you please have a look at my patch? Thanks.

> Throw an exception when binary object without explicitly set hash code is 
> used as a key
> ---
>
> Key: IGNITE-3633
> URL: https://issues.apache.org/jira/browse/IGNITE-3633
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> New binary built keys erroneously get put to cache as having cache code of 0. 
> We want to force user to set hash code explicitly by throwing an exception 
> when they do not do so.
> Proposed solution by Denis Magda:
> http://apache-ignite-developers.2346864.n4.nabble.com/All-BinaryObjects-created-by-BinaryObjectBuilder-stored-at-the-same-partition-by-default-td8042i20.html



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

[jira] [Closed] (IGNITE-2546) Need to introduce transformers to SCAN queries

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-2546.
---

> Need to introduce transformers to SCAN queries
> --
>
> Key: IGNITE-2546
> URL: https://issues.apache.org/jira/browse/IGNITE-2546
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 1.8
>
>
> Need to add new method to {{IgniteCache}} API:
> {code}
> public  QueryCursor query(Query qry, IgniteClosure 
> transformer);
> {code}
> For now this will be supported only for {{ScanQuery}}, for all others we 
> should throw {{UnsupportedOperationException}} with proper message.
> Example and documentation should be also added.



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

[jira] [Commented] (IGNITE-2546) Need to introduce transformers to SCAN queries

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-2546:
-

Merged suggestion with several fixes. Eduard, thanks again!

> Need to introduce transformers to SCAN queries
> --
>
> Key: IGNITE-2546
> URL: https://issues.apache.org/jira/browse/IGNITE-2546
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 1.8
>
>
> Need to add new method to {{IgniteCache}} API:
> {code}
> public  QueryCursor query(Query qry, IgniteClosure 
> transformer);
> {code}
> For now this will be supported only for {{ScanQuery}}, for all others we 
> should throw {{UnsupportedOperationException}} with proper message.
> Example and documentation should be also added.



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

[jira] [Commented] (IGNITE-3808) Missing EntryProcessor invocations with partitions in flight

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3808:


GitHub user pperalta opened a pull request:

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

IGNITE-3808 Reproducer for missing EntryProcessr invocation

This test reproduces 
[IGNITE-3808.](https://issues.apache.org/jira/browse/IGNITE-3808) It is 
intermittent; every 3 or 4 invocations the test will fail with a message like 
this:

```
junit.framework.AssertionFailedError: Unexpected clear bit: 180424
```

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

$ git pull https://github.com/pperalta/ignite ignite-3808

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

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


commit b95454161d1359a222ffd64045b3b03d9317b09b
Author: Patrick Peralta 
Date:   2016-08-30T19:17:37Z

IGNITE-3808 Reproducer for missing EntryProcessr invocation

This test reproduces IGNITE-3808. It is intermittent; every 3 or
4 invocations the test will fail with a message like this:

junit.framework.AssertionFailedError: Unexpected clear bit: 180424




> Missing EntryProcessor invocations with partitions in flight
> 
>
> Key: IGNITE-3808
> URL: https://issues.apache.org/jira/browse/IGNITE-3808
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Patrick Peralta
>Priority: Critical
>
> With {{CacheAtomicityMode.ATOMIC}}, on occasion we see entry processor 
> invocations that go missing when partitions are in flight.
> Reproducer will follow in a PR.



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

[jira] [Created] (IGNITE-3808) Missing EntryProcessor invocations with partitions in flight

[Patrick Peralta (JIRA)]

Patrick Peralta created IGNITE-3808:
---

 Summary: Missing EntryProcessor invocations with partitions in 
flight
 Key: IGNITE-3808
 URL: https://issues.apache.org/jira/browse/IGNITE-3808
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Patrick Peralta
Priority: Critical


With {{CacheAtomicityMode.ATOMIC}}, on occasion we see entry processor 
invocations that go missing when partitions are in flight.

Reproducer will follow in a PR.



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

[jira] [Created] (IGNITE-3807) IgniteSpiContext registers message listeners incorrectly

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-3807:
---

 Summary: IgniteSpiContext registers message listeners incorrectly
 Key: IGNITE-3807
 URL: https://issues.apache.org/jira/browse/IGNITE-3807
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.7
Reporter: Valentin Kulichenko
 Fix For: 1.8


{{IgniteSpiContext}} implementation provided by {{GridManagerAdapter}} uses 
{{ctx.io().addMessageListener(..)}} method to register message listeners. This 
is incorrect, because this creates a listener for internal Ignite messages, not 
for user messages. Thus, when user tries to send a message on this topic, the 
listener is not invoked. To fix this, {{ctx.io().addUserMessageListener(..)}} 
method should be used instead.



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

[jira] [Commented] (IGNITE-3651) IGFS: Local secondary: Implement "usedSpaceSize()" operation.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3651:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3651 IGFS: Local secondary: Implement "usedSpaceSize()" operation.



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

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

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

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






> IGFS: Local secondary: Implement "usedSpaceSize()" operation.
> -
>
> Key: IGNITE-3651
> URL: https://issues.apache.org/jira/browse/IGNITE-3651
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>




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

[jira] [Comment Edited] (IGNITE-3628) ODBC: Improve data fetching performance.

[Igor Sapego (JIRA)]

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

Igor Sapego edited comment on IGNITE-3628 at 8/30/16 6:02 PM:
--

Completed benchmark. Got following results:
{noformat}
Default page size  (32),   no network delay: 25893 
operations/second.
Default page size  (32),   2 ms network delay emulation: 5379  
operations/second.
Adjusted page size (1024), no network delay: 28011 
operations/second.
Adjusted page size (1024), 2 ms network delay emulation: 24691 
operations/second.
{noformat}

Now I'm going to set default value to 1024 and add corresponding connection 
argument, so user can adjust it during connection.



was (Author: isapego):
Completed benchmark. Got following results:
{noformat}
Default page size  (32),   no network delay: 25893 
operations/second.
Default page size  (32),   2 ms network delay emulation: 5379  
operations/second.
Adjusted page size (1024), no network delay: 28011 
operations/second.
Adjusted page size (1024), 2 ms network delay emulation: 24691 
operations/second.
{noformat}


> ODBC: Improve data fetching performance.
> 
>
> Key: IGNITE-3628
> URL: https://issues.apache.org/jira/browse/IGNITE-3628
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: important, odbc, performance
> Fix For: 1.8
>
>
> Need to add some kind of benchmark to be able to measure fetching performance 
> of the ODBC driver, then profile it and improve performance where it is 
> possible. Pay attention to the fetching page size.
> Consider adding "Fast first row" feature.
> Consider adding {{FETCH_PAGE_SIZE}} connection argument.



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

[jira] [Commented] (IGNITE-3628) ODBC: Improve data fetching performance.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-3628:
-

Completed benchmark. Got following results:
{noformat}
Default page size  (32),   no network delay: 25893 
operations/second.
Default page size  (32),   2 ms network delay emulation: 5379  
operations/second.
Adjusted page size (1024), no network delay: 28011 
operations/second.
Adjusted page size (1024), 2 ms network delay emulation: 24691 
operations/second.
{noformat}


> ODBC: Improve data fetching performance.
> 
>
> Key: IGNITE-3628
> URL: https://issues.apache.org/jira/browse/IGNITE-3628
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: important, odbc, performance
> Fix For: 1.8
>
>
> Need to add some kind of benchmark to be able to measure fetching performance 
> of the ODBC driver, then profile it and improve performance where it is 
> possible. Pay attention to the fetching page size.
> Consider adding "Fast first row" feature.
> Consider adding {{FETCH_PAGE_SIZE}} connection argument.



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

[jira] [Updated] (IGNITE-3806) Node hangs on invocation of .clear() method of Ignite queue.

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov updated IGNITE-3806:
--
Description: 
Steps for reproduction:
1) Start tow node from example.
2) All works fine until none of the nodes are leaved topology.
3) Node hangs on .clear() of listen.

Look at the thread for details
http://apache-ignite-users.70518.x6.nabble.com/Clearing-a-distributed-queue-hangs-after-taking-down-one-node-td7353.html

  was:
Steps for reproduction:
1) Start tow node from example.
2) All works fine until none of the nodes are leaved topology.
3) Node hangs on .clear() of listen.


> Node hangs on invocation of .clear() method of Ignite queue.
> 
>
> Key: IGNITE-3806
> URL: https://issues.apache.org/jira/browse/IGNITE-3806
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vladislav Pyatkov
> Attachments: ServerNode.java
>
>
> Steps for reproduction:
> 1) Start tow node from example.
> 2) All works fine until none of the nodes are leaved topology.
> 3) Node hangs on .clear() of listen.
> Look at the thread for details
> http://apache-ignite-users.70518.x6.nabble.com/Clearing-a-distributed-queue-hangs-after-taking-down-one-node-td7353.html



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

[jira] [Updated] (IGNITE-3806) Node hangs on invocation of .clear() method of Ignite queue.

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov updated IGNITE-3806:
--
Attachment: ServerNode.java

> Node hangs on invocation of .clear() method of Ignite queue.
> 
>
> Key: IGNITE-3806
> URL: https://issues.apache.org/jira/browse/IGNITE-3806
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vladislav Pyatkov
> Attachments: ServerNode.java
>
>
> Steps for reproduction:
> 1) Start tow node from example.
> 2) All works fine until none of the nodes are leaved topology.
> 3) Node hangs on .clear() of listen.



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

[jira] [Created] (IGNITE-3806) Node hangs on invocation of .clear() method of Ignite queue.

[Vladislav Pyatkov (JIRA)]

Vladislav Pyatkov created IGNITE-3806:
-

 Summary: Node hangs on invocation of .clear() method of Ignite 
queue.
 Key: IGNITE-3806
 URL: https://issues.apache.org/jira/browse/IGNITE-3806
 Project: Ignite
  Issue Type: Bug
Reporter: Vladislav Pyatkov


Steps for reproduction:
1) Start tow node from example.
2) All works fine until none of the nodes are leaved topology.
3) Node hangs on .clear() of listen.



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

[jira] [Assigned] (IGNITE-1099) Need to cleanup git

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-1099:


Assignee: Alexey Kuznetsov  (was: Artem Shutak)

> Need to cleanup git
> ---
>
> Key: IGNITE-1099
> URL: https://issues.apache.org/jira/browse/IGNITE-1099
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Alexey Kuznetsov
> Fix For: 1.8
>
>
> * Need to resurrect tool (formerly named JiraBranchesToHtml) that shows up 
> branches for closed tickets in JIRA
> * Need to go through the branches and determine what branches are useless:
> ** ignite-sprint-*
> ** branches with no activity for recent months



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

[jira] [Updated] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-3727:
---
Assignee: Semen Boikov  (was: Dmitriy Govorukhin)

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin commented on IGNITE-3727:


First of all, if you want use msg.remoteListen(...) listener, you need more 
that one node, when you do 
Ignition.start() you create only one node. Now you have one node and one 
listener on this local node, when send message we notify local listener, in the 
same thread that send() method invoke, and then remote nodes. I think you 
problem because you try to send and receive message in one node and one thread. 
If you want you can add System.out.println(Thread.currentThread().getName()); 
to cycle and listener, and you see that it the same thread. This may not be 
obvious.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Updated] (IGNITE-3743) ODBC: Escape sequences: Support procedure call escape sequence.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-3743:
-
Description: 
https://msdn.microsoft.com/en-us/library/ms710248(v=vs.85).aspx


> ODBC: Escape sequences: Support procedure call escape sequence. 
> 
>
> Key: IGNITE-3743
> URL: https://issues.apache.org/jira/browse/IGNITE-3743
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> https://msdn.microsoft.com/en-us/library/ms710248(v=vs.85).aspx



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

[jira] [Commented] (IGNITE-3743) ODBC: Escape sequences: Support procedure call escape sequence.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3743:


GitHub user AMashenkov opened a pull request:

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

IGNITE-3743 ODBC: Escape sequences: Support procedure call escape sequence. 



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

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

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

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


commit 54e432e9bb6927351ea45d85b94965925a8351c7
Author: sboikov 
Date:   2016-05-23T18:08:14Z

ignite-2899 Fixed issues with 'keepBinary' handling, added test.
(cherry picked from commit e47440d)

commit c8269da30a1d55f06531857c52d254268056e84e
Author: sboikov 
Date:   2016-05-24T08:14:03Z

ignite-2620: Need override 'unswap' for detached entry.
(cherry picked from commit f7b376b)

commit e1ec0dedab0221b53dd11f2854c8c88b2641d147
Author: sboikov 
Date:   2016-05-24T11:31:43Z

IGNITE-2865 Continuous query event passed to filter should be immutable for 
users. This closes #744.
(cherry picked from commit 046657b)

commit 727afc87dce6c26756b56620c2aaccc3a3d0117e
Author: Vladislav Pyatkov 
Date:   2016-05-25T05:29:00Z

IGNITE-2667: Allow to start caches in PRIVATE and ISOLATED deployment modes 
when BinaryMarshaller is used

commit 183620cd31095dcd92471927cccf8741e3b63ed7
Author: nikolay_tikhonov 
Date:   2016-05-25T06:47:14Z

IGNITE-3168 Added idle timeout property.

commit 30aa287b881d4f9dc3fd5eec9840eab8d9a20828
Author: sboikov 
Date:   2016-05-24T13:57:20Z

ignite-2620 Skip empty entries in GridCacheMapEntry.onTtlExpired
(cherry picked from commit 6fc274a)

commit e2db87bb1b6c71d7978af17e9f2005ba1c661ab4
Author: sboikov 
Date:   2016-05-25T07:06:43Z

Added trace logging for entry/offheap updates.
(cherry picked from commit 9b2767f)

commit 6fcc7a41d8676956983792717483318b85781479
Author: MaBiao 
Date:   2016-05-25T09:54:40Z

IGNITE-2538 - IgniteRDD count() and isEmpty() method use IgniteCache API

commit e274d44a37fd1269e7a3a5fe1ee6139fd0b0
Author: Denis Magda 
Date:   2016-05-26T11:57:52Z

IGNITE-3188: Binary marshaller doesn't unmarshal a void type (added tests)

commit 6687e2bfb9627ce08c1c258527e2927606a500ed
Author: Yakov Zhdanov 
Date:   2016-05-13T08:48:00Z

review IGNITE-2708 Need to validate that SPIs are started only once
(cherry picked from commit cd063da)

commit 40a41fc50bdb73d50e2aa13da8203784be98e38a
Author: Yakov Zhdanov 
Date:   2016-05-13T08:59:02Z

reverting review IGNITE-2708 Need to validate that SPIs are started only 
once
(cherry picked from commit bf561e1)

commit d05786d8bfc8177223b6db9a98bd3c8170b6bcf1
Author: Ryan Zhao 
Date:   2016-05-13T09:00:43Z

review IGNITE-2708 Need to validate that SPIs are started only once (commit 
with proper author)
(cherry picked from commit 98338ff)

commit 9d937ca34775f39b46568eb3fca4585ce00a0fb1
Author: Yakov Zhdanov 
Date:   2016-05-13T09:54:01Z

review IGNITE-2708 Need to validate that SPIs are started only once (added 
logic to protect properly started grids)
(cherry picked from commit b8d624a)

commit edc2947d7340cac4a3c90fa726c23d5d47798ab9
Author: vozerov-gridgain 
Date:   2016-05-25T10:07:03Z

IGNITE-3191: IGFS: Improved error logging for operations in dual mode.

commit 2f1747d726da87b67f6c5323b3e64762d56398cb
Author: vozerov-gridgain 
Date:   2016-05-27T11:40:17Z

Merge remote-tracking branch 'upstream/gridgain-7.6.1' into gridgain-7.6.1

commit 1bb8b647264593034659b7db929c2664dec603e1
Author: sboikov 
Date:   2016-05-27T11:21:01Z

ignite-3116 Fixed NodeStoppingException in GridDhtGetFuture.
(cherry picked from commit 303d3ca)

commit 47c575c8696d51b675a16aa260ec9d398e0a68e9
Author: nikolay_tikhonov 
Date:   2016-05-30T09:42:37Z

Added benchmark property file.

commit 00e2dda9a850f74178ee893a3acf74ddc30d4a13
Author: nikolay_tikhonov 
Date:   2016-05-30T11:45:38Z

Updated benchmark property file.

commit a28e16e24adb0a03df959830517db84d2505c481
Author: Vladislav Pyatkov 
Date:   2016-05-31T07:01:46Z

IGNITE-3190: OffHeap cache metrics doesn't work properly for OFFHEAP_TIRED 

[jira] [Commented] (IGNITE-2629) ODBC: Added GridNioAsyncNotifyFilter and GridConnectionBytesVerifyFilter to NIO server.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-2629:
--

OdbcThreadPool is instantiating before OdbcProcessor in IgnitionEx class with 
other thread-pools. So, thread pool size parameters should be validate in their 
use place, outside OdbcProcessor class.

Also, I've found that there is no checks of any pool size at all. An 
IllegalArgumentException will be thrown from one of java standard 
implementation of ThreadPool without any information about wrong parameter if 
incorrect value provided. 

We need to validate threadPoolSize parameter for all thread pools to prevent 
user confusion. 

> ODBC: Added GridNioAsyncNotifyFilter and GridConnectionBytesVerifyFilter to 
> NIO server.
> ---
>
> Key: IGNITE-2629
> URL: https://issues.apache.org/jira/browse/IGNITE-2629
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> This is low-priority task, lets return to it once everything else is finished.
> Justification:
> 1) *GridNioAsyncNotifyFilter* moves requests processing to separate thread 
> pool. If you do no do that, all NIO workers might stuck in potentially 
> long-running query operations and you will not be able to accept new client 
> requests what may result in timeouts on client side.
> 2) *GridConnectionBytesVerifyFilter* expects special magic header to ensure 
> connected client identity.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Yujue Li (JIRA)]

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

Yujue Li commented on IGNITE-3727:
--

According to my understanding,in async mode，after send message to the 
queue，send() method should be returned immediately, should not be blocked.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Created] (IGNITE-3805) ODBC: Add support for SQL92 TRANSLATE function.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-3805:
---

 Summary: ODBC: Add support for SQL92 TRANSLATE function.
 Key: IGNITE-3805
 URL: https://issues.apache.org/jira/browse/IGNITE-3805
 Project: Ignite
  Issue Type: Task
  Components: odbc
Affects Versions: 1.7
Reporter: Igor Sapego
Priority: Minor
 Fix For: 1.8


H2 does not currently provides support for the SQL92 {{TRANSLATE}} function - 
{{TRANSLATE(expr USING transcoding_name)}}. {{TRANSLATE}} alters the character 
set of a string value from one base character set to another. For example, 
{{TRANSLATE}} might be used to translate a value from the English character set 
to a Kanji (Japanese) or Cyrillic (Russian) character set. 

Corresponding ODBC flag is {{SQL_SSF_TRANSLATE}} in 
{{SQL_SQL92_STRING_FUNCTIONS}}.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin commented on IGNITE-3727:


msg.send() just add msg to queue, after that another thread send this message 
to cluster nodes.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin commented on IGNITE-3727:


Ok, i understand your problem. Method send() is blocking method, you can find 
which method support async mode by annotation (@IgniteAsyncSupported), for 
example,method remoteListen(...); mark as @IgniteAsyncSupported but send(...) 
is not. 

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-2946) CPP: Method GetNext() of the cursor classes should be optimized.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-2946:
-

Vladimir,

1. Good catch. I believe, .NET changes have been lost during re-merge.
2. Well, it's either that or manual new/delete, as we can not use auto pointers 
in exported class. Maybe we should add our own implementation of auto pointers. 
Changed for manual new/delete for now.
3. If we do that this way this is going to invalidate all {{QueryFieldsRow}}s, 
which is breaking backward compatibility.
4. I prefer it in a separate class as it more clean to me. If we put it into 
{{QueryImpl}} itself then we would need to re-create stream and reader every 
time we get a new memory chunk, which is 2 memory allocations instead of 1. But 
I agree with the performance concerns. I've changed shared pointers to plain 
references. This seem to be ok as the lifetime of batches is <= lifetime of the 
cursors.

{quote}
Ideally there should be no heap allocations at all after we constructed a 
QueryImpl instance. The only exclusion to this rule is memory chunk, which 
should be allocated 1 time on first batch access.
{quote}

As I said, this is going to break backward compatibility. In this case every 
{{GetNext}} call on cursor may invalidate all existing query rows. If we are 
fine with that then I can do that.

> CPP: Method GetNext() of the cursor classes should be optimized.
> 
>
> Key: IGNITE-2946
> URL: https://issues.apache.org/jira/browse/IGNITE-2946
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp, performance
> Fix For: 1.8
>
>
> Current implementation of the GetNext() method of the cursor classes is too 
> slow and should be optimized.



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

[jira] [Assigned] (IGNITE-3651) IGFS: Local secondary: Implement "usedSpaceSize()" operation.

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-3651:


Assignee: Taras Ledkov

> IGFS: Local secondary: Implement "usedSpaceSize()" operation.
> -
>
> Key: IGNITE-3651
> URL: https://issues.apache.org/jira/browse/IGNITE-3651
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>




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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Yujue Li (JIRA)]

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

Yujue Li commented on IGNITE-3727:
--

package msg_async_test;

import java.util.UUID;

import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteMessaging;
import org.apache.ignite.Ignition;
import org.apache.ignite.lang.IgniteBiPredicate;

public class IgniteMsgAsyncTest {

public static void main(String[] args) {
// TODO Auto-generated method stub

try(Ignite ignite = Ignition.start()){
IgniteMessaging msg = ignite.message().withAsync();

msg.remoteListen("Topic", new IgniteBiPredicate() {
@Override public boolean apply(UUID nodeId, String 
msg) {
try {

Thread.currentThread().sleep(2000);
} catch (InterruptedException e) {
// TODO Auto-generated catch 
block
e.printStackTrace();
}
System.out.println("Received message [msg=" + 
msg + ", from=" + nodeId + ']');
return true; // Return true to continue 
listening.
}
});

for (int i = 0; i < 5; i++){
msg.send("Topic", Integer.toString(i));
System.out.println("MSG:" + i);
}
}   
}
}

this small program work in sync mode.
after msg.send() method executed,current thread is blocked.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3750) ODBC: Scalar functions: Support time/date functions.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-3750:
-

Vladimir, ticket is already added. You can find it in related tickets.

> ODBC: Scalar functions: Support time/date functions.
> 
>
> Key: IGNITE-3750
> URL: https://issues.apache.org/jira/browse/IGNITE-3750
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Fix For: 1.8
>
>
> 1) All the functions from the list must be supported: 
> https://msdn.microsoft.com/en-us/library/ms714639(v=vs.85).aspx
> 2) Separate test for every function must be added.
> 3) If some of them cannot be supported immediately, then JIRA ticket must be 
> created and linked to this ticket.



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

[jira] [Created] (IGNITE-3804) ODBC: Add support for SQL92 CONVERT function.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-3804:
---

 Summary: ODBC: Add support for SQL92 CONVERT function.
 Key: IGNITE-3804
 URL: https://issues.apache.org/jira/browse/IGNITE-3804
 Project: Ignite
  Issue Type: Task
  Components: odbc
Affects Versions: 1.7
Reporter: Igor Sapego
Priority: Minor
 Fix For: 1.8


H2 does not currently provides support for the SQL92 {{CONVERT}} function - 
{{CONVERT(expr USING transcoding_name)}}. The {{CONVERT}} function alters the 
representation of a character string within its character set and collation. 
For example, {{CONVERT}} might be used to alter the number of bits per 
character.

Corresponding ODBC flag is {{SQL_SSF_CONVERT}} in 
{{SQL_SQL92_STRING_FUNCTIONS}}.



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

[jira] [Updated] (IGNITE-2946) CPP: Method GetNext() of the cursor classes should be optimized.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2946:

Assignee: Igor Sapego  (was: Vladimir Ozerov)

> CPP: Method GetNext() of the cursor classes should be optimized.
> 
>
> Key: IGNITE-2946
> URL: https://issues.apache.org/jira/browse/IGNITE-2946
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp, performance
> Fix For: 1.8
>
>
> Current implementation of the GetNext() method of the cursor classes is too 
> slow and should be optimized.



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

[jira] [Commented] (IGNITE-2546) Need to introduce transformers to SCAN queries

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-2546:
---

I have made suggest for this page 
https://apacheignite.readme.io/docs/cache-queries.

Can you look through and apply this suggest (if everything is ok?)?

> Need to introduce transformers to SCAN queries
> --
>
> Key: IGNITE-2546
> URL: https://issues.apache.org/jira/browse/IGNITE-2546
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 1.8
>
>
> Need to add new method to {{IgniteCache}} API:
> {code}
> public  QueryCursor query(Query qry, IgniteClosure 
> transformer);
> {code}
> For now this will be supported only for {{ScanQuery}}, for all others we 
> should throw {{UnsupportedOperationException}} with proper message.
> Example and documentation should be also added.



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

[jira] [Assigned] (IGNITE-3646) IGFS: Local secondary: Support symlinks for mkdirs operation.

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-3646:


Assignee: Taras Ledkov

> IGFS: Local secondary: Support symlinks for mkdirs operation.
> -
>
> Key: IGNITE-3646
> URL: https://issues.apache.org/jira/browse/IGNITE-3646
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>




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

[jira] [Commented] (IGNITE-1525) Return value for cache operation can be lost with onePhaseCommit

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-1525:
--

Hi Anton,

I reviewed fix, looks good, but still have few comments:
- could you please add test to check result of cache operations which return 
boolean (e.g. putIfAbsent)
- please change GridDhtTxFinishRequest to pass 'retVal' as part of existing 
'flags' and let's add 'flags' for GridDhtTxPrepareRequest
- please move move DeferredResponseBuffer to some common class to avoid 
copy/paste

Thanks!

> Return value for cache operation can be lost with onePhaseCommit
> 
>
> Key: IGNITE-1525
> URL: https://issues.apache.org/jira/browse/IGNITE-1525
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Semen Boikov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.8
>
>
> Looks like with {{onePhaseCommit}} return value for cache operation can be 
> lost if primary node fails, {{GridNearTxPrepareResponse}} with return value 
> is not received, but transaction executes 'check backup' step and finishes 
> without error.
> Reproduces in {{IgniteCachePutRetryTransactionalSelfTest.testInvoke}}, also 
> added one more test to check return value 
> {{IgniteCachePutRetryTransactionalSelfTest.testGetAndPut}}.
> Please unmute tests on TC when fixed.



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

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

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev commented on IGNITE-2208:
-

Semen, fixed your notes, but there is one more issue.
Enum arguments passed to SQL query are unmarshalled on remote nodes. Removing 
mentioned snipped causes tests to fail and also may produce errors on remote 
node if it doesn't know this enum class.

Unmarshalling happens at 
org/apache/ignite/internal/processors/query/h2/twostep/GridMapQueryExecutor.java:173
{code:title=GridMapQueryExecutor.java:173|borderStyle=solid}
if (msg instanceof GridCacheQueryMarshallable)

((GridCacheQueryMarshallable)msg).unmarshall(ctx.config().getMarshaller(), ctx);
{code}

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



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

[jira] [Created] (IGNITE-3803) Web Console: Do not show sign-in page for user with valid session

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3803:


 Summary: Web Console: Do not show sign-in page for user with valid 
session
 Key: IGNITE-3803
 URL: https://issues.apache.org/jira/browse/IGNITE-3803
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Maxim Afanasiev
Priority: Critical
 Fix For: 1.8


Steps for reproduce:
# Login to web console.
# Close page.
# Open page - you will see "Sign in" page and immediately redirected to 
"Clusters" page.

Expected:
Only "Clusters" page should be shown.



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

[jira] [Closed] (IGNITE-3798) ODBC: Escape sequences: Ensure that escape sequences are parsed correctly irrespective of delimiter chars inside literals.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-3798.
---

> ODBC: Escape sequences: Ensure that escape sequences are parsed correctly 
> irrespective of delimiter chars inside literals.
> --
>
> Key: IGNITE-3798
> URL: https://issues.apache.org/jira/browse/IGNITE-3798
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> Example: {noformat} "SELECT * FROM t1 WHERE t1.col1 = '{smth}'; {noformat} 
> Parser should not try literal _'\{smth\}'_ as escape sequence.



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

[jira] [Updated] (IGNITE-3798) ODBC: Escape sequences: Ensure that escape sequences are parsed correctly irrespective of delimiter chars inside literals.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-3798:
-
Description: 
Example: {noformat} "SELECT * FROM t1 WHERE t1.col1 = '{smth}'; {noformat} 
Parser should not try literal _'\{smth\}'_ as escape sequence.

  was:
Example: {noformat} "SELECT * FROM t1 WHERE t1.col1 = "{smth}"; {noformat} 
Parser should not try literal _"\{smth\}"_ as escape sequence.


> ODBC: Escape sequences: Ensure that escape sequences are parsed correctly 
> irrespective of delimiter chars inside literals.
> --
>
> Key: IGNITE-3798
> URL: https://issues.apache.org/jira/browse/IGNITE-3798
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> Example: {noformat} "SELECT * FROM t1 WHERE t1.col1 = '{smth}'; {noformat} 
> Parser should not try literal _'\{smth\}'_ as escape sequence.



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

[jira] [Comment Edited] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin edited comment on IGNITE-3727 at 8/30/16 9:36 AM:
-

Yujue Li, I found the test GridMessagingSelfTest.testAsync(). Could you please 
describe more details why do you think what method work like sync but not async?


was (Author: dmitriygovorukhin):
Yujue Li, I found the test GridMessagingSelfTest.testAsync(). Could you please 
describe more details why do you think what method work like sync but not asycn?

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Updated] (IGNITE-3802) Web console: we need some how describe limitations for SQL in mode 'become this user'

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-3802:
---
Description: Currently  SQL and Monitoring works incorrect in 'become this 
user' mode, but there is no message about this restriction is showing.  (was: 
Currently we restrict access to SQL in 'become this user' mode, but there is no 
message about this restriction is showing.)

> Web console: we need some how describe limitations for SQL in mode 'become 
> this user'
> -
>
> Key: IGNITE-3802
> URL: https://issues.apache.org/jira/browse/IGNITE-3802
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>
> Currently  SQL and Monitoring works incorrect in 'become this user' mode, but 
> there is no message about this restriction is showing.



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

[jira] [Created] (IGNITE-3802) Web console: we need some how describe limitations for SQL in mode 'become this user'

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3802:
--

 Summary: Web console: we need some how describe limitations for 
SQL in mode 'become this user'
 Key: IGNITE-3802
 URL: https://issues.apache.org/jira/browse/IGNITE-3802
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


Currently we restrict access to SQL in 'become this user' mode, but there is no 
message about this restriction is showing.



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

[jira] [Comment Edited] (IGNITE-3471) Do not send previous value to client node for invoke() when possible

[Andrey Velichko (JIRA)]

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

Andrey Velichko edited comment on IGNITE-3471 at 8/30/16 9:16 AM:
--

Created reproduce test. Inside transaction, for every put operation 
CacheEntryProcessor method process() calls twice on local node, and one time on 
remote node after commit.


was (Author: andreyvel):
Created reproduce test. Inside transaction, for every put operation 
CacheEntryProcessor call method process() twice on local node, and one time on 
remote node after commit.

> Do not send previous value to client node for invoke() when possible
> 
>
> Key: IGNITE-3471
> URL: https://issues.apache.org/jira/browse/IGNITE-3471
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 1.4
>Reporter: Alexey Goncharuk
>Assignee: Andrey Velichko
> Attachments: CacheEntryProcessorTxSelfTest.java
>
>
> Currently for invoke() or invokeAll() methods we send previous cache value to 
> near node and apply EntryProcessor locally to get a return value. This can 
> induce a significant overhead when cache value is much larger than entry 
> processor result.
> For many cases this can be avoided, e.g.
> {code}
> try (tx = txStart()) {
> cache.invoke(key, EP); // No need to send previous value to client in 
> this case.
> tx.commit();
> }
> {code}
> Note that we need to add additional handling of such a case:
> {code}
> try (tx = txStart()) {
> cache.invoke(key, EP); // No need to send previous value to client in 
> this case.
> cache.get(key); // This should actually get the current cache value from 
> primary node and apply an entry processor locally to get the updated value.
> tx.commit();
> }
> {code}



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin commented on IGNITE-3727:


Yujue Li, I found the test GridMessagingSelfTest.testAsync(). Could you please 
describe more details why do you think what method work like sync but not asycn?

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3798) ODBC: Escape sequences: Ensure that escape sequences are parsed correctly irrespective of delimiter chars inside literals.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3798:
-

Andrew,
Probably it makes sense to ignore p.1 for now and fix it in IGNITE-3741.

> ODBC: Escape sequences: Ensure that escape sequences are parsed correctly 
> irrespective of delimiter chars inside literals.
> --
>
> Key: IGNITE-3798
> URL: https://issues.apache.org/jira/browse/IGNITE-3798
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> Example: {noformat} "SELECT * FROM t1 WHERE t1.col1 = "{smth}"; {noformat} 
> Parser should not try literal _"\{smth\}"_ as escape sequence.



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

[jira] [Created] (IGNITE-3801) ODBC: Add test for OUTER JOIN escape sequence and ensure it is marked as supported.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3801:
---

 Summary: ODBC: Add test for OUTER JOIN escape sequence and ensure 
it is marked as supported.
 Key: IGNITE-3801
 URL: https://issues.apache.org/jira/browse/IGNITE-3801
 Project: Ignite
  Issue Type: Task
  Components: odbc
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Assignee: Igor Sapego
Priority: Minor
 Fix For: 1.8


IGNITE-3742 is ready, so that we are able to parse OJ escape sequences in Java. 
We need to add tests for it in ODBC layer and ensure this feature is marked as 
supported.



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

[jira] [Closed] (IGNITE-3742) ODBC: Escape sequences: Support OUTER JOIN escape sequence.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-3742.
---

> ODBC: Escape sequences: Support OUTER JOIN escape sequence. 
> 
>
> Key: IGNITE-3742
> URL: https://issues.apache.org/jira/browse/IGNITE-3742
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> See https://msdn.microsoft.com/en-us/library/ms710299(v=vs.85).aspx



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

[jira] [Comment Edited] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Yujue Li (JIRA)]

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

Yujue Li edited comment on IGNITE-3727 at 8/30/16 8:27 AM:
---

remoteListen work in sync mode,async mode not supported.


was (Author: liyuj):
remoteListen work in sync mode.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Yujue Li (JIRA)]

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

Yujue Li commented on IGNITE-3727:
--

remoteListen work in sync mode.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin commented on IGNITE-3727:


Hi Yujue Li, i will check.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Created] (IGNITE-3800) IGFS: Local secondary: Add tests for local fs properties

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-3800:


 Summary: IGFS: Local secondary: Add tests for local fs properties
 Key: IGNITE-3800
 URL: https://issues.apache.org/jira/browse/IGNITE-3800
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Taras Ledkov
Priority: Minor
 Fix For: 2.0


There are restrictions for check file system entry property on real local file 
system.
- we cannot change owner without native code and root permissions;
- to change the group the group must be pre-configured on the host. 

The base class for Local FS tests 
*IgfsLocalSecondaryFileSystemDualAbstractSelfTest* must read from environment 
the names of pre-configured groups. If the host environment doesn't support 
POSIX fs or cannot provide additional groups for test the flag 
*IGFS_LOCAL_FS_PROPERTIES_SUPPORT* must be set to false.

Build environment must be set names of groups and the flag.



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

[jira] [Assigned] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin reassigned IGNITE-3727:
--

Assignee: Dmitriy Govorukhin

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Commented] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-3727:
--

IgniteMessaging's method remoteListen/stopRemoteListen should support async 
execution, need check if there are corresponding tests.

> ignite.message() method not support async mode,withAsync() is invalid.
> --
>
> Key: IGNITE-3727
> URL: https://issues.apache.org/jira/browse/IGNITE-3727
> Project: Ignite
>  Issue Type: Bug
>  Components: messaging
>Affects Versions: 1.7
> Environment: windows 7
>Reporter: Yujue Li
>Priority: Blocker
> Fix For: 1.8
>
>
> ignite.message() method not support async mode,withAsync() is invalid.



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

[jira] [Assigned] (IGNITE-3645) IGFS: Local secondary: Implement update() operation.

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-3645:


Assignee: Taras Ledkov

> IGFS: Local secondary: Implement update() operation.
> 
>
> Key: IGNITE-3645
> URL: https://issues.apache.org/jira/browse/IGNITE-3645
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>




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

[jira] [Updated] (IGNITE-1837) Rebalancing on a big cluster (30 nodes and more)

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1837:
-
Fix Version/s: (was: 1.8)

> Rebalancing on a big cluster (30 nodes and more)
> 
>
> Key: IGNITE-1837
> URL: https://issues.apache.org/jira/browse/IGNITE-1837
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Semen Boikov
>
> It seems that Ignite has different rebalancing related issues that appear 
> when a big cluster is started.
> Under the big cluster I mean:
> - cluster of 64 server nodes;
> - cluster of 64 server and 64 client nodes.
> The issues can be divided on three main use cases.
> 1) Slow rebalancing on start.
> - If to set partitions number for some cache to value bigger than default one 
> (to 3200 or to 6400, etc.) then rebalancing of such caches may take several 
> minutes. The caches are empty at that time. In addition, as a part of this 
> issue let's document that the number of partitions can't exceed some value.
> - exchange message on NODE_JOINED event that times out for a long time. 
> Discussed there: 
> http://apache-ignite-users.70518.x6.nabble.com/Help-with-tuning-for-larger-clusters-td1692.html#a1813
> 2) Slow rebalancing on client nodes shutdown.
> If to stop a significant number of client nodes at the same time then again 
> by some reason the rebalancing will take serveral minutes.



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

[jira] [Updated] (IGNITE-1183) IgniteAtomicLong closing and getting during rolling restart causes hangs

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1183:
-
Assignee: (was: Semen Boikov)

> IgniteAtomicLong closing and getting during rolling restart causes hangs
> 
>
> Key: IGNITE-1183
> URL: https://issues.apache.org/jira/browse/IGNITE-1183
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
> Attachments: AtomicLongChangingTopologySelfTest.java, log.zip, 
> thread_dump.zip
>
>
> During rolling restart of nodes some threads hang on closing or getting 
> {{IgniteAtomicLong}}.
> Stack trace for thread that hangs on {{IgniteAtomicLong.close()}}:
> {noformat}
> "Test worker" #11 prio=5 os_prio=31 tid=0x7fbbf4ae7800 nid=0x5b03 waiting 
> on condition [0x000122f93000]
> java.lang.Thread.State: WAITING (parking)
>  at sun.misc.Unsafe.park(Native Method)
>  - parking to wait for <0x00076db515a0> (a 
> org.apache.ignite.internal.util.future.GridFutureAdapter$ChainFuture)
>  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
>  at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
>  at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
>  at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4376)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1448)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:288)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$14.call(DataStructuresProcessor.java:1086)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$14.call(DataStructuresProcessor.java:1082)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:939)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeInternal(DataStructuresProcessor.java:1081)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.access$800(DataStructuresProcessor.java:51)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:453)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:448)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:507)
>  at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeAtomicLong(DataStructuresProcessor.java:448)
>  at 
> org.apache.ignite.internal.processors.datastructures.GridCacheAtomicLongImpl.close(GridCacheAtomicLongImpl.java:368)
> {noformat}
> Stack trace for thread that hangs on {{Ignite.atomicLong()}}:
> {noformat}
> "datastructures.AtomicLongChangingTopologySelfTest-1" prio=10 
> tid=0x7f9cd800a800 nid=0x2bb3 waiting on condition [0x7f9c49cfc000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0x0007f106e580> (a 
> org.apache.ignite.internal.util.future.GridEmbeddedFuture)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:964)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1282)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:113)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$24.op(GridCacheAdapter.java:2089)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$24.op(GridCacheAdapter.java:2081)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:3990)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke(GridCacheAdapter.java:2081)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getAtomic(DataStructuresProcessor.java:449)
>   at 
> 

[jira] [Closed] (IGNITE-2560) Support injections in entry processors

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-2560.

Assignee: (was: Semen Boikov)

> Support injections in entry processors
> --
>
> Key: IGNITE-2560
> URL: https://issues.apache.org/jira/browse/IGNITE-2560
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Valentin Kulichenko
> Fix For: 1.8
>
>
> Currently resources are not injected in entry processor, which is not 
> consistent with other functionality, like closures, jobs, listeners, etc.
> To avoid performance degradation we should introspect the class only once, 
> cache this information and do not try to inject if there are no annotations.



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