[jira] [Commented] (IGNITE-2881) SPI queries not working

2016-08-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-2881:


GitHub user AMashenkov opened a pull request:

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

IGNITE-2881 : SPI queries not working

... fixed

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

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

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

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


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 
mode.
Reviewed and merged by Denis Magda (dma...@gridgain.com)
(cherry picked from commit 7533dfc)

commit 56c605622dbecf71f3ee87cc41a16d2ee87e92d3
Author: vozerov-gridgain 
Date:   2016-05-26T08:15:48Z

IGNITE-3200: Resolved classloader leak.

commit a815067a0e8e7cfc9f49c57efe2b2eba562e9071
Author: vozerov-gridgain 
Date:   2016-05-31T07:23:00Z

IGNITE-3202: Hadoop: Implemented user name mappers.

commit 421cf03b03276d0ab6c32ef6665d547746446dfc
Author: vozerov-gridgain 
Date:   2016-05-31T07:40:24Z

7.5.24: Added missing JavaDocs.

commit 167e47781f65c056b9d273eea52d268bc9a8fa0b
Author: Denis Magda 
Date:   2016-05-31T10:50:06Z

IGNITE-2708: fix tests that don't create unique IndexingSPI per node
(cherry picked from commit f90e424)

commit 21bdf3148f05481d86e77e13b282ac44c6c3a059
Author: vozerov-gridgain 
Date:   2016-05-31T10:54:32Z

Added pacajge info for java.org.apache.ignite.hadoop.util package.

commit 3ca9febeb2bf53d17b6dea739938cff40c5fa67d
Author: vozerov-gridgain

[jira] [Commented] (IGNITE-2881) SPI queries not working

2016-08-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-2881:


Github user AMashenkov closed the pull request at:

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


> SPI queries not working
> ---
>
> Key: IGNITE-2881
> URL: https://issues.apache.org/jira/browse/IGNITE-2881
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: SpiQueryTest.java
>
>
> {{SpiQuery}} functionality looks completely broken right now, any query 
> execution fails with the exception shown below. Also I didn't find a single 
> test for it, they should be added.
> I'm attaching the simple example that reproduce the issue.
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Received next page 
> request after iterator was removed. Consider increasing maximum number of 
> stored iterators (see GridCacheConfiguration.getMaximumQueryIteratorCount() 
> configuration property).
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.executeFieldsQuery(GridCacheQueryManager.java:666)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runFieldsQuery(GridCacheQueryManager.java:1168)
>   ... 7 more
> {noformat}



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

[jira] [Commented] (IGNITE-2881) SPI queries not working

2016-08-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-2881:


GitHub user AMashenkov opened a pull request:

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

IGNITE-2881 SPI queries not working

... fixed

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

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

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

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






> SPI queries not working
> ---
>
> Key: IGNITE-2881
> URL: https://issues.apache.org/jira/browse/IGNITE-2881
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: SpiQueryTest.java
>
>
> {{SpiQuery}} functionality looks completely broken right now, any query 
> execution fails with the exception shown below. Also I didn't find a single 
> test for it, they should be added.
> I'm attaching the simple example that reproduce the issue.
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Received next page 
> request after iterator was removed. Consider increasing maximum number of 
> stored iterators (see GridCacheConfiguration.getMaximumQueryIteratorCount() 
> configuration property).
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.executeFieldsQuery(GridCacheQueryManager.java:666)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runFieldsQuery(GridCacheQueryManager.java:1168)
>   ... 7 more
> {noformat}



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

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

2016-08-31 Thread Alexander Paschenko (JIRA) 

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

Alexander Paschenko reassigned IGNITE-3633:
---

Assignee: Alexander Paschenko  (was: Denis Magda)

> 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: Alexander Paschenko
> 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] [Commented] (IGNITE-3628) ODBC: Improve data fetching performance.

2016-08-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-3628:


GitHub user isapego opened a pull request:

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

IGNITE-3628: Added fetch page size to configuration params.



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

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

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

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


commit d23936c0251a376dff964c53e51834793e47468c
Author: isapego 
Date:   2016-08-30T15:26:09Z

IGNITE-3628: Benchmark stub.

commit e0b4b44710c0661fef0d4c98aeb02b22275afba1
Author: isapego 
Date:   2016-08-30T15:44:28Z

IGNITE-3628: Adjusted benchmark.

commit 73df311b13aaf648c8edfbf41af65fca2dd3c8b6
Author: isapego 
Date:   2016-08-30T16:45:46Z

IGNITE-3628: Benchmark is ready.

commit 6c75f03b41ae7a587f1039322407147642f8996a
Author: isapego 
Date:   2016-08-30T17:25:04Z

IGNITE-3628: Improved benchmark.

commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit e960c00574127b489ee6acc3b53b7f468c71aff6
Author: isapego 
Date:   2016-08-31T09:57:26Z

IGNITE-3628: Changed default page size to 1024.

commit 70e69cb7aa08c268b07920838add4a40e28fe25d
Author: isapego 
Date:   2016-08-31T13:47:11Z

IGNITE-3390: Added DSN configuration window.

commit 727edc57bd26f2cdda32f50ea873230402b902df
Author: isapego 
Date:   2016-08-31T14:15:35Z

Merge branch 'ignite-1.6.7' into ignite-3628

commit 72a37710ae3f8ac6fdbfc87bd98f656ac7fc6ea4
Author: isapego 
Date:   2016-08-31T15:30:37Z

IGNITE-3628: Added fetch page size to configuration params.

commit a2961f5fe56a36b996cc54fdb5d46a9cfab61e7c
Author: isapego 
Date:   2016-08-31T16:37:40Z

IGNITE-3628: Added Fetch page size param to configuration dialog.

commit 442dfc2e283da9af43534005076ad97d16b6ad90
Author: isapego 
Date:   2016-08-31T16:50:55Z

IGNITE-3628: Added tests.




> 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] [Created] (IGNITE-3814) Unstable results of compute benchmarks

2016-08-31 Thread Ilya Suntsov (JIRA) 
Ilya Suntsov created IGNITE-3814:


 Summary: Unstable results of compute benchmarks
 Key: IGNITE-3814
 URL: https://issues.apache.org/jira/browse/IGNITE-3814
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
 Environment: Ubuntu 14.04
jdk 1.7, jdk 1.8
Reporter: Ilya Suntsov


I've run the following compute benchmarks:
* exec-compute
* run-compute
* broad-compute
* apply-compute
and got huge difference between the best and worst results e.g. for 
exec-compute we have the following numbers:
1   1222.38
2   1220.63
3   1044.53
4   1342.39
5   1393.57
5   1064.66

delta between 3-rd and 4-th runs is 28%.
I think we should re-work these benchmarks.



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

2016-08-31 Thread Alexey Goncharuk (JIRA) 

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

Alexey Goncharuk commented on IGNITE-3633:
--

Alexander,

Looks like the hashCodeSet flag is lost when we create a new 
BinaryObjectBuilder from another BinaryObject. Otherwise looks good. Please fix 
this (and add a test) and I will merge this PR.

> 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-3727) ignite.message() method not support async mode,withAsync() is invalid.

2016-08-31 Thread Semen Boikov (JIRA) 

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

Semen Boikov updated IGNITE-3727:
-
Priority: Major  (was: Blocker)

> 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
> 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-2539) NPE at RendezvousAffinityFunction

2016-08-31 Thread Dmitriy Govorukhin (JIRA) 

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

Dmitriy Govorukhin reassigned IGNITE-2539:
--

Assignee: Dmitriy Govorukhin  (was: Alexey Goncharuk)

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



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

[jira] [Assigned] (IGNITE-613) [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails

2016-08-31 Thread Dmitriy Govorukhin (JIRA) 

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

Dmitriy Govorukhin reassigned IGNITE-613:
-

Assignee: Dmitriy Govorukhin  (was: Sergi Vladykin)

> [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails
> --
>
> Key: IGNITE-613
> URL: https://issues.apache.org/jira/browse/IGNITE-613
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Artem Shutak
>Assignee: Dmitriy Govorukhin
>Priority: Critical
>  Labels: Muted_test
> Attachments: ignite-613.patch
>
>
> IgniteCacheReplicatedQuerySelfTest #testNodeLeft  test fails by unknown 
> reason (should be unmuted on TC after fix). 
> Test works long and fails after. Should be enabled after fix.



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

[jira] [Commented] (IGNITE-3390) ODBC: Add system DSN support for Windows.

2016-08-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-3390:


Github user isapego closed the pull request at:

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


> ODBC: Add system DSN support for Windows.
> -
>
> Key: IGNITE-3390
> URL: https://issues.apache.org/jira/browse/IGNITE-3390
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
> Attachments: dsn_configuration_window.png, 
> dsn_configuration_window_reworked.png, dsn_configuration_window_v3.png, 
> dsn_configuration_window_v4.png
>
>
> Need to add support for the DSN creation/modification in Windows. To do so we 
> will need to create some UI windows with matching fields.
> DSN stands for the Data Source Name, and it is actually list of options for 
> the ODBC driver which can be used to establish connection. In our case it is 
> set of the host name, tcp port and cache name to which connection should be 
> established. In Windows it seems to be common practice to use "ODBC Data 
> Source Administrator" system tool to configure DNS for the ODBC driver. "ODBC 
> Data Source Administrator" it it's turn uses GUI windows to get DSN 
> information from the user. So to support this feature, we'd needed to 
> implement GUI window that would allow our users to configure their own DSNs.



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

[jira] [Resolved] (IGNITE-1110) REST API: create/delete cache

2016-08-31 Thread Sergey Kozlov (JIRA) 

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

Sergey Kozlov resolved IGNITE-1110.
---
Resolution: Fixed

> REST API: create/delete cache
> -
>
> Key: IGNITE-1110
> URL: https://issues.apache.org/jira/browse/IGNITE-1110
> Project: Ignite
>  Issue Type: Task
>Affects Versions: sprint-8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Minor
>
> Apache Ignite supports dynamic caches so REST API could be extended by 
> following commands:
>  - get or create cache (start cache)
>  - destroy cache (stop cache)



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

[jira] [Closed] (IGNITE-1110) REST API: create/delete cache

2016-08-31 Thread Sergey Kozlov (JIRA) 

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

Sergey Kozlov closed IGNITE-1110.
-

> REST API: create/delete cache
> -
>
> Key: IGNITE-1110
> URL: https://issues.apache.org/jira/browse/IGNITE-1110
> Project: Ignite
>  Issue Type: Task
>Affects Versions: sprint-8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Minor
>
> Apache Ignite supports dynamic caches so REST API could be extended by 
> following commands:
>  - get or create cache (start cache)
>  - destroy cache (stop cache)



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

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

2016-08-31 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov edited comment on IGNITE-3646 at 8/31/16 1:13 PM:
---

Symbolic link was supported by development. The test 
{{IgfsLocalSecondaryFileSystemDualAbstractSelfTest.testMkdirsInsideSymlink}} is 
added to be ensure the feature is completed.

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


was (Author: tledkov-gridgain):
Symbolic link was supported by development. The test 
{{IgfsLocalSecondaryFileSystemDualAbstractSelfTest.testMkdirsInsideSymlink}} is 
added to be ensure the feature is completed.

> 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-3646) IGFS: Local secondary: Support symlinks for mkdirs operation.

2016-08-31 Thread Taras Ledkov (JIRA) 

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

Taras Ledkov commented on IGNITE-3646:
--

Symbolic link was supported by development. The test 
{{IgfsLocalSecondaryFileSystemDualAbstractSelfTest.testMkdirsInsideSymlink}} is 
added to be ensure the feature is completed.

> 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-3646) IGFS: Local secondary: Support symlinks for mkdirs operation.

2016-08-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-3646:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation.



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

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

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

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


commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit 684f7af64169912959d1545990c736433494fa32
Author: tledkov-gridgain 
Date:   2016-08-31T13:09:17Z

IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation.




> 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] [Updated] (IGNITE-3813) High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys

2016-08-31 Thread Dmitry Karachentsev (JIRA) 

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

Dmitry Karachentsev updated IGNITE-3813:

Attachment: jstack.log

> High contention on GridCacheMapEntry.obsolete() on loading data to data 
> stremer with composite keys
> ---
>
> Key: IGNITE-3813
> URL: https://issues.apache.org/jira/browse/IGNITE-3813
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.7
>Reporter: Dmitry Karachentsev
> Fix For: 1.8
>
> Attachments: jstack.log
>
>
> On loading entries with non-primitive key to data streamer too many calls to 
> metadata cache which causes high contention on GridCacheMapEntry.
> Example thread dump in attachment.



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

[jira] [Created] (IGNITE-3813) High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys

2016-08-31 Thread Dmitry Karachentsev (JIRA) 
Dmitry Karachentsev created IGNITE-3813:
---

 Summary: High contention on GridCacheMapEntry.obsolete() on 
loading data to data stremer with composite keys
 Key: IGNITE-3813
 URL: https://issues.apache.org/jira/browse/IGNITE-3813
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.7
Reporter: Dmitry Karachentsev
 Fix For: 1.8


On loading entries with non-primitive key to data streamer too many calls to 
metadata cache which causes high contention on GridCacheMapEntry.

Example thread dump in attachment.



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

[jira] [Commented] (IGNITE-3390) ODBC: Add system DSN support for Windows.

2016-08-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-3390:


GitHub user isapego opened a pull request:

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

IGNITE-3390: Added DSN configuration window.



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

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

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

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


commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit 5477d3c1e342adda9fc03bc6b4d8811885ae4664
Author: isapego 
Date:   2016-08-31T12:23:59Z

IGNITE-3390: Added DSN configuration window.




> ODBC: Add system DSN support for Windows.
> -
>
> Key: IGNITE-3390
> URL: https://issues.apache.org/jira/browse/IGNITE-3390
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
> Attachments: dsn_configuration_window.png, 
> dsn_configuration_window_reworked.png, dsn_configuration_window_v3.png, 
> dsn_configuration_window_v4.png
>
>
> Need to add support for the DSN creation/modification in Windows. To do so we 
> will need to create some UI windows with matching fields.
> DSN stands for the Data Source Name, and it is actually list of options for 
> the ODBC driver which can be used to establish connection. In our case it is 
> set of the host name, tcp port and cache name to which connection should be 
> established. In Windows it seems to be common practice to use "ODBC Data 
> Source Administrator" system tool to configure DNS for the ODBC driver. "ODBC 
> Data Source Administrator" it it's turn uses GUI windows to get DSN 
> information from the user. So to support this feature, we'd needed to 
> implement GUI window that would allow our users to configure their own DSNs.



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

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

2016-08-31 Thread Amir Akhmedov (JIRA) 

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

Amir Akhmedov reassigned IGNITE-3699:
-

Assignee: Valentin Kulichenko  (was: Amir Akhmedov)

> 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: Valentin Kulichenko
> 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] [Commented] (IGNITE-3474) Grid hung during load test with warning "Failed to wait for partition map exchange"

2016-08-31 Thread Ilya Suntsov (JIRA) 

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

Ilya Suntsov commented on IGNITE-3474:
--

I reproduced this issue on ignite-1.7.0

> Grid hung during load test with warning "Failed to wait for partition map 
> exchange"
> ---
>
> Key: IGNITE-3474
> URL: https://issues.apache.org/jira/browse/IGNITE-3474
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Assignee: Semen Boikov
>Priority: Critical
> Attachments: 091826_id0_192.168.1.21_part.log, 
> ignite-base-load-config.xml, run-load.properties, run-load.xml
>
>
> During atomic operations load test grid hung:
> {noformat}
> [09:22:17,688][WARN 
> ][exchange-worker-#137%null%][GridCachePartitionExchangeManager] Failed to 
> wait for partition map exchange [topVer=AffinityTopologyVersion [topVer=97, 
> minorTopVer=0], node=0fe0c0f2-65e1-4ad5-a8c9-92db997fcb7d]. Dumpin
> g pending objects that might be the cause:
> ...
> {noformat}
> See attached file with more info from logs.
> Notes:
> 1) The issue was also reproduced with IGNITE-3239 fixed. So, IGNITE-3239 
> doesn't seem to be a root cause. 
> 2) The issue was also reproduced with other configs (not only atomic 
> operations). Actually, most of laod tests failed due to this issue.
> Load test config:
> - Benchmark name: IgniteCacheRandomOperationBenchmark
> - Operations: put, put_all, get, get_all, invoke, invoke_all, remove, 
> remove_all, put_if_absent, replace
> - Heap: 2Gb for servers, 1Gb for clients
> - 48 clients, 48 servers, 6 hosts
> - Preload amount: 2.5M
> - Key range: 5M
> - Number of caches: 12
> - Types of caches (atomicity mode): only atomic
> - Types of caches (tiered storage mode): different (onheap without eviction, 
> onheap with eviction, offheap_tired, offheap_values)
> - Types of caches (indexing): different (with and without indexes)
> - Types of caches (cache mode): partitioned
> - Backups count: 1
> Attachments:
> - part of log with the problem (for one of the servers)
> - xml configs and property file that were used to run yardstick



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

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

2016-08-31 Thread Andrew Mashenkov (JIRA) 

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

Andrew Mashenkov updated IGNITE-3812:
-
Description: 
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.

  was:
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. threadPoolSize <= 0). So, it is not obvious 
which executor service initialization failed.

See IgnitionEx.IgniteNamedInstance class


> 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] [Updated] (IGNITE-3812) Add executors configuration validation.

2016-08-31 Thread Andrew Mashenkov (JIRA) 

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

Andrew Mashenkov updated IGNITE-3812:
-
Affects Version/s: 1.6

> 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. threadPoolSize <= 0). So, it is not obvious 
> which executor service initialization failed.
> See IgnitionEx.IgniteNamedInstance class



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

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

2016-08-31 Thread Andrew Mashenkov (JIRA) 
Andrew Mashenkov created IGNITE-3812:


 Summary: Add executors configuration validation.
 Key: IGNITE-3812
 URL: https://issues.apache.org/jira/browse/IGNITE-3812
 Project: Ignite
  Issue Type: Task
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. threadPoolSize <= 0). So, it is not obvious 
which executor service initialization failed.

See IgnitionEx.IgniteNamedInstance class



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

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

2016-08-31 Thread Andrey Novikov (JIRA) 

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

Andrey Novikov resolved IGNITE-3811.

Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Andrey Novikov)

Fixed query for merge operation.

For test: need put value with same key twice all should work fine.
Note: key must be an object with two or more fields.

> 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: Pavel Konstantinov
> Fix For: 1.8
>
>




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

[jira] [Assigned] (IGNITE-3789) Test for EntryProcessor/partition events

2016-08-31 Thread Semen Boikov (JIRA) 

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

Semen Boikov reassigned IGNITE-3789:


Assignee: Semen Boikov  (was: Patrick Peralta)

> Test for EntryProcessor/partition events
> 
>
> Key: IGNITE-3789
> URL: https://issues.apache.org/jira/browse/IGNITE-3789
> Project: Ignite
>  Issue Type: Test
>  Components: cache
>Affects Versions: 1.7
>Reporter: Patrick Peralta
>Assignee: Semen Boikov
>
> Create a test that validates:
> 1. EntryProcessors execute against partitions that are fully owned/loaded.
> 2. Expected events are raised when partitions are moved due to a change in 
> cluster topology.
> See https://issues.apache.org/jira/browse/IGNITE-3456



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