[jira] [Resolved] (IGNITE-3796) .NET: Platforms system cache

2016-09-10 Thread Vladimir Ozerov (JIRA) 

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

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

> .NET: Platforms system cache
> 
>
> Key: IGNITE-3796
> URL: https://issues.apache.org/jira/browse/IGNITE-3796
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
>  Labels: .net
> Fix For: 1.8
>
>
> Create a new system cache (similar to ignite-sys-cache and others) for 
> platforms.
> The need for such cache emerged in two tickets: IGNITE-1915, IGNITE-2703
> * Cache (and listener) should be started even if there is no platform
> * Different purpose keys should be clearly separated (different class)



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

[jira] [Closed] (IGNITE-3796) .NET: Platforms system cache

2016-09-10 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-3796.
---

> .NET: Platforms system cache
> 
>
> Key: IGNITE-3796
> URL: https://issues.apache.org/jira/browse/IGNITE-3796
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
>  Labels: .net
> Fix For: 1.8
>
>
> Create a new system cache (similar to ignite-sys-cache and others) for 
> platforms.
> The need for such cache emerged in two tickets: IGNITE-1915, IGNITE-2703
> * Cache (and listener) should be started even if there is no platform
> * Different purpose keys should be clearly separated (different class)



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

[jira] [Reopened] (IGNITE-3796) .NET: Platforms system cache

2016-09-10 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov reopened IGNITE-3796:
-

> .NET: Platforms system cache
> 
>
> Key: IGNITE-3796
> URL: https://issues.apache.org/jira/browse/IGNITE-3796
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
>  Labels: .net
> Fix For: 1.8
>
>
> Create a new system cache (similar to ignite-sys-cache and others) for 
> platforms.
> The need for such cache emerged in two tickets: IGNITE-1915, IGNITE-2703
> * Cache (and listener) should be started even if there is no platform
> * Different purpose keys should be clearly separated (different class)



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

[jira] [Commented] (IGNITE-3796) .NET: Platforms system cache

2016-09-10 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov commented on IGNITE-3796:
-

I performed several private discussions with Pavel Tupitsyn, Alexey Goncharuk 
and Semen Boikov. Summary:
1) Adding new cache doesn't seem to be a good idea for several purposes:
- It increases start time and memory footprint
- Marshaller metadata handling is tough thing as it easily lead to various 
deadlock. For this reason current Java marshaller cache has separate thread 
pool.
2) There is alternative solution - use custom discovery events. However, this 
mechanism appears to be pretty complex to implement, and it can break 
compatibility.
3) Instead of introducing a new cache, we decided to re-use existing marshaller 
cache. This appears to be the most sensible solution for now.

Closing this ticket as "Won't Fix".

> .NET: Platforms system cache
> 
>
> Key: IGNITE-3796
> URL: https://issues.apache.org/jira/browse/IGNITE-3796
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
>  Labels: .net
> Fix For: 1.8
>
>
> Create a new system cache (similar to ignite-sys-cache and others) for 
> platforms.
> The need for such cache emerged in two tickets: IGNITE-1915, IGNITE-2703
> * Cache (and listener) should be started even if there is no platform
> * Different purpose keys should be clearly separated (different class)



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

[jira] [Commented] (IGNITE-3812) Add executors configuration validation.

2016-09-10 Thread Andrew Mashenkov (JIRA) 

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

Andrew Mashenkov commented on IGNITE-3812:
--

{noformat}
final IgniteConfiguration cfg = new IgniteConfiguration();

cfg.setLocalHost("127.0.0.1");
cfg.setManagementThreadPoolSize(-1);

Ignition.start(cfg);
{noformat}
The code above results in IllegalArgumentException:
{noformat}
java.lang.IllegalArgumentException
at 
java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
at 
java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
at 
org.apache.ignite.thread.IgniteThreadPoolExecutor.(IgniteThreadPoolExecutor.java:185)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1672)
{noformat}

> Add executors configuration validation.
> ---
>
> Key: IGNITE-3812
> URL: https://issues.apache.org/jira/browse/IGNITE-3812
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.6
>Reporter: Andrew Mashenkov
>
> An IllegalArgumentException will be thrown from one of java standard 
> implementation of ThreadPool without any information about wrong parameter  
> if incorrect value provided (e.g. if set  threadPoolSize <= 0). So, it is not 
> obvious which executor service initialization has failed.
> See IgnitionEx.IgniteNamedInstance class.



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

[jira] [Comment Edited] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.

2016-09-10 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov edited comment on IGNITE-3376 at 9/10/16 2:42 PM:
---

