[jira] [Closed] (IGNITE-1522) Cache entry listener is executed on a joining node
[ https://issues.apache.org/jira/browse/IGNITE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-1522. --- > Cache entry listener is executed on a joining node > -- > > Key: IGNITE-1522 > URL: https://issues.apache.org/jira/browse/IGNITE-1522 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Blocker > Fix For: ignite-1.4 > > > Scenario is the following: > # Start first node. > # Register cache entry listener. Its configuration is added to cache > configuration (required by JCache). > # Start second node. > # As a result entry listener configuration is serialized as a part of cache > configuration, which is wrong. Moreover, it's executed on this new node. > Need to make listener configurations transient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1522) Cache entry listener is executed on a joining node
[ https://issues.apache.org/jira/browse/IGNITE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-1522. - Resolution: Fixed Fixed in 1.4 > Cache entry listener is executed on a joining node > -- > > Key: IGNITE-1522 > URL: https://issues.apache.org/jira/browse/IGNITE-1522 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Blocker > Fix For: ignite-1.4 > > > Scenario is the following: > # Start first node. > # Register cache entry listener. Its configuration is added to cache > configuration (required by JCache). > # Start second node. > # As a result entry listener configuration is serialized as a part of cache > configuration, which is wrong. Moreover, it's executed on this new node. > Need to make listener configurations transient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1522) Cache entry listener is executed on a joining node
[ https://issues.apache.org/jira/browse/IGNITE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902037#comment-14902037 ] ASF GitHub Bot commented on IGNITE-1522: Github user vkulichenko closed the pull request at: https://github.com/apache/ignite/pull/103 > Cache entry listener is executed on a joining node > -- > > Key: IGNITE-1522 > URL: https://issues.apache.org/jira/browse/IGNITE-1522 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Blocker > Fix For: ignite-1.4 > > > Scenario is the following: > # Start first node. > # Register cache entry listener. Its configuration is added to cache > configuration (required by JCache). > # Start second node. > # As a result entry listener configuration is serialized as a part of cache > configuration, which is wrong. Moreover, it's executed on this new node. > Need to make listener configurations transient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901890#comment-14901890 ] Vasiliy Sisko commented on IGNITE-1489: --- Add confirmation about unsaved changes on a profile page. > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > Attachments: ig-1489-1.png, ig-1489-2.png > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1489: --- Attachment: ig-1489-2.png > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > Attachments: ig-1489-1.png, ig-1489-2.png > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901852#comment-14901852 ] Pavel Konstantinov commented on IGNITE-1489: Metadata screen: display Key\Value Type without package name only class name. Package name display in separate filed. Please see attachment for details (1489-2). > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > Attachments: ig-1489-1.png, ig-1489-2.png > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1276) Implement POJO classes generation.
[ https://issues.apache.org/jira/browse/IGNITE-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901782#comment-14901782 ] Vasiliy Sisko commented on IGNITE-1276: --- Implemented showing of POJO in web console. > Implement POJO classes generation. > -- > > Key: IGNITE-1276 > URL: https://issues.apache.org/jira/browse/IGNITE-1276 > Project: Ignite > Issue Type: Sub-task > Components: UI >Affects Versions: ignite-1.4 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > > Schema import utility generates POJO classes. > Web control centre should generate too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1522) Cache entry listener is executed on a joining node
[ https://issues.apache.org/jira/browse/IGNITE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901616#comment-14901616 ] ASF GitHub Bot commented on IGNITE-1522: GitHub user vkulichenko opened a pull request: https://github.com/apache/ignite/pull/103 IGNITE-1522 - Made cache entry listener configurations transient You can merge this pull request into a Git repository by running: $ git pull https://github.com/vkulichenko/incubator-ignite ignite-1522 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/103.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 #103 commit b6de049252411c2c1e13e00803adf5312cf3eb8a Author: Valentin Kulichenko Date: 2015-09-21T23:31:51Z IGNITE-1522 - Made cache entry listener configurations transient in cache configuration > Cache entry listener is executed on a joining node > -- > > Key: IGNITE-1522 > URL: https://issues.apache.org/jira/browse/IGNITE-1522 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Blocker > Fix For: ignite-1.4 > > > Scenario is the following: > # Start first node. > # Register cache entry listener. Its configuration is added to cache > configuration (required by JCache). > # Start second node. > # As a result entry listener configuration is serialized as a part of cache > configuration, which is wrong. Moreover, it's executed on this new node. > Need to make listener configurations transient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1181) Comparatively benchmark ordinary Hive vs. Hive over Ignited Hadoop.
[
https://issues.apache.org/jira/browse/IGNITE-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901596#comment-14901596
]
Konstantin Boudnik commented on IGNITE-1181:
I just did some quite and dirty benchmarking using a simple data sample and
running a query, producing a couple of map-reduce jobs, ie
{code}
select count(*) from batting where year > 1909 and year < 1998;
{code}
What I see is 5x performance improvement compare to the case of Hive over YARN.
> Comparatively benchmark ordinary Hive vs. Hive over Ignited Hadoop.
> ---
>
> Key: IGNITE-1181
> URL: https://issues.apache.org/jira/browse/IGNITE-1181
> Project: Ignite
> Issue Type: Task
> Components: hadoop
>Affects Versions: sprint-8
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: ignite-1.6
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1523) Need to make marshaller in discovery pluggable
Valentin Kulichenko created IGNITE-1523:
---
Summary: Need to make marshaller in discovery pluggable
Key: IGNITE-1523
URL: https://issues.apache.org/jira/browse/IGNITE-1523
Project: Ignite
Issue Type: Improvement
Components: general
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Blocker
Fix For: ignite-1.4
Currently we always use {{JdkMarshaller}}. It can be useful to use a custom
one. Need to add {{TcpDiscoverySpi.setMarshaller()}} method to allow this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1522) Cache entry listener is executed on a joining node
Valentin Kulichenko created IGNITE-1522: --- Summary: Cache entry listener is executed on a joining node Key: IGNITE-1522 URL: https://issues.apache.org/jira/browse/IGNITE-1522 Project: Ignite Issue Type: Bug Components: cache Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko Priority: Blocker Fix For: ignite-1.4 Scenario is the following: # Start first node. # Register cache entry listener. Its configuration is added to cache configuration (required by JCache). # Start second node. # As a result entry listener configuration is serialized as a part of cache configuration, which is wrong. Moreover, it's executed on this new node. Need to make listener configurations transient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901355#comment-14901355 ] Alexandre Boudnik commented on IGNITE-1371: --- Hi Raúl, Still working on this and hope I'll have working prototype very soon. > Key-Value store (like Cassandra) as CacheStore > -- > > Key: IGNITE-1371 > URL: https://issues.apache.org/jira/browse/IGNITE-1371 > Project: Ignite > Issue Type: New Feature > Components: cache >Reporter: Alexandre Boudnik >Assignee: Alexandre Boudnik > Original Estimate: 504h > Remaining Estimate: 504h > > It will provide ability to map particular cache holding POJOs to Cassandra > table. Later it would be generalized to support eventually any any Key-Value > store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandre Boudnik updated IGNITE-1371: -- Description: It will provide ability to map particular cache holding POJOs to Cassandra table. Later it would be generalized to support eventually any any Key-Value store. > Key-Value store (like Cassandra) as CacheStore > -- > > Key: IGNITE-1371 > URL: https://issues.apache.org/jira/browse/IGNITE-1371 > Project: Ignite > Issue Type: New Feature > Components: cache >Reporter: Alexandre Boudnik >Assignee: Alexandre Boudnik > Original Estimate: 504h > Remaining Estimate: 504h > > It will provide ability to map particular cache holding POJOs to Cassandra > table. Later it would be generalized to support eventually any any Key-Value > store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901160#comment-14901160
]
Semen Boikov commented on IGNITE-973:
-
Sergi,
I fixed error on cache side and now old value is provided to indexing for cache
'remove' operation (fix is in ignite-1.4), but error 'Failed to get value for
key' still reproduces. Please take a look.
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1521) Exception when running sql benchmark on AWS
[
https://issues.apache.org/jira/browse/IGNITE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900963#comment-14900963
]
Artem Shutak commented on IGNITE-1521:
--
My assume it had been 2 different versions of ignite at the classpath. For
example, as I see {code}1.2.0-incubating{code}
at
https://github.com/apacheignite/yardstick-ignite/blob/master/pom.xml. But tests
have been run for ignite-1.4 (it has been copied manually at libs/ dir).
For better investigation I need to have more detailed steps what have been done
and logs.
> Exception when running sql benchmark on AWS
> ---
>
> Key: IGNITE-1521
> URL: https://issues.apache.org/jira/browse/IGNITE-1521
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Ilya Suntsov
>Assignee: Artem Shutak
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> 1. I fork this repo: https://github.com/apacheignite/yardstick-ignite
> 2. Clone it
> 3. Used the following docs for start SQL benchmarks on AWS:
> https://github.com/yardstick-benchmarks/yardstick-docker
> And got the following exception:
> {noformat}
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> java.lang.NoSuchMethodError:
> org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery.(Ljava/util/Set;Ljava/lang/String;[Ljava/lang/Object;)V
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:216)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:859)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:807)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:662)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:660)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:660)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:618)
> at
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:85)
> at
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:61)
> at
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1521) Exception when running sql benchmark on AWS
Ilya Suntsov created IGNITE-1521:
Summary: Exception when running sql benchmark on AWS
Key: IGNITE-1521
URL: https://issues.apache.org/jira/browse/IGNITE-1521
Project: Ignite
Issue Type: Bug
Components: SQL
Affects Versions: ignite-1.4
Reporter: Ilya Suntsov
Assignee: Artem Shutak
Priority: Blocker
Fix For: ignite-1.4
1. I fork this repo: https://github.com/apacheignite/yardstick-ignite
2. Clone it
3. Used the following docs for start SQL benchmarks on AWS:
https://github.com/yardstick-benchmarks/yardstick-docker
And got the following exception:
{noformat}
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
java.lang.NoSuchMethodError:
org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery.(Ljava/util/Set;Ljava/lang/String;[Ljava/lang/Object;)V
at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:216)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:859)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:807)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:662)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:660)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:660)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:618)
at
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:85)
at
org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:61)
at
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-535) Implement IgniteMqttStreamer to stream data from MQTT
[
https://issues.apache.org/jira/browse/IGNITE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani resolved IGNITE-535.
---
Resolution: Fixed
Fix Version/s: ignite-1.5
Merged into master in 88acd318b84ce3bff8c061bb34718e0e5f7127fb.
> Implement IgniteMqttStreamer to stream data from MQTT
> -
>
> Key: IGNITE-535
> URL: https://issues.apache.org/jira/browse/IGNITE-535
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [MQTT|http://mqtt.org/] site for more info.
> We should create {{IgniteMqttStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert MQTT messages to Ignite data using an optional pluggable converter.
> If not provided, we should have some default mechanism.
> * 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-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900912#comment-14900912 ] Ivan Veselovsky commented on IGNITE-586: corrected by review results, ran tests on TC. > [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC. > - > > Key: IGNITE-586 > URL: https://issues.apache.org/jira/browse/IGNITE-586 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Vladimir Ozerov > Labels: failedtest > Fix For: ignite-1.5 > > > The problem is that format() doesn't clean all previously written data. > See GG-8578 (the issue was closed, but stay reproducible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used
[
https://issues.apache.org/jira/browse/IGNITE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1272:
Priority: Blocker (was: Major)
> PortableMarshaller: issues when different class loaders are used
>
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}}
> by type id. Returned descriptor has a constructor which already has been
> loaded with another class loader. Fix is not trivial and issue is reproduced
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1500) Invalid docs in distributed data structures classes.
[
https://issues.apache.org/jira/browse/IGNITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura closed IGNITE-1500.
---
> Invalid docs in distributed data structures classes.
>
>
> Key: IGNITE-1500
> URL: https://issues.apache.org/jira/browse/IGNITE-1500
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
>
> Problem: it is mentioned that async operations are supported, while they are
> not:
> {code}All previously described methods have asynchronous analogs.{code}
> Affected classes:
> - IgniteAtomicLong
> - IgniteAtomicReference
> - IgniteAtomicSequence
> - IgniteAtomicStamped
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900833#comment-14900833
]
ASF GitHub Bot commented on IGNITE-1370:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/85
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1520) IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of IgfsMetaManager#moveNonTx
Ivan Veselovsky created IGNITE-1520: --- Summary: IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of IgfsMetaManager#moveNonTx Key: IGNITE-1520 URL: https://issues.apache.org/jira/browse/IGNITE-1520 Project: Ignite Issue Type: Improvement Reporter: Ivan Veselovsky Assignee: Ivan Veselovsky In IGNITE-586 we implenmented method IgfsMetaManager#move that performs generic move work. Since IgfsMetaManager#renameDual has similar functionality , we should refactor code to reuse IgfsMetaManager#move in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm
[
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900558#comment-14900558
]
Chandresh Pancholi commented on IGNITE-429:
---
Gian,
I have included your suggestions and wrote unit test as well but i am having
problem with getStreamer() and getIgnite(). Its giving me null.
I have pushed the code(https://github.com/chandresh-pancholi/ignite). can you
please check?
Thanks
> 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: Chandresh Pancholi
>
> 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-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-1494:
-
Priority: Major (was: Critical)
Fix Version/s: (was: ignite-1.4)
ignite-1.5
I found that test can fail only with ATOMIC cache with
atomicWriteOrderMode=CLOCK and only if cache.removeAll() (without parameters)
operation is used.
In CLOCK mode update version is generated on the node initiated update,
cache.removeAll() is implemented as compute job which is executed on server
node, so it is possible that if client executes 'put' right after 'removeAll()'
operation then version generated on client for 'put' will be smaller than
version generated on server for 'remove' and 'put' will be ignored.
Need discuss if it makes sense to fix this issue, for now I suggest to change
test to add 1sec delay after 'removeAll()'.
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Semen Boikov
> Fix For: ignite-1.5
>
> Attachments: CacheTestExample.java, grid_config_01.client.xml,
> grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
> directory (it contains 25 FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
> 4. Build and run CacheTestExample (it makes put/get/remove operations for 100
> keys) a few times (w/o stopping server nodes)
> 5. The normal output should be following:
> {noformat}
> [12:12:02] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [12:12:02]
> [12:12:02] Ignite node started OK (id=3f1ea113)
> [12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
> >>>cache_0001
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0002
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0003
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_0011
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Get 21..100
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1519) Introduce Ignite type configuration.
Vladimir Ozerov created IGNITE-1519:
---
Summary: Introduce Ignite type configuration.
Key: IGNITE-1519
URL: https://issues.apache.org/jira/browse/IGNITE-1519
Project: Ignite
Issue Type: Task
Components: general
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
Fix For: ignite-1.5
*Problem*:
Ignite has sophisticated type configuration defined in classes
[CacheTypeMetadata|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/CacheTypeMetadata.java],
[CacheTypeFieldMetadata|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/CacheTypeFieldMetadata.java],
[org.apache.ignite.cache.query.annotations|https://github.com/apache/ignite/tree/master/modules/core/src/main/java/org/apache/ignite/cache/query/annotations].
We are planning to add portable and platform features. Portables will have
their own configuration describing how to find fields in serialized object
without having a class (see
[PortableMarshaller|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/portable/api/PortableMarshaller.java]
and
[PortableTypeConfiguration|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/portable/api/PortableTypeConfiguration.java]).
Platforms will also have type configuration which is passed to native platform
to map portable types (see
[PlatformDotNetPortableTypeConfiguration|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/dotnet/PlatformDotNetPortableTypeConfiguration.java]).
Trying to configure all these stuff will be a nightmare for users.
*Goal*:
Simplify and unify Ignite types system to make it more user-friendly.
*Considerations*:
1) Backward compatibility must be preserved.
2) Four interested parties must be considered: cache queries, JDBC store,
portables, platforms.
3) Per-cache configuration must stay because different caches may need to
interpret the same type differently (e.g. create index in cache A, but do not
do that in cache B).
4) CacheTypeMetadata is essentially a pair of key and value types.
5) PortableTypeConfiguration is configured for either single class or all
classes in some package.
*Raw design proposal*:
1) Define a new property in IgniteConfiguration "typesConfiguration" accepting
collection of objects "TypeConfiguration".
2) TypeConfiguration structure:
{code}
name : String
fields : Map
affKeyField: String
portableConfig : TypePortableConfig
dotNetConfig : TypeDotNetConfiguration
{code}
"name" is type name as it is used everywhere in the system.
"fields" is a map from field name to field type. Must be provided at least if
queries or POJO store is used. When defined, we register them in portable
metadata on startup if type is portable.
"affKeyField" name of affinity key field, used for query colocation and in
portables.
"portableConfig" is what PortableTypeConfiguration currently is.
"dotNetConfig" is platform-specific configuration for .Net, e.g. assembly name.
3) CacheTypeMetadata stay in CacheConfiguration but is simplified, because we
no longer need to define field classes. Normally user will only define several
sets or varargs (not maps!) of field names for indexes and query fields.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
