[jira] [Updated] (IGNITE-2242) CPP: Implement SQLGetData function for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2242:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement SQLGetData function for the ODBC driver.
> ---
>
> Key: IGNITE-2242
> URL: https://issues.apache.org/jira/browse/IGNITE-2242
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This function listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.



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

[jira] [Updated] (IGNITE-2243) CPP: Implement Environment attributes manipulation for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2243:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement Environment attributes manipulation for the ODBC driver.
> ---
>
> Key: IGNITE-2243
> URL: https://issues.apache.org/jira/browse/IGNITE-2243
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetEnvAttr}}
> - {{SQLSetEnvAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ODBC_VER}}



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

[jira] [Updated] (IGNITE-2245) CPP: Implement Statement attributes manipulation for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2245:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement Statement attributes manipulation for the ODBC driver.
> -
>
> Key: IGNITE-2245
> URL: https://issues.apache.org/jira/browse/IGNITE-2245
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetStmtAttr}}
> - {{SQLSetStmtAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_APP_PARAM_DESC}}
> - {{SQL_ATTR_APP_ROW_DESC}}
> - {{SQL_ATTR_IMP_PARAM_DESC}}
> - {{SQL_ATTR_IMP_ROW_DESC}}
> - {{SQL_ATTR_METADATA_ID}}
> - {{SQL_ATTR_NOSCAN}}
> - {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_PARAM_BIND_TYPE}}
> - {{SQL_ATTR_PARAM_OPERATION_PTR}}
> - {{SQL_ATTR_PARAM_STATUS_PTR}}
> - {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
> - {{SQL_ATTR_PARAMSET_SIZE}}
> - {{SQL_ATTR_ROW_ARRAY_SIZE}}
> - {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_ROW_BIND_TYPE}}
> - {{SQL_ATTR_ROW_STATUS_PTR}}
> - {{SQL_ATTR_ROWS_FETCHED_PTR}}



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

[jira] [Updated] (IGNITE-2244) CPP: Implement Connection attributes manipulation for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2244:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement Connection attributes manipulation for the ODBC driver.
> --
>
> Key: IGNITE-2244
> URL: https://issues.apache.org/jira/browse/IGNITE-2244
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetConnectAttr}}
> - {{SQLSetConnectAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ACCESS_MODE}}
> - {{SQL_ATTR_ODBC_CURSORS}}
> - {{SQL_ATTR_QUIET_MODE}}
> - {{SQL_ATTR_TRACE}}
> - {{SQL_ATTR_TRACEFILE}}
> - {{SQL_ATTR_TRANSLATE_LIB}}
> - {{SQL_ATTR_TRANSLATE_OPTION}}



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

[jira] [Comment Edited] (IGNITE-2080) JVM crashes on Solaris (SPARC V9 arch) with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-2080 at 1/14/16 4:02 PM:
--

All problems found during test execution on Solaris SPARC are fixed. Waiting 
for TC results.

Also I create new PR where code rebased on top of {{master}} branch: 
https://github.com/apache/ignite/pull/404


was (Author: agura):
All problem found during test execution on Solaris SPARC are fixed. Waiting for 
TC results.

Also I create new PR where code rebased on top of {{master}} branch: 
https://github.com/apache/ignite/pull/404

> JVM crashes on Solaris (SPARC V9 arch) with SIGBUS (0xa) on frame 
> [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> ---
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> 

[jira] [Commented] (IGNITE-2080) JVM crashes on Solaris (SPARC V9 arch) with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-2080:
-

All problem found during test execution on Solaris SPARC are fixed. Waiting for 
TC results.

Also I create new PR where code rebased on top of {{master}} branch: 
https://github.com/apache/ignite/pull/404

> JVM crashes on Solaris (SPARC V9 arch) with SIGBUS (0xa) on frame 
> [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> ---
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> 

[jira] [Updated] (IGNITE-2248) CPP: Implement obtaining the row-identifying column of tables for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2248:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement obtaining the row-identifying column of tables for the ODBC 
> driver.
> --
>
> Key: IGNITE-2248
> URL: https://issues.apache.org/jira/browse/IGNITE-2248
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.
> This means implementing obtaining the {{SQL_BEST_ROWID}} row-identifying 
> column of tables, by calling {{SQLSpecialColumns}}.



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

[jira] [Updated] (IGNITE-2241) CPP: Implement SQLGetTypeInfo function for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2241:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement SQLGetTypeInfo function for the ODBC driver.
> ---
>
> Key: IGNITE-2241
> URL: https://issues.apache.org/jira/browse/IGNITE-2241
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This function is listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.



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

[jira] [Updated] (IGNITE-2246) CPP: Implement Descriptors support for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2246:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement Descriptors support for the ODBC driver.
> ---
>
> Key: IGNITE-2246
> URL: https://issues.apache.org/jira/browse/IGNITE-2246
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.
> This includes implementation of the following functions:
> - {{SQLCopyDesc}}
> - {{SQLGetDescField}}
> - {{SQLGetDescRec}}
> - {{SQLSetDescField}}
> - {{SQLSetDescRec}}
> Following header fields:
> - {{SQL_DESC_ALLOC_TYPE}}
> - {{SQL_DESC_ARRAY_SIZE}}
> - {{SQL_DESC_ARRAY_STATUS_PTR}}
> - {{SQL_DESC_BIND_OFFSET_PTR}}
> - {{SQL_DESC_BIND_TYPE}}
> - {{SQL_DESC_COUNT}}
> - {{SQL_DESC_ROWS_PROCESSED_PTR}}
> Following record fields:
> - {{SQL_DESC_BASE_COLUMN_NAME}}
> - {{SQL_DESC_CASE_SENSITIVE}}
> - {{SQL_DESC_CONCISE_TYPE}}
> - {{SQL_DESC_DATA_PTR}}
> - {{SQL_DESC_DATETIME_INTERVAL_ CODE}}
> - {{SQL_DESC_DATETIME_INTERVAL_ PRECISION}}
> - {{SQL_DESC_DISPLAY_SIZE}}
> - {{SQL_DESC_FIXED_PREC_SCALE}}
> - {{SQL_DESC_INDICATOR_PTR}}
> - {{SQL_DESC_LENGTH}}
> - {{SQL_DESC_LITERAL_PREFIX}}
> - {{SQL_DESC_LITERAL_SUFFIX}}
> - {{SQL_DESC_LOCAL_TYPE_NAME}}
> - {{SQL_DESC_NAME}}
> - {{SQL_DESC_NULLABLE}}
> - {{SQL_DESC_OCTET_LENGTH}}
> - {{SQL_DESC_OCTET_LENGTH_PTR}}
> - {{SQL_DESC_PARAMETER_TYPE}}
> - {{SQL_DESC_PRECISION}}
> - {{SQL_DESC_SCALE}}
> - {{SQL_DESC_SEARCHABLE}}
> - {{SQL_DESC_TYPE}}
> - {{SQL_DESC_TYPE_NAME}}
> - {{SQL_DESC_UNNAMED}}
> - {{SQL_DESC_UNSIGNED}}
> - {{SQL_DESC_UPDATABLE}}



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

[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-2096:
--
Labels: newbie  (was: )

> AtomicConfiguration and CollectionConfiguration should be properly checked 
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>  Labels: newbie
> Fix For: 1.6
>
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped 
> to system caches configuration and consistency is checked like for any other 
> cache. This leads to unintuitive errors.



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

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-429:
-

Roman, 
That's a regular check for streamers, we should ensure that only corect data 
goes to the cache, easiest way is to check before and after :) 
First check should happened after components created for test but before they 
should start data producing.

> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
> Fix For: 1.6
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-429:
-

Roman,

Looks good, please check "Checklist before push" ( 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepush
 ) and I'll push changes to master.

> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
> Fix For: 1.6
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Resolved] (IGNITE-2370) Validation of cache's data sorces with the same name

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-2370.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Implemented check on save of cache that all contain that cache clusters have 
caches with the same database for data sources with the same data source bean.
Implemented check on save of cluster that all cluster's caches have the same 
database for data sources with the same data source bean.

> Validation of cache's data sorces with the same name
> 
>
> Key: IGNITE-2370
> URL: https://issues.apache.org/jira/browse/IGNITE-2370
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> On save of cache or cluster check that all cache's data sources with the same 
> name configured for same database.



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

[jira] [Created] (IGNITE-2376) .NET: UnmanagedUtils.IgnitionStart return value is never used

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2376:
--

 Summary: .NET: UnmanagedUtils.IgnitionStart return value is never 
used
 Key: IGNITE-2376
 URL: https://issues.apache.org/jira/browse/IGNITE-2376
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


UnmanagedUtils.IgnitionStart is used only once, and return value is not used.
Quick test to make it void resulted in OutOfMemory in tests on TC.
Need to investigate what is going on.



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

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-429:
-

Anton, thanks, I have updated PR. I added a check for cache is empty after the 
streamer is created && before the topology is started.

> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
> Fix For: 1.6
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Commented] (IGNITE-2324) .NET: Code analysis

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2324:


Done. Failure conditions to be enabled on TC after merge.

> .NET: Code analysis
> ---
>
> Key: IGNITE-2324
> URL: https://issues.apache.org/jira/browse/IGNITE-2324
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> * Investigate code analysis tools (FxCop, SonarQube, etc)
> * Set up a step on TeamCity
> * Set up visual studio to check on build
> * Modify code (adjust inspections/suppressions)



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

[jira] [Updated] (IGNITE-2366) May be remove buttons from the bottom of the page (Save, Clone, Remove)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2366:
-
Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

> May be remove buttons from the bottom of the page (Save, Clone, Remove)
> ---
>
> Key: IGNITE-2366
> URL: https://issues.apache.org/jira/browse/IGNITE-2366
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Trivial
> Fix For: 1.6
>
>
> We have the all needed button on the top of the page on floating panel which 
> makes buttons always visible on the screen.



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

[jira] [Created] (IGNITE-2377) Docker image run on Mac OS hangs

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2377:
---

 Summary: Docker image run on Mac OS hangs
 Key: IGNITE-2377
 URL: https://issues.apache.org/jira/browse/IGNITE-2377
 Project: Ignite
  Issue Type: Wish
Affects Versions: ignite-1.4
Reporter: Denis Magda
 Fix For: 1.6


Docker hangs at the point when {{CommandLineRandomNumberGenerator}} is being 
executed. The reason is that the current and previous Docker version has some 
bug that can be overcame if to put {{System.exit(0)}} at the end of 
{{main(...)}} function.

More investigation details and steps to reproduce can be found here:
http://stackoverflow.com/questions/34661934/ignite-running-in-docker-is-general-java-docker-issue

It makes sense to add {{System.exit(0)}} to all our classes that are executed 
by {{ignite.bat}} or {{ignite.sh}} because it's not harmful in any case.



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

[jira] [Commented] (IGNITE-1630) .Net: Create LINQ adapter for queries.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-1630:


* This may intersect with Entity Framework Data Provider functionality
* Investigate reLinq 
http://chris.eldredge.io/blog/2012/03/29/Getting-Started-With-Relinq/

> .Net: Create LINQ adapter for queries.
> --
>
> Key: IGNITE-1630
> URL: https://issues.apache.org/jira/browse/IGNITE-1630
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>
> *NOTE*: Is targeted for 1.6, but might be moved forward in case of tight 
> release schedule.
> SQL queries are one of the most frequently used features in data grids. And 
> .Net comes with a very nice LINQ concept. 
> We need to investigate and idea of own LINQ adapter which will delegate to 
> Ignite native query API.



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

[jira] [Comment Edited] (IGNITE-1630) .Net: Create LINQ adapter for queries.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-1630 at 1/14/16 12:11 PM:
--

* This may intersect with Entity Framework Data Provider functionality
* Investigate reLinq (it is under Apache license, and is used by EF and 
NHibernate)
  * http://chris.eldredge.io/blog/2012/03/29/Getting-Started-With-Relinq/
  * https://relinq.codeplex.com/


was (Author: ptupitsyn):
* This may intersect with Entity Framework Data Provider functionality
* Investigate reLinq 
http://chris.eldredge.io/blog/2012/03/29/Getting-Started-With-Relinq/

> .Net: Create LINQ adapter for queries.
> --
>
> Key: IGNITE-1630
> URL: https://issues.apache.org/jira/browse/IGNITE-1630
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>
> *NOTE*: Is targeted for 1.6, but might be moved forward in case of tight 
> release schedule.
> SQL queries are one of the most frequently used features in data grids. And 
> .Net comes with a very nice LINQ concept. 
> We need to investigate and idea of own LINQ adapter which will delegate to 
> Ignite native query API.



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

[jira] [Updated] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2379:
---
Fix Version/s: 1.6

> .NET: ASP.NET Output Cache provider
> ---
>
> Key: IGNITE-2379
> URL: https://issues.apache.org/jira/browse/IGNITE-2379
> Project: Ignite
>  Issue Type: New Feature
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Implement System.Web.Caching.OutputCacheProvider 
> (https://msdn.microsoft.com/en-us/library/system.web.caching.outputcacheprovider(v=vs.110).aspx)



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

[jira] [Assigned] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-2379:
--

Assignee: Pavel Tupitsyn

> .NET: ASP.NET Output Cache provider
> ---
>
> Key: IGNITE-2379
> URL: https://issues.apache.org/jira/browse/IGNITE-2379
> Project: Ignite
>  Issue Type: New Feature
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Implement System.Web.Caching.OutputCacheProvider 
> (https://msdn.microsoft.com/en-us/library/system.web.caching.outputcacheprovider(v=vs.110).aspx)



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

[jira] [Commented] (IGNITE-2376) .NET: UnmanagedUtils.IgnitionStart return value is never used

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2376:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2376 .NET: UnmanagedUtils.IgnitionStart return value is never used



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

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

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

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


commit ba1b0b17a1eb2a8af1497655d571316fa403e244
Author: Pavel Tupitsyn 
Date:   2016-01-14T11:35:59Z

IGNITE-2376 .NET: UnmanagedUtils.IgnitionStart return value is never used




> .NET: UnmanagedUtils.IgnitionStart return value is never used
> -
>
> Key: IGNITE-2376
> URL: https://issues.apache.org/jira/browse/IGNITE-2376
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> UnmanagedUtils.IgnitionStart is used only once, and return value is not used.
> Quick test to make it void resulted in OutOfMemory in tests on TC.
> Need to investigate what is going on.



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

[jira] [Created] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2379:
--

 Summary: .NET: ASP.NET Output Cache provider
 Key: IGNITE-2379
 URL: https://issues.apache.org/jira/browse/IGNITE-2379
 Project: Ignite
  Issue Type: New Feature
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn


Implement System.Web.Caching.OutputCacheProvider 
(https://msdn.microsoft.com/en-us/library/system.web.caching.outputcacheprovider(v=vs.110).aspx)



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

[jira] [Updated] (IGNITE-2377) Docker image hangs on Mac OS

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-2377:

Labels: newbie  (was: )

> Docker image hangs on Mac OS
> 
>
> Key: IGNITE-2377
> URL: https://issues.apache.org/jira/browse/IGNITE-2377
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>  Labels: newbie
> Fix For: 1.6
>
>
> Docker hangs at the point when {{CommandLineRandomNumberGenerator}} is being 
> executed. The reason is that the current and previous Docker version has some 
> bug that can be overcame if to put {{System.exit(0)}} at the end of 
> {{main(...)}} function.
> More investigation details and steps to reproduce can be found here:
> http://stackoverflow.com/questions/34661934/ignite-running-in-docker-is-general-java-docker-issue
> It makes sense to add {{System.exit(0)}} to all our classes that are executed 
> by {{ignite.bat}} or {{ignite.sh}} because it's not harmful in any case.



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

[jira] [Created] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2380:
--

 Summary: .NET: Ignite configuration in app.config and web.config
 Key: IGNITE-2380
 URL: https://issues.apache.org/jira/browse/IGNITE-2380
 Project: Ignite
  Issue Type: New Feature
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn


* Define custom ConfigurationSection for IgniteConfiguration
* Extend Ignition class to be able to start Ignite from app.config / web.config 
configuration



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

[jira] [Commented] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2379:


OutputCacheProvider is set in web.config. Need to figure out the Ignite 
instance lifetime and startup:
1. Provide "gridName" property. Starting Ignite is up to user (in Startup 
class, Global.asax, etc).
2. Provide springConfigUrl property to start the grid
3. ??

> .NET: ASP.NET Output Cache provider
> ---
>
> Key: IGNITE-2379
> URL: https://issues.apache.org/jira/browse/IGNITE-2379
> Project: Ignite
>  Issue Type: New Feature
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Implement System.Web.Caching.OutputCacheProvider 
> (https://msdn.microsoft.com/en-us/library/system.web.caching.outputcacheprovider(v=vs.110).aspx)



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

[jira] [Comment Edited] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-2379 at 1/14/16 2:19 PM:
-

OutputCacheProvider is set in web.config. Need to figure out the Ignite 
instance lifetime and startup:
1) Provide "gridName" property. Starting Ignite is up to user (in Startup 
class, Global.asax, etc).
2) Provide springConfigUrl property to start the grid
3) ??


was (Author: ptupitsyn):
OutputCacheProvider is set in web.config. Need to figure out the Ignite 
instance lifetime and startup:
1. Provide "gridName" property. Starting Ignite is up to user (in Startup 
class, Global.asax, etc).
2. Provide springConfigUrl property to start the grid
3. ??

> .NET: ASP.NET Output Cache provider
> ---
>
> Key: IGNITE-2379
> URL: https://issues.apache.org/jira/browse/IGNITE-2379
> Project: Ignite
>  Issue Type: New Feature
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Implement System.Web.Caching.OutputCacheProvider 
> (https://msdn.microsoft.com/en-us/library/system.web.caching.outputcacheprovider(v=vs.110).aspx)



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

[jira] [Commented] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2380:


Can't be done before IGNITE-1906

> .NET: Ignite configuration in app.config and web.config
> ---
>
> Key: IGNITE-2380
> URL: https://issues.apache.org/jira/browse/IGNITE-2380
> Project: Ignite
>  Issue Type: New Feature
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>
> * Define custom ConfigurationSection for IgniteConfiguration
> * Extend Ignition class to be able to start Ignite from app.config / 
> web.config configuration



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

[jira] [Assigned] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-2032:


Assignee: Alexey Goncharuk  (was: Semen Boikov)

> Filters passed to ScanQuery are not redeployed when originating from a client 
> node
> --
>
> Key: IGNITE-2032
> URL: https://issues.apache.org/jira/browse/IGNITE-2032
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
> Attachments: ScanQueryFailure.java, test-config.xml
>
>
> The following case doesn't work:
> - start a standalone server node with peer class loading enabled;
> - start a client node, populate a cache with data, perform a scan query using 
> a filter;
> - since the server doesn't have the filter in its classpath it will load it 
> from the client. Everything works fine here;
> - stop the client, the server will undeploy the filter. No issue here so far;
> - modify the filter a bit and start the client one more time. The server 
> won't deploy the new version of the filter and will be using the old 
> regardless of the fact that it was undeployed before according to the logs.
> The server can be started using ignite.bat and test-config.xml (attached).
> The source of the client is located in attached ScanQueryFailure.java.
> BTW, everything works fine if to use the server mode instead of the client 
> one.



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

[jira] [Updated] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2380:
---
Description: 
* Define custom ConfigurationSection for IgniteConfiguration (see 
https://msdn.microsoft.com/en-us/library/2tw134k3.aspx)
* Extend Ignition class to be able to start Ignite from app.config / web.config 
configuration

  was:
* Define custom ConfigurationSection for IgniteConfiguration
* Extend Ignition class to be able to start Ignite from app.config / web.config 
configuration


> .NET: Ignite configuration in app.config and web.config
> ---
>
> Key: IGNITE-2380
> URL: https://issues.apache.org/jira/browse/IGNITE-2380
> Project: Ignite
>  Issue Type: New Feature
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>
> * Define custom ConfigurationSection for IgniteConfiguration (see 
> https://msdn.microsoft.com/en-us/library/2tw134k3.aspx)
> * Extend Ignition class to be able to start Ignite from app.config / 
> web.config configuration



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

[jira] [Created] (IGNITE-2381) Move Indexed key-value pairs from Cache Screen to Metadata Screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2381:


 Summary: Move Indexed key-value pairs from Cache Screen to 
Metadata Screen
 Key: IGNITE-2381
 URL: https://issues.apache.org/jira/browse/IGNITE-2381
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Vasiliy Sisko
 Fix For: 1.6


It is more logical to configure indexed key-value pairs on Metadata screen.



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

[jira] [Updated] (IGNITE-2240) CPP: Implement SQLEndTran function for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2240:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1786

> CPP: Implement SQLEndTran function for the ODBC driver.
> ---
>
> Key: IGNITE-2240
> URL: https://issues.apache.org/jira/browse/IGNITE-2240
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This function listed in the [ODBC Core Interface 
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] 
> and should be implemented for our driver.



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

[jira] [Updated] (IGNITE-2382) Force client mode in JDBC driver and provide default configuration file

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-2382:

Description: 
# There is no reason to start server node during creation JDBC connection. So 
client mode should be forced.
# If user didn't specify any configuration file in JDBC URL then default 
configuration file should be used.
# Remove multicast IP finder from example because it is default IP finder.

Also need  sample step-by-step guide with a sample configuration. This 
configuration should include a couple of data types, like Person and 
Organization, define indexes for them, etc.

This guide should include:

# Start Ignite Servers
# Populate data - should have example with configuration.
# Query data using JDBC driver - example code and, if needed, configuration to 
support it.

See laso discussion here: 
http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html

  was:
# There is no reason to start server node during creation JDBC connection. So 
client mode should be forced.
# If user didn't specify any configuration file in JDBC URL then default 
configuration file should be used.
# Remove multicast IP finder from example because it is default IP finder.

See laso discussion here: 
http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html


> Force client mode in JDBC driver and provide default configuration file
> ---
>
> Key: IGNITE-2382
> URL: https://issues.apache.org/jira/browse/IGNITE-2382
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Minor
> Fix For: 1.6
>
>
> # There is no reason to start server node during creation JDBC connection. So 
> client mode should be forced.
> # If user didn't specify any configuration file in JDBC URL then default 
> configuration file should be used.
> # Remove multicast IP finder from example because it is default IP finder.
> Also need  sample step-by-step guide with a sample configuration. This 
> configuration should include a couple of data types, like Person and 
> Organization, define indexes for them, etc.
> This guide should include:
> # Start Ignite Servers
> # Populate data - should have example with configuration.
> # Query data using JDBC driver - example code and, if needed, configuration 
> to support it.
> See laso discussion here: 
> http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html



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

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-429:
-

Anton,

Run through the check list, warnings fixed. Unfortunately, I don't have 
permissions to add it to 'Streamers' on TC. May I ask you to add it?

As to 'Documentation & examples,' I will write an article on how to use it 
based on README.txt. Should I do it on readme.io (under ver. 1.5 I guess) or 
prepare a wiki file and attach it here?

> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
> Fix For: 1.6
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Updated] (IGNITE-2384) Notification missed in continuous query

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-2384:

Attachment: ListenerTest.java

> Notification missed in continuous query
> ---
>
> Key: IGNITE-2384
> URL: https://issues.apache.org/jira/browse/IGNITE-2384
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: ListenerTest.java
>
>
> Test reproducing the issue is attached, fails on assertion on line 76.



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

[jira] [Created] (IGNITE-2385) Rename metadata to domain model

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-2385:
-

 Summary: Rename metadata to domain model
 Key: IGNITE-2385
 URL: https://issues.apache.org/jira/browse/IGNITE-2385
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko






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

[jira] [Created] (IGNITE-2384) Notification missed in continuous query

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2384:
---

 Summary: Notification missed in continuous query
 Key: IGNITE-2384
 URL: https://issues.apache.org/jira/browse/IGNITE-2384
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
Priority: Critical
 Fix For: 1.6


Test reproducing the issue is attached, fails on assertion on line 76.



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

[jira] [Created] (IGNITE-2386) affinityCall() execution hangs

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2386:
---

 Summary: affinityCall() execution hangs
 Key: IGNITE-2386
 URL: https://issues.apache.org/jira/browse/IGNITE-2386
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
Priority: Critical
 Fix For: 1.6


Test reproducing the issue is attached. affinityCall() invocation hangs with 
the following trace:

{code}
"main" prio=5 tid=0x7f8b1b001800 nid=0x1703 waiting on condition 
[0x70218000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0007ab170eb8> (a 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture)
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.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:477)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:435)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.assignments(GridAffinityAssignmentCache.java:306)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignments(GridCacheAffinityManager.java:159)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:333)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:238)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.affinityCall(GridClosureProcessor.java:442)
at 
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:130)
at AffinityTest.main(AffinityTest.java:42)
{code}



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

[jira] [Updated] (IGNITE-2386) affinityCall() execution hangs

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-2386:

Description: 
Test reproducing the issue is attached. affinityCall() invocation hangs with 
the following trace:

{noformat}
"main" prio=5 tid=0x7f8b1b001800 nid=0x1703 waiting on condition 
[0x70218000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0007ab170eb8> (a 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture)
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.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:477)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:435)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.assignments(GridAffinityAssignmentCache.java:306)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignments(GridCacheAffinityManager.java:159)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:333)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:238)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.affinityCall(GridClosureProcessor.java:442)
at 
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:130)
at AffinityTest.main(AffinityTest.java:42)
{noformat}

  was:
Test reproducing the issue is attached. affinityCall() invocation hangs with 
the following trace:

{code}
"main" prio=5 tid=0x7f8b1b001800 nid=0x1703 waiting on condition 
[0x70218000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0007ab170eb8> (a 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture)
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.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:477)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:435)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.assignments(GridAffinityAssignmentCache.java:306)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignments(GridCacheAffinityManager.java:159)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:333)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:238)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.affinityCall(GridClosureProcessor.java:442)
at 
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:130)
at AffinityTest.main(AffinityTest.java:42)
{code}


> affinityCall() execution hangs
> --
>
> Key: IGNITE-2386
> URL: https://issues.apache.org/jira/browse/IGNITE-2386
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
>

[jira] [Updated] (IGNITE-2386) affinityCall() execution hangs

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-2386:

Flags: Important

> affinityCall() execution hangs
> --
>
> Key: IGNITE-2386
> URL: https://issues.apache.org/jira/browse/IGNITE-2386
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
>
> Test reproducing the issue is attached. affinityCall() invocation hangs with 
> the following trace:
> {code}
> "main" prio=5 tid=0x7f8b1b001800 nid=0x1703 waiting on condition 
> [0x70218000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0x0007ab170eb8> (a 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture)
>   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.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:477)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:435)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.assignments(GridAffinityAssignmentCache.java:306)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignments(GridCacheAffinityManager.java:159)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:333)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:238)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.affinityCall(GridClosureProcessor.java:442)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:130)
>   at AffinityTest.main(AffinityTest.java:42)
> {code}



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

[jira] [Updated] (IGNITE-2387) Ignite puzzle picture on readme.io has broken size in FireFox

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2387:
---
Attachment: ApacheIgnitePuzzlePicture.png

> Ignite puzzle picture on readme.io has broken size in FireFox
> -
>
> Key: IGNITE-2387
> URL: https://issues.apache.org/jira/browse/IGNITE-2387
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: ApacheIgnitePuzzlePicture.png
>
>




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

[jira] [Updated] (IGNITE-2387) Ignite puzzle picture on readme.io has broken size in Firefox

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2387:
---
Summary: Ignite puzzle picture on readme.io has broken size in Firefox  
(was: Ignite puzzle picture on readme.io has broken size in FireFox)

> Ignite puzzle picture on readme.io has broken size in Firefox
> -
>
> Key: IGNITE-2387
> URL: https://issues.apache.org/jira/browse/IGNITE-2387
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: ApacheIgnitePuzzlePicture.png
>
>




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

[jira] [Updated] (IGNITE-2387) Ignite puzzle picture on readme.io has broken size in Firefox

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2387:
---
Description: I've noticed that Ignite puzzle picture size on 
https://apacheignite.readme.io/ is broken in FireFox (in Chrome all OK).

> Ignite puzzle picture on readme.io has broken size in Firefox
> -
>
> Key: IGNITE-2387
> URL: https://issues.apache.org/jira/browse/IGNITE-2387
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: ApacheIgnitePuzzlePicture.png
>
>
> I've noticed that Ignite puzzle picture size on 
> https://apacheignite.readme.io/ is broken in FireFox (in Chrome all OK).



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

[jira] [Resolved] (IGNITE-2366) May be remove buttons from the bottom of the page (Save, Clone, Remove)

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-2366.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Removed bottom buttons.

> May be remove buttons from the bottom of the page (Save, Clone, Remove)
> ---
>
> Key: IGNITE-2366
> URL: https://issues.apache.org/jira/browse/IGNITE-2366
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 1.6
>
>
> We have the all needed button on the top of the page on floating panel which 
> makes buttons always visible on the screen.



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

[jira] [Created] (IGNITE-2387) Ignite puzzle picture on readme.io has broken size in FireFox

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2387:
--

 Summary: Ignite puzzle picture on readme.io has broken size in 
FireFox
 Key: IGNITE-2387
 URL: https://issues.apache.org/jira/browse/IGNITE-2387
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Minor






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

[jira] [Commented] (IGNITE-2191) Binary marshaller: support user classes with the same simple name

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-2191:
--

Finished with implementation. 

Also found and fixed the following bug: {{BinaryContext.typeId(typeName)}} 
method uses the default IdMapper for not registered types in process of 
initialization instead of calculating idMapper according to configuration.

Waiting for TC results. WIll fix tests and will write new ones.

> Binary marshaller: support user classes with the same simple name
> -
>
> Key: IGNITE-2191
> URL: https://issues.apache.org/jira/browse/IGNITE-2191
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Artem Shutak
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
>
> Presently the user won't be able to use across the cluster object that have a 
> single simple name.
> As an example if the user has 'org.comp.MyObject' and 
> 'org.apache.comp.MyObject' then he won't be able to have them both in a 
> cluster because marshalling mechanism supports uniqueness at simple name 
> level only.
> There are several reasons for that:
> - interoperability with other platforms;
> - queries that use simple name is their 'where' clause.
> In general according to the API as a workaround the user can implement its 
> own BinaryIdMapper returning a precise id for every class. However there is a 
> bug in BinaryContext that passes simple name rather than a full name to a 
> BinaryIdMapper implementation. BinaryIdMapper must be fixed as well.



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

[jira] [Comment Edited] (IGNITE-2381) Move Indexed key-value pairs from Cache Screen to Metadata Screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-2381 at 1/15/16 6:42 AM:


Indexed types removed from cache screen and moved to metadata screen. 
Added property metadata on metadata screen.
All metadata with property metadata set as 'Annotations' on cache used as 
indexed types.


was (Author: vsisko):
Indexed types removed from cache. 
Added property metadata on configuration of metadata.
All metadata with property metadata set as 'Annotations' on cache used as 
indexed types.

> Move Indexed key-value pairs from Cache Screen to Metadata Screen
> -
>
> Key: IGNITE-2381
> URL: https://issues.apache.org/jira/browse/IGNITE-2381
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 1.6
>
>
> It is more logical to configure indexed key-value pairs on Metadata screen.



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

[jira] [Comment Edited] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-429 at 1/15/16 6:42 AM:
--

Anton,

Ran through the check list, warnings fixed. Unfortunately, I don't have 
permissions to add it to 'Streamers' on TC. May I ask you to add it?

As to 'Documentation & examples,' I will write an article on how to use it 
based on README.txt. Should I do it on readme.io (under ver. 1.5 I guess) or 
prepare a wiki file and attach it here?


was (Author: roman_s):
Anton,

Run through the check list, warnings fixed. Unfortunately, I don't have 
permissions to add it to 'Streamers' on TC. May I ask you to add it?

As to 'Documentation & examples,' I will write an article on how to use it 
based on README.txt. Should I do it on readme.io (under ver. 1.5 I guess) or 
prepare a wiki file and attach it here?

> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
> Fix For: 1.6
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Updated] (IGNITE-2384) Notification missed in continuous query

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-2384:
-
Assignee: Nikolay Tikhonov

> Notification missed in continuous query
> ---
>
> Key: IGNITE-2384
> URL: https://issues.apache.org/jira/browse/IGNITE-2384
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Nikolay Tikhonov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: ListenerTest.java
>
>
> Test reproducing the issue is attached, fails on assertion on line 76.



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

[jira] [Created] (IGNITE-2388) Security issue in corner case

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2388:
--

 Summary: Security issue in corner case
 Key: IGNITE-2388
 URL: https://issues.apache.org/jira/browse/IGNITE-2388
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


To reproduce:
1) you should have admin rights
2) open admin page
3) become a ordinary user
4) click Back in browser

Observed: ordinary user can get access to admin page
Expected:  admin page must be inaccessible for ordinary user 



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

[jira] [Updated] (IGNITE-2386) affinityCall() execution hangs

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-2386:

Attachment: AffinityTest.java

> affinityCall() execution hangs
> --
>
> Key: IGNITE-2386
> URL: https://issues.apache.org/jira/browse/IGNITE-2386
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: AffinityTest.java
>
>
> Test reproducing the issue is attached. affinityCall() invocation hangs with 
> the following trace:
> {noformat}
> "main" prio=5 tid=0x7f8b1b001800 nid=0x1703 waiting on condition 
> [0x70218000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0x0007ab170eb8> (a 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture)
>   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.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:477)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:435)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.assignments(GridAffinityAssignmentCache.java:306)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignments(GridCacheAffinityManager.java:159)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:333)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:238)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.affinityCall(GridClosureProcessor.java:442)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:130)
>   at AffinityTest.main(AffinityTest.java:42)
> {noformat}



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

[jira] [Assigned] (IGNITE-2386) affinityCall() execution hangs

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-2386:


Assignee: Semen Boikov

> affinityCall() execution hangs
> --
>
> Key: IGNITE-2386
> URL: https://issues.apache.org/jira/browse/IGNITE-2386
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: AffinityTest.java
>
>
> Test reproducing the issue is attached. affinityCall() invocation hangs with 
> the following trace:
> {noformat}
> "main" prio=5 tid=0x7f8b1b001800 nid=0x1703 waiting on condition 
> [0x70218000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0x0007ab170eb8> (a 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture)
>   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.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:477)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:435)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.assignments(GridAffinityAssignmentCache.java:306)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignments(GridCacheAffinityManager.java:159)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:333)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:238)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.affinityCall(GridClosureProcessor.java:442)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:130)
>   at AffinityTest.main(AffinityTest.java:42)
> {noformat}



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

[jira] [Commented] (IGNITE-2381) Move Indexed key-value pairs from Cache Screen to Metadata Screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-2381:
---

Indexed types removed from cache. 
Added property metadata on configuration of metadata.
All metadata with property metadata set as 'Annotations' on cache used as 
indexed type.

> Move Indexed key-value pairs from Cache Screen to Metadata Screen
> -
>
> Key: IGNITE-2381
> URL: https://issues.apache.org/jira/browse/IGNITE-2381
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 1.6
>
>
> It is more logical to configure indexed key-value pairs on Metadata screen.



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

[jira] [Closed] (IGNITE-2366) May be remove buttons from the bottom of the page (Save, Clone, Remove)

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> May be remove buttons from the bottom of the page (Save, Clone, Remove)
> ---
>
> Key: IGNITE-2366
> URL: https://issues.apache.org/jira/browse/IGNITE-2366
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Trivial
> Fix For: 1.6
>
>
> We have the all needed button on the top of the page on floating panel which 
> makes buttons always visible on the screen.



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

[jira] [Updated] (IGNITE-2360) Add tooltip for "Key should be configured" link

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2360:
---
Description: 
1) In metadata page link to filter metadata without configured primary key 
fields should have elucidative tooltip.
2) Automatically switch to 'correct' metadata list after the last 'incorrect' 
was fixed (currently we stay on empty 'incorrect' list)

  was:In metadata page link to filter metadata without configured primary key 
fields should have elucidative tooltip.


> Add tooltip for "Key should be configured" link
> ---
>
> Key: IGNITE-2360
> URL: https://issues.apache.org/jira/browse/IGNITE-2360
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 1.6
>
>
> 1) In metadata page link to filter metadata without configured primary key 
> fields should have elucidative tooltip.
> 2) Automatically switch to 'correct' metadata list after the last 'incorrect' 
> was fixed (currently we stay on empty 'incorrect' list)



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

[jira] [Comment Edited] (IGNITE-2381) Move Indexed key-value pairs from Cache Screen to Metadata Screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-2381 at 1/15/16 6:22 AM:


Indexed types removed from cache. 
Added property metadata on configuration of metadata.
All metadata with property metadata set as 'Annotations' on cache used as 
indexed types.


was (Author: vsisko):
Indexed types removed from cache. 
Added property metadata on configuration of metadata.
All metadata with property metadata set as 'Annotations' on cache used as 
indexed type.

> Move Indexed key-value pairs from Cache Screen to Metadata Screen
> -
>
> Key: IGNITE-2381
> URL: https://issues.apache.org/jira/browse/IGNITE-2381
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 1.6
>
>
> It is more logical to configure indexed key-value pairs on Metadata screen.



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

[jira] [Created] (IGNITE-2389) Need to add ability to swap the queue if it's too long

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2389:
---

 Summary: Need to add ability to swap the queue if it's too long
 Key: IGNITE-2389
 URL: https://issues.apache.org/jira/browse/IGNITE-2389
 Project: Ignite
  Issue Type: Improvement
  Components: data structures
Reporter: Valentin Kulichenko
 Fix For: 1.6


In some cases there can be a requirement to start swapping new queue elements 
to avoid out of memory errors. For example, if the consumer temporarily stopped 
for some reason, but the producer still adds elements.

We can do this based on cache swap space and evictions. I think we should:
# Add max allowed in-memory elements property to {{CollectionConfiguration}}. 
We can also support limit by memory size.
# Implement special eviction policy that will evict new queue elements if 
limits are reached.
# Automatically unswap latest elements when consumer resumes polling (can be 
achieved by a background process).

In case of {{IgniteSet}}, limits should be also honored, but here we don't have 
ordering. So I think we can use our standard LRU, but make sure that only 
elements are swapped. Header and other meta objects should be always in memory.



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

[jira] [Updated] (IGNITE-2388) Routing issue in corner case

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2388:
-
Assignee: Andrey Novikov  (was: Alexey Kuznetsov)

> Routing issue in corner case
> 
>
> Key: IGNITE-2388
> URL: https://issues.apache.org/jira/browse/IGNITE-2388
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>
> To reproduce:
> 1) you should have admin rights
> 2) open admin page
> 3) become a ordinary user
> 4) click Back in browser
> Observed: ordinary user can get access to admin page
> Expected:  admin page must be inaccessible for ordinary user 



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

[jira] [Updated] (IGNITE-2388) Routing issue in corner case

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2388:
-
Summary: Routing issue in corner case  (was: Security issue in corner case)

> Routing issue in corner case
> 
>
> Key: IGNITE-2388
> URL: https://issues.apache.org/jira/browse/IGNITE-2388
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 1.6
>
>
> To reproduce:
> 1) you should have admin rights
> 2) open admin page
> 3) become a ordinary user
> 4) click Back in browser
> Observed: ordinary user can get access to admin page
> Expected:  admin page must be inaccessible for ordinary user 



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

[jira] [Updated] (IGNITE-2390) IGFS path modes are not honored

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-2390:

Assignee: Ivan Veselovsky

> IGFS path modes are not honored
> ---
>
> Key: IGNITE-2390
> URL: https://issues.apache.org/jira/browse/IGNITE-2390
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.5
>Reporter: Denis Magda
>Assignee: Ivan Veselovsky
> Fix For: 1.6
>
>
> The following configuration is used with some specific path modes.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On running a simple MR job an output dir is set under /tmp
> e.g.
> /tmp/denis2
> as such I would expect this to be in memory only, and no changes seen on the 
> secondary file system as path is set to PRIMARY.
> On checking HDFS I find that these files are created by Ignite on the 
> secondary file system.
> Found that document here:
> http://apacheignite.gridgain.org/docs/modes
> is incorrect, the paths are not regex patterns as this document implies, but 
> simply the code checks if path string starts with.
> Have removed /.* from the above config and seems to be resolved.
> The configuration must be fixed or the code.



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

[jira] [Commented] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2032:


Github user asfgit closed the pull request at:

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


> Filters passed to ScanQuery are not redeployed when originating from a client 
> node
> --
>
> Key: IGNITE-2032
> URL: https://issues.apache.org/jira/browse/IGNITE-2032
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
> Attachments: ScanQueryFailure.java, test-config.xml
>
>
> The following case doesn't work:
> - start a standalone server node with peer class loading enabled;
> - start a client node, populate a cache with data, perform a scan query using 
> a filter;
> - since the server doesn't have the filter in its classpath it will load it 
> from the client. Everything works fine here;
> - stop the client, the server will undeploy the filter. No issue here so far;
> - modify the filter a bit and start the client one more time. The server 
> won't deploy the new version of the filter and will be using the old 
> regardless of the fact that it was undeployed before according to the logs.
> The server can be started using ignite.bat and test-config.xml (attached).
> The source of the client is located in attached ScanQueryFailure.java.
> BTW, everything works fine if to use the server mode instead of the client 
> one.



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

[jira] [Commented] (IGNITE-2099) Binary marshaller writes any map as a HashMap

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2099:


Github user asfgit closed the pull request at:

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


> Binary marshaller writes any map as a HashMap
> -
>
> Key: IGNITE-2099
> URL: https://issues.apache.org/jira/browse/IGNITE-2099
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Reporter: Valentin Kulichenko
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> Bug is described and discussed in this user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Serialization-issue-with-Ignite-1-5-built-from-master-357d791-td2149.html
> In general, we need to make sure that binary marshaller fully supports Java 
> serialization and behaves consistently with optimized marshaller.



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

[jira] [Commented] (IGNITE-2389) Need to add ability to swap the queue if it's too long

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-2389:
--

Context: 
http://apache-ignite-users.70518.x6.nabble.com/Stupide-question-about-Queue-td2557.html

> Need to add ability to swap the queue if it's too long
> --
>
> Key: IGNITE-2389
> URL: https://issues.apache.org/jira/browse/IGNITE-2389
> Project: Ignite
>  Issue Type: Improvement
>  Components: data structures
>Reporter: Valentin Kulichenko
> Fix For: 1.6
>
>
> In some cases there can be a requirement to start swapping new queue elements 
> to avoid out of memory errors. For example, if the consumer temporarily 
> stopped for some reason, but the producer still adds elements.
> We can do this based on cache swap space and evictions. I think we should:
> # Add max allowed in-memory elements property to {{CollectionConfiguration}}. 
> We can also support limit by memory size.
> # Implement special eviction policy that will evict new queue elements if 
> limits are reached.
> # Automatically unswap latest elements when consumer resumes polling (can be 
> achieved by a background process).
> In case of {{IgniteSet}}, limits should be also honored, but here we don't 
> have ordering. So I think we can use our standard LRU, but make sure that 
> only elements are swapped. Header and other meta objects should be always in 
> memory.



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

[jira] [Updated] (IGNITE-2343) IGFS: MapReduce task sent by Hunk/Splunk fails with NPE

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-2343:

Attachment: splunk.log.txt
ignite-2bcc8d7c.log.txt
ignite.thread.log.txt

> IGFS: MapReduce task sent by Hunk/Splunk fails with NPE
> ---
>
> Key: IGNITE-2343
> URL: https://issues.apache.org/jira/browse/IGNITE-2343
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.5
>Reporter: Denis Magda
>Assignee: Ivan Veselovsky
>  Labels: important
> Fix For: 1.6
>
> Attachments: ignite-2bcc8d7c.log.txt, ignite.thread.log.txt, 
> splunk.log.txt
>
>
> A MR task being sent by Hunk [1] fails with NPE
> {noformat}
> [10:31:58,250][ERROR][Hadoop-task-fd3ff783-d952-4147-8e5b-8e3080b91ddb_1-MAP-50-
>  0-#271%null%][HadoopRunnableTask] Task execution failed.
> class org.apache.ignite.IgniteCheckedException: class 
> org.apache.ignite.IgniteCh eckedException: null
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0( 
> HadoopV2MapTask.java:105)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2Task.run(Hado 
> opV2Task.java:54)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> un(HadoopV2TaskContext.java:249)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.runTask(HadoopRunnableTask.java:201)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call0(HadoopRunnableTask.java:144)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:116)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1 
> .run(HadoopV2TaskContext.java:550)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma 
> tion.java:1657)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> unAsJobOwner(HadoopV2TaskContext.java:548)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:46)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu 
> torService$2.body(HadoopExecutorService.java:186)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at com.splunk.mr.SplunkSearchMapper.runImpl(SplunkSearchMapper.java:308)
> at com.splunk.mr.SplunkBaseMapper.run(SplunkBaseMapper.java:169)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0( 
> HadoopV2MapTask.java:87)
> ... 16 more
> at org.apache.ignite.internal.processors.hadoop.HadoopUtils.transformExc 
> eption(HadoopUtils.java:290)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> un(HadoopV2TaskContext.java:255)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.runTask(HadoopRunnableTask.java:201)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call0(HadoopRunnableTask.java:144)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:116)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1 
> .run(HadoopV2TaskContext.java:550)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma 
> tion.java:1657)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> unAsJobOwner(HadoopV2TaskContext.java:548)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:46)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu 
> torService$2.body(HadoopExecutorService.java:186)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> [1] http://www.splunk.com/en_us/products/hunk.html



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

[jira] [Commented] (IGNITE-2343) IGFS: MapReduce task sent by Hunk/Splunk fails with NPE

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2343:
-

MR doesn't work if tmp and the splunk user are running NOT in IGFS PRIMARY 
mode. 
If to put splunk user and tmp dirs on PRIMARY mode only that everything works 
fine.

Attached logs and thread dumps that might be useful.

> IGFS: MapReduce task sent by Hunk/Splunk fails with NPE
> ---
>
> Key: IGNITE-2343
> URL: https://issues.apache.org/jira/browse/IGNITE-2343
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.5
>Reporter: Denis Magda
>Assignee: Ivan Veselovsky
>  Labels: important
> Fix For: 1.6
>
>
> A MR task being sent by Hunk [1] fails with NPE
> {noformat}
> [10:31:58,250][ERROR][Hadoop-task-fd3ff783-d952-4147-8e5b-8e3080b91ddb_1-MAP-50-
>  0-#271%null%][HadoopRunnableTask] Task execution failed.
> class org.apache.ignite.IgniteCheckedException: class 
> org.apache.ignite.IgniteCh eckedException: null
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0( 
> HadoopV2MapTask.java:105)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2Task.run(Hado 
> opV2Task.java:54)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> un(HadoopV2TaskContext.java:249)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.runTask(HadoopRunnableTask.java:201)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call0(HadoopRunnableTask.java:144)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:116)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1 
> .run(HadoopV2TaskContext.java:550)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma 
> tion.java:1657)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> unAsJobOwner(HadoopV2TaskContext.java:548)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:46)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu 
> torService$2.body(HadoopExecutorService.java:186)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at com.splunk.mr.SplunkSearchMapper.runImpl(SplunkSearchMapper.java:308)
> at com.splunk.mr.SplunkBaseMapper.run(SplunkBaseMapper.java:169)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0( 
> HadoopV2MapTask.java:87)
> ... 16 more
> at org.apache.ignite.internal.processors.hadoop.HadoopUtils.transformExc 
> eption(HadoopUtils.java:290)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> un(HadoopV2TaskContext.java:255)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.runTask(HadoopRunnableTask.java:201)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call0(HadoopRunnableTask.java:144)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:116)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask$1.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1 
> .run(HadoopV2TaskContext.java:550)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma 
> tion.java:1657)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r 
> unAsJobOwner(HadoopV2TaskContext.java:548)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna 
> bleTask.call(HadoopRunnableTask.java:46)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu 
> torService$2.body(HadoopExecutorService.java:186)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> [1] 

[jira] [Created] (IGNITE-2390) IGFS path modes are not honored

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2390:
---

 Summary: IGFS path modes are not honored
 Key: IGNITE-2390
 URL: https://issues.apache.org/jira/browse/IGNITE-2390
 Project: Ignite
  Issue Type: Bug
  Components: IGFS
Affects Versions: 1.5
Reporter: Denis Magda
 Fix For: 1.6


The following configuration is used with some specific path modes.












On running a simple MR job an output dir is set under /tmp
e.g.
/tmp/denis2

as such I would expect this to be in memory only, and no changes seen on the 
secondary file system as path is set to PRIMARY.

On checking HDFS I find that these files are created by Ignite on the secondary 
file system.

Found that document here:
http://apacheignite.gridgain.org/docs/modes

is incorrect, the paths are not regex patterns as this document implies, but 
simply the code checks if path string starts with.
Have removed /.* from the above config and seems to be resolved.

The configuration must be fixed or the code.



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

[jira] [Resolved] (IGNITE-2381) Move Indexed key-value pairs from Cache Screen to Metadata Screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-2381.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Move Indexed key-value pairs from Cache Screen to Metadata Screen
> -
>
> Key: IGNITE-2381
> URL: https://issues.apache.org/jira/browse/IGNITE-2381
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> It is more logical to configure indexed key-value pairs on Metadata screen.



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

[jira] [Closed] (IGNITE-2350) Make IGNITE_UPDATE_NOTIFIER per cluster setting

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2350.


Fix confirmed.

> Make IGNITE_UPDATE_NOTIFIER per cluster setting
> ---
>
> Key: IGNITE-2350
> URL: https://issues.apache.org/jira/browse/IGNITE-2350
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Ilya Suntsov
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
>
> We need to refactor update notification behavior to make it more transparent.
> # The first node (topVer=1) should behave in accordance to its local settings
> # The first node should set cluster-wide default which should survive its 
> (first node) exit.
> # Further nodes should ignore local setting and respect cluster wide value 
> set on cluster start



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

[jira] [Assigned] (IGNITE-2350) Make IGNITE_UPDATE_NOTIFIER per cluster setting

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov reassigned IGNITE-2350:


Assignee: Ilya Suntsov  (was: Sergey Kozlov)

> Make IGNITE_UPDATE_NOTIFIER per cluster setting
> ---
>
> Key: IGNITE-2350
> URL: https://issues.apache.org/jira/browse/IGNITE-2350
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Ilya Suntsov
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
>
> We need to refactor update notification behavior to make it more transparent.
> # The first node (topVer=1) should behave in accordance to its local settings
> # The first node should set cluster-wide default which should survive its 
> (first node) exit.
> # Further nodes should ignore local setting and respect cluster wide value 
> set on cluster start



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

[jira] [Created] (IGNITE-2382) Force client mode in JDBC driver and provide default configuration file

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-2382:
---

 Summary: Force client mode in JDBC driver and provide default 
configuration file
 Key: IGNITE-2382
 URL: https://issues.apache.org/jira/browse/IGNITE-2382
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Gura
Assignee: Andrey Gura
Priority: Minor
 Fix For: 1.6


#. There is no reason to start server node during creation JDBC connection. So 
client mode should be forced.
#. If user didn't specify any configuration file in JDBC URL then default 
configuration file should be used.
#. Remove multicast IP finder from example because it is default IP finder.

See laso discussion here: 
http://apache-ignite-developers.2346864.n4.nabble.com/What-is-jdbc-ignite-cfg-td5573.html



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

[jira] [Created] (IGNITE-2383) Non-string system properties should be ignored in node attributes and update checker

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2383:
---

 Summary: Non-string system properties should be ignored in node 
attributes and update checker
 Key: IGNITE-2383
 URL: https://issues.apache.org/jira/browse/IGNITE-2383
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
 Fix For: 1.6


user@ discussion: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-quot-bugs-quot-td2534.html

Some frameworks can put non-string and/or non-serializable values into system 
properties. We should ignore them in 
{{GridUpdateNotifier.getSystemProperties()}} method and when adding properties 
to node attributes.



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