I join the fixes of {{open}} and {{create}}/{{append}} into one patch because 
it is hard to test input and output separately.

[Tests 
results|http://149.202.210.143:8111/project.html?projectId=IgniteTests_IgniteTests=pull%2F1054%2Fhead]


was (Author: tledkov-gridgain):
I join the fixes of {{open}} and {{create}}/{{append}} into one patch because 
it is hard to test input and output separately.

> IGFS: Allow direct PROXY mode invocations.
> --
>
> Key: IGNITE-3376
> URL: https://issues.apache.org/jira/browse/IGNITE-3376
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
>  Labels: roadmap
>
> Currently we do not have special handling for PROXY mode. So we will either 
> hit AssertionError during dev, or will go to incorrect code path in 
> productions systems.
> We need to fix that - PROXY mode should be handled correctly.



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

[jira] [Comment Edited] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.

2016-09-10 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov edited comment on IGNITE-3376 at 9/10/16 2:42 PM:
---

I join the fixes of {{open}} and {{create}}/{{append}} into one patch because 
it is hard to test input and output separately.


was (Author: tledkov-gridgain):
I join the fixes of {{open}} and {{create}}/{{append}} into one patch because 
it is hard to test input and output separately.

> IGFS: Allow direct PROXY mode invocations.
> --
>
> Key: IGNITE-3376
> URL: https://issues.apache.org/jira/browse/IGNITE-3376
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
>  Labels: roadmap
>
> Currently we do not have special handling for PROXY mode. So we will either 
> hit AssertionError during dev, or will go to incorrect code path in 
> productions systems.
> We need to fix that - PROXY mode should be handled correctly.



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

[jira] [Commented] (IGNITE-1296) Add to local node metrics new value - up time

2016-09-10 Thread Andrew Mashenkov (JIRA) 

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

Andrew Mashenkov commented on IGNITE-1296:
--

This ticket seems to be resolved in version 1.6. See 
[IgniteKernal.java|https://github.com/apache/ignite/blob/ignite-1.6/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java]

> Add to local node metrics new value - up time
> -
>
> Key: IGNITE-1296
> URL: https://issues.apache.org/jira/browse/IGNITE-1296
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Priority: Trivial
>
> Currently looking at the node console output I don't understand how many time 
> node already working. So I suggesting to add this info to the (for example) 
> the Node section as 'up time=4d 23h 45m 32sec'.
> {code}
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=79d693a9, name=tester-DC1]
> ^-- H/N/C [hosts=2, nodes=2, CPUs=32]
> ^-- CPU [cur=4.7%, avg=4.84%, GC=0%]
> ^-- Heap [used=23324MB, free=35.94%, comm=29244MB]
> ^-- Public thread pool [active=0, idle=32, qSize=0]
> ^-- System thread pool [active=0, idle=32, qSize=0]
> ^-- Outbound messages queue [size=0]
> {code}



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

[jira] [Comment Edited] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.

2016-09-10 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov edited comment on IGNITE-3376 at 9/10/16 11:58 AM:


I join the fixes of {{open}} and {{create}}/{{append}} into one patch because 
it is hard to test input and output separately.


was (Author: tledkov-gridgain):
I join the fixes of open and create/append into one patch because it is hard to 
test input and output separately.

> IGFS: Allow direct PROXY mode invocations.
> --
>
> Key: IGNITE-3376
> URL: https://issues.apache.org/jira/browse/IGNITE-3376
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
>  Labels: roadmap
>
> Currently we do not have special handling for PROXY mode. So we will either 
> hit AssertionError during dev, or will go to incorrect code path in 
> productions systems.
> We need to fix that - PROXY mode should be handled correctly.



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

[jira] [Commented] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.

2016-09-10 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov commented on IGNITE-3376:
--

I join the fixes of open and create/append into one patch because it is hard to 
test input and output separately.

> IGFS: Allow direct PROXY mode invocations.
> --
>
> Key: IGNITE-3376
> URL: https://issues.apache.org/jira/browse/IGNITE-3376
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
>  Labels: roadmap
>
> Currently we do not have special handling for PROXY mode. So we will either 
> hit AssertionError during dev, or will go to incorrect code path in 
> productions systems.
> We need to fix that - PROXY mode should be handled correctly.



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

[jira] [Commented] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.

2016-09-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-3376:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3376  IGFS: Allow direct PROXY mode invocations.



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

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

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

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


commit 12fd4976f482ebc43831754645e34042c9073b2d
Author: sboikov 
Date:   2016-08-25T09:29:04Z

Fixed GridQueryParsingTest.

commit 12f532986677c30a716f73aeaa7d3587dd701f55
Author: sboikov 
Date:   2016-09-01T14:05:15Z

Merge remote-tracking branch 'remotes/community/ignite-1.6.6' into 
ignite-1.6.7

commit ae7765329fd6f7d50d13183d13626f39c5682334
Author: dkarachentsev 
Date:   2016-09-02T15:01:12Z

IGNITE-2208 - Queries with object arguments doesn't work wth 
BinaryMarshaller.

commit 7a84ab6a9163ca31fbcfcc6d7ff27e06bf9babef
Author: vozerov-gridgain 
Date:   2016-09-02T15:05:16Z

IGNITE-3827: Removed double marshalling of keys in 
DataStreamerImpl.addData(Map) method.

commit 7bb961fd0a2e78334d33b6bc279c4edc323c246a
Author: vozerov-gridgain 
Date:   2016-09-02T15:05:54Z

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

commit e3c4868d6737e5a0f0b90f99666242865add750c
Author: vozerov-gridgain 
Date:   2016-09-02T15:23:09Z

IGNITE-3829: Optimized affinity key field name handling.

commit e9c797fd964727882ad6f40f2a452b17ae7c857e
Author: isapego 
Date:   2016-09-04T13:47:40Z

IGNITE-2946: CPP: Optimized GetNext() method for cursors. This closes #992.

commit c992213274ec5872ef7ce359efa51e26003424ad
Author: isapego 
Date:   2016-09-04T13:49:42Z

IGNITE-3760: ODBC: Added tests for supported SQL92 string functions. This 
closes #1006.

commit d06eaa2344a753e08d1e3cb00e6b4ab83c6a9a01
Author: isapego 
Date:   2016-09-04T13:52:04Z

IGNITE-3801: ODBC: Added tests for OUTER JOIN. This closes #1027.

commit f8ae67456703e63e3afc9bb5c21d81d576d59448
Author: tledkov-gridgain 
Date:   2016-09-04T14:09:08Z

IGNITE-3651 IGFS: Implemented "usedSpaceSize()" operation for local 
secondary file system. This closes #1009.

commit fc2fe7bf1905675258d40932a4ff649156c17488
Author: tledkov-gridgain 
Date:   2016-09-04T14:12:35Z

IGNITE-3646: IGFS: Added test for symlinked mkdirs on local secondary file 
system. This closes #1013.

commit 3aa13f716934a6ccfe49f8bf99ec3b654e263900
Author: vozerov-gridgain 
Date:   2016-09-05T07:19:48Z

IGNITE-3829: Additional fix.

commit a760918757bee71ab28495496f94e9067ef17888
Author: Igor Sapego 
Date:   2016-09-05T07:36:38Z

IGNITE-3750: ODBC: Added tests for date/time types. This closes #1002.

commit d65228e42ec9c84182b8c9c9c8d06a0056d5eed2
Author: Andrey V. Mashenkov 
Date:   2016-09-05T08:20:26Z

IGNITE-2974: ODBC: Added "socketSendBufferSize" and 
"socketReceiveBufferSize" configuration parameters. This closes #994.

commit 40d4b6ac6a71ed541d20018cf7deb2fb9b9bbb9b
Author: vozerov-gridgain 
Date:   2016-09-05T08:35:26Z

IGNITE-3834: Fixed a problem with BinaryMarshaller handles resolution.

commit 42963e6c99e9b282972e6ad67a813a8038cf580f
Author: Alexander Paschenko 
Date:   2016-09-05T11:10:39Z

IGNITE-3817: Fixed binary object re-build with missing schema.

commit df8163f1ad3a390bb8d51b0eb2f378b5b3663025
Author: Andrey V. Mashenkov 
Date:   2016-09-05T11:15:59Z

IGNITE-3743: ODBC: Added procedure call escape sequence support. This 
closes #1008.

commit e3533010b584ba986196f9c7dbc36359aebd829e
Author: Igor Sapego 
Date:   2016-09-05T12:02:07Z

IGNITE-3819: ODBC: Improved error logging. This closes #1024.

commit 008cf64429f40635e396a71f2c0aaf184077ff2b
Author: Andrey V. Mashenkov 
Date:   2016-09-05T12:17:53Z

IGNITE-3741: ODBC: Added character escape support to expression parser. 
This closes #1004.

commit bf9371a3ddb020209a6b031e11282706e19c58cb
Author: vozerov-gridgain 
Date:   2016-09-05T14:05:05Z

IGNITE-3611: IGFS: Slight refactoring to listPaths() and listFiles() 
methods.

commit