[jira] [Updated] (IGNITE-1338) SQL engine doesn't convert query fields name in upper case before using
[
https://issues.apache.org/jira/browse/IGNITE-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-1338:
Fix Version/s: (was: 2.0)
1.9
> SQL engine doesn't convert query fields name in upper case before using
> ---
>
> Key: IGNITE-1338
> URL: https://issues.apache.org/jira/browse/IGNITE-1338
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Sergey Kalashnikov
>Priority: Trivial
> Fix For: 1.9
>
> Attachments: test-cluster-2.xml
>
>
> Node can not be started if query fields name written in *lower case* and key
> fields with the *same* fields in *upper case* in cache type metadata.
> Please use attached configuration file for reproducing.
> {code}
> [14:30:28,526][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> class org.apache.ignite.IgniteCheckedException: Failed to register query
> type: TypeDescriptor [name=org.apache.ignite.Comalgorithm,
> fields={APCSBJCODE=class java.math.BigDecimal, APCID=class
> java.math.BigDecimal, AGRSBJCODE=class java.math.BigDecimal, AGRID=class
> java.math.BigDecimal, DAOSBJCODE=class java.math.BigDecimal, DAOID=class
> java.math.BigDecimal, CTPSBJCODE=class java.math.BigDecimal, CTPID=class
> java.math.BigDecimal, apcsbjcode=class java.math.BigDecimal, apcid=class
> java.math.BigDecimal, algcode=class java.math.BigDecimal,
> algisversioned=class java.lang.Short, algtype=class java.lang.Integer,
> algcalcobjecttype=class java.lang.Integer, algclasspath=class
> java.lang.String, algcomment=class java.lang.String, algopendate=class
> java.sql.Date, algclosedate=class java.sql.Date, algentstatus=class
> java.lang.Integer, agrsbjcode=class java.math.BigDecimal, agrid=class
> java.math.BigDecimal, daosbjcode=class java.math.BigDecimal, daoid=class
> java.math.BigDecimal, ctpsbjcode=class java.math.BigDecimal, ctpid=class
> java.math.BigDecimal, algusefields=class java.lang.String},
> indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED],
> FK3COMALGORITHM=IndexDescriptor [type=SORTED],
> FK4COMALGORITHM=IndexDescriptor [type=SORTED],
> SQL050208183448780=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
> keyCls=class java.lang.Object, valCls=class java.lang.Object,
> valTextIdx=false, registered=false]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1058)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:194)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:292)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1048)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:820)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:963)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546)
> at org.apache.ignite.Ignition.start(Ignition.java:346)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбца "APCSBJCODE"
> Duplicate column name "APCSBJCODE"; SQL statement:
> CREATE TABLE "cache2".org_apache_ignite_Comalgorithm (_key OTHER NOT
> NULL,_val OTHER,APCSBJCODE DECIMAL,APCID DECIMAL,AGRSBJCODE DECIMAL,AGRID
> DECIMAL,DAOSBJCODE DECIMAL,DAOID DECIMAL,CTPSBJCODE DECIMAL,CTPID
> DECIMAL,apcsbjcode DECIMAL,apcid DECIMAL,algcode DECIMAL,algisversioned
> SMALLINT,algtype INT,algcalcobjecttype INT,algclasspath VARCHAR,algcomment
> VARCHAR,algopendate DATE,algclosedate DATE,algentstatus INT,agrsbjcode
> DECIMAL,agrid DECIMAL,daosbjcode DECIMAL,daoid DECIMAL,ctpsbjcode
> DECIMAL,ctpid DECIMAL,algusefields VARCHAR) engine
> "org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine"
> [42121-175]
> at org.h2.message.DbException.getJdbcSQLException(DbExceptio
[jira] [Assigned] (IGNITE-4534) Implement offheap eviction policies based on page memory
[ https://issues.apache.org/jira/browse/IGNITE-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov reassigned IGNITE-4534: -- Assignee: Ivan Rakov > Implement offheap eviction policies based on page memory > > > Key: IGNITE-4534 > URL: https://issues.apache.org/jira/browse/IGNITE-4534 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Alexey Goncharuk >Assignee: Ivan Rakov > Fix For: 2.0 > > > Since the internal structure of offheap storage has changed, we need to > re-implement Fifo, Lru and Sorted eviction policies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.
[ https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2216: Fix Version/s: (was: 2.0) 1.9 > Duplicate field names with aliases do not work in queries. > -- > > Key: IGNITE-2216 > URL: https://issues.apache.org/jira/browse/IGNITE-2216 > Project: Ignite > Issue Type: Bug > Components: cache, SQL >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Sergey Kalashnikov > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-481) Add tests for Metrics to the file system tests infrastructure
[ https://issues.apache.org/jira/browse/IGNITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-481: --- Fix Version/s: (was: 2.0) 1.9 > Add tests for Metrics to the file system tests infrastructure > - > > Key: IGNITE-481 > URL: https://issues.apache.org/jira/browse/IGNITE-481 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky >Priority: Minor > Fix For: 1.9 > > > Need to add tests for org.apache.ignite.igfs.IgfsMetrics to the filesystem > tests. > See org.apache.ignite.IgniteFileSystem#metrics , > org.apache.ignite.IgniteFileSystem#resetMetrics . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4645) Best effort to avoid extra copying in binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4645: Fix Version/s: (was: 2.0) 1.9 > Best effort to avoid extra copying in binary marshaller > --- > > Key: IGNITE-4645 > URL: https://issues.apache.org/jira/browse/IGNITE-4645 > Project: Ignite > Issue Type: Bug > Components: binary >Reporter: Yakov Zhdanov >Assignee: Igor Seliverstov > Fix For: 1.9 > > > If we marshal a class that contain only primitives then we can predict the > final byte array size and avoid copies to grow array and final trimming. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4645) Best effort to avoid extra copying in binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865300#comment-15865300
]
Vladimir Ozerov commented on IGNITE-4645:
-
[~gvvinblade],
Currently you perform 2 {{ConcurentHashMap}} lookups to {{descByCls}} on
regular hot path. Earlier there was only 1. This is what I meant.
> Best effort to avoid extra copying in binary marshaller
> ---
>
> Key: IGNITE-4645
> URL: https://issues.apache.org/jira/browse/IGNITE-4645
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Fix For: 1.9
>
>
> If we marshal a class that contain only primitives then we can predict the
> final byte array size and avoid copies to grow array and final trimming.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-2552) Eviction policy must consider either max size or max entries count
[ https://issues.apache.org/jira/browse/IGNITE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-2552: Assignee: Alexey Kuznetsov > Eviction policy must consider either max size or max entries count > -- > > Key: IGNITE-2552 > URL: https://issues.apache.org/jira/browse/IGNITE-2552 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.0 > > > Presently both max size and max entries number are considered by eviction > policy logic even if the only one is set by user explicitly. > This behavior must be reworked in a way that if one of the parameters is set > explicitly then only it will be used by eviction policy while the other one > will be ignored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4162) Step-by-step guidance on how to start and use Ignite cluster with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865118#comment-15865118 ] Denis Magda commented on IGNITE-4162: - Kubernetes IP finder documentation is completed: https://apacheignite-mix.readme.io/docs/kubernetes-discovery Kubernetes getting started guide is still in progress: https://apacheignite.readme.io/docs/kubernetes-deployment > Step-by-step guidance on how to start and use Ignite cluster with Kubernetes > > > Key: IGNITE-4162 > URL: https://issues.apache.org/jira/browse/IGNITE-4162 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > > At the end, we have to prepare a step-by-step guidance on how to: > - configure, launch and scale Ignite cluster. > - how to connect and work with this cluster from applications running inside > and outside of Kubernetes. > Refer to existed guidance prepared for other products: > https://github.com/kubernetes/kubernetes/tree/master/examples/storage/cassandra > https://github.com/pires/hazelcast-kubernetes > https://www.mongodb.com/blog/post/running-mongodb-as-a-microservice-with-docker-and-kubernetes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4539) RocketMQ data streamer
[ https://issues.apache.org/jira/browse/IGNITE-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864865#comment-15864865 ] Denis Magda commented on IGNITE-4539: - [~roman_s], how close are you to finish the development? The community plans to announce the code freeze on Feb 17 this week. > RocketMQ data streamer > -- > > Key: IGNITE-4539 > URL: https://issues.apache.org/jira/browse/IGNITE-4539 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Roman Shtykh >Assignee: Roman Shtykh > Fix For: 1.9 > > > Streamer for RocketMQ (https://github.com/rocketmq) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4162) Step-by-step guidance on how to start and use Ignite cluster with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-4162: --- Assignee: Denis Magda > Step-by-step guidance on how to start and use Ignite cluster with Kubernetes > > > Key: IGNITE-4162 > URL: https://issues.apache.org/jira/browse/IGNITE-4162 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > > At the end, we have to prepare a step-by-step guidance on how to: > - configure, launch and scale Ignite cluster. > - how to connect and work with this cluster from applications running inside > and outside of Kubernetes. > Refer to existed guidance prepared for other products: > https://github.com/kubernetes/kubernetes/tree/master/examples/storage/cassandra > https://github.com/pires/hazelcast-kubernetes > https://www.mongodb.com/blog/post/running-mongodb-as-a-microservice-with-docker-and-kubernetes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4162) Step-by-step guidance on how to start and use Ignite cluster with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864862#comment-15864862 ] Denis Magda commented on IGNITE-4162: - Need to create a documentation for Kubernetes IP finder on readme.io integration site. After that a getting started similar to Mesos, YARN, AWS deployment has to be prepared on the main readme.io site. > Step-by-step guidance on how to start and use Ignite cluster with Kubernetes > > > Key: IGNITE-4162 > URL: https://issues.apache.org/jira/browse/IGNITE-4162 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > Fix For: 1.9 > > > At the end, we have to prepare a step-by-step guidance on how to: > - configure, launch and scale Ignite cluster. > - how to connect and work with this cluster from applications running inside > and outside of Kubernetes. > Refer to existed guidance prepared for other products: > https://github.com/kubernetes/kubernetes/tree/master/examples/storage/cassandra > https://github.com/pires/hazelcast-kubernetes > https://www.mongodb.com/blog/post/running-mongodb-as-a-microservice-with-docker-and-kubernetes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4159) Cloud Native Deployment of Apache Ignite using Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4159: Fix Version/s: (was: 1.9) 2.0 > Cloud Native Deployment of Apache Ignite using Kubernetes > - > > Key: IGNITE-4159 > URL: https://issues.apache.org/jira/browse/IGNITE-4159 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 2.0 > > > Kubernetes is an open-source system for automating deployment, scaling, and > management of containerized applications. > http://kubernetes.io > Apache Ignite perfectly fits the concepts implemented in Kubernetes which may > greatly simplify and automate the maintenance and scaling of Apache Ignite > clusters running under the supervision of Kubernetes. > Ignite won't be the first distributed storage that supports Kubernetes. There > are already a number of existed ones that being used: > https://github.com/kubernetes/kubernetes/tree/master/examples/storage/cassandra > https://github.com/pires/hazelcast-kubernetes > https://www.mongodb.com/blog/post/running-mongodb-as-a-microservice-with-docker-and-kubernetes > This is an umbrella ticket that incorporates all the works that have to be > done before Ignite officially claims that it can be launched under Kubernetes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-4160) Discovery SPI Implementation for Ignite Kubernetes Pods
[ https://issues.apache.org/jira/browse/IGNITE-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-4160. - Resolution: Fixed Merged to master and 1.9. > Discovery SPI Implementation for Ignite Kubernetes Pods > --- > > Key: IGNITE-4160 > URL: https://issues.apache.org/jira/browse/IGNITE-4160 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > > There is no way to set a predefined internal IP address and port number for a > Kubernetes pod. Kubernetes manages this on its own by assigning an IP address > dynamically. > In order to assemble an Ignite cluster under Kubernetes supervision we have > to provide a Kubernetes specific implementation of discovery SPI. The > discovery implementation has to use Kubernetes API to locate private IP > addresses of all the Ignite pods (nodes) started so far and use these IP > addresses at the join phase. > Refer to an exemplary implementation of a discovery component in other > distributed storage: > https://github.com/pires/hazelcast-kubernetes#hazelcast-discovery-source -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-4160) Discovery SPI Implementation for Ignite Kubernetes Pods
[ https://issues.apache.org/jira/browse/IGNITE-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-4160. --- > Discovery SPI Implementation for Ignite Kubernetes Pods > --- > > Key: IGNITE-4160 > URL: https://issues.apache.org/jira/browse/IGNITE-4160 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > > There is no way to set a predefined internal IP address and port number for a > Kubernetes pod. Kubernetes manages this on its own by assigning an IP address > dynamically. > In order to assemble an Ignite cluster under Kubernetes supervision we have > to provide a Kubernetes specific implementation of discovery SPI. The > discovery implementation has to use Kubernetes API to locate private IP > addresses of all the Ignite pods (nodes) started so far and use these IP > addresses at the join phase. > Refer to an exemplary implementation of a discovery component in other > distributed storage: > https://github.com/pires/hazelcast-kubernetes#hazelcast-discovery-source -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4162) Step-by-step guidance on how to start and use Ignite cluster with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4162: Fix Version/s: (was: 2.0) 1.9 > Step-by-step guidance on how to start and use Ignite cluster with Kubernetes > > > Key: IGNITE-4162 > URL: https://issues.apache.org/jira/browse/IGNITE-4162 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > Fix For: 1.9 > > > At the end, we have to prepare a step-by-step guidance on how to: > - configure, launch and scale Ignite cluster. > - how to connect and work with this cluster from applications running inside > and outside of Kubernetes. > Refer to existed guidance prepared for other products: > https://github.com/kubernetes/kubernetes/tree/master/examples/storage/cassandra > https://github.com/pires/hazelcast-kubernetes > https://www.mongodb.com/blog/post/running-mongodb-as-a-microservice-with-docker-and-kubernetes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4160) Discovery SPI Implementation for Ignite Kubernetes Pods
[ https://issues.apache.org/jira/browse/IGNITE-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4160: Fix Version/s: (was: 2.0) 1.9 > Discovery SPI Implementation for Ignite Kubernetes Pods > --- > > Key: IGNITE-4160 > URL: https://issues.apache.org/jira/browse/IGNITE-4160 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > > There is no way to set a predefined internal IP address and port number for a > Kubernetes pod. Kubernetes manages this on its own by assigning an IP address > dynamically. > In order to assemble an Ignite cluster under Kubernetes supervision we have > to provide a Kubernetes specific implementation of discovery SPI. The > discovery implementation has to use Kubernetes API to locate private IP > addresses of all the Ignite pods (nodes) started so far and use these IP > addresses at the join phase. > Refer to an exemplary implementation of a discovery component in other > distributed storage: > https://github.com/pires/hazelcast-kubernetes#hazelcast-discovery-source -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4526) Add Spark Shared RDD examples
[ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4526: Priority: Critical (was: Major) > Add Spark Shared RDD examples > - > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task >Affects Versions: 1.8 >Reporter: Denis Magda >Assignee: Manish Mishra >Priority: Critical > Fix For: 1.9 > > Attachments: profiles.png, SuiteSnapShot.png, > Teamcity_Runn_Java8_example > > > Spark Shared RDD functionality doesn't have its own examples. We need to add > an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the > RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. > Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one > of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid > different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4526) Add Spark Shared RDD examples
[ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4526: Affects Version/s: 1.8 > Add Spark Shared RDD examples > - > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task >Affects Versions: 1.8 >Reporter: Denis Magda >Assignee: Manish Mishra > Fix For: 1.9 > > Attachments: profiles.png, SuiteSnapShot.png, > Teamcity_Runn_Java8_example > > > Spark Shared RDD functionality doesn't have its own examples. We need to add > an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the > RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. > Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one > of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid > different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4526) Add Spark Shared RDD examples
[ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-4526: --- Assignee: Manish Mishra (was: Denis Magda) > Add Spark Shared RDD examples > - > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Assignee: Manish Mishra > Fix For: 1.9 > > Attachments: profiles.png, SuiteSnapShot.png, > Teamcity_Runn_Java8_example > > > Spark Shared RDD functionality doesn't have its own examples. We need to add > an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the > RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. > Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one > of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid > different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4526) Add Spark Shared RDD examples
[ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864549#comment-15864549 ] Denis Magda commented on IGNITE-4526: - [~manish__mishra], thanks a lot. I'll take a look at your changes tomorrow. I do believe we will be able to merge them till Feb 17 (Apache Ignite 1.9 code freeze). > Add Spark Shared RDD examples > - > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Assignee: Manish Mishra > Fix For: 1.9 > > Attachments: profiles.png, SuiteSnapShot.png, > Teamcity_Runn_Java8_example > > > Spark Shared RDD functionality doesn't have its own examples. We need to add > an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the > RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. > Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one > of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid > different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4526) Add Spark Shared RDD examples
[ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-4526: --- Assignee: Denis Magda (was: Manish Mishra) > Add Spark Shared RDD examples > - > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > Attachments: profiles.png, SuiteSnapShot.png, > Teamcity_Runn_Java8_example > > > Spark Shared RDD functionality doesn't have its own examples. We need to add > an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the > RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. > Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one > of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid > different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4526) Add Spark Shared RDD examples
[ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-4526: --- Assignee: Manish Mishra (was: Denis Magda) > Add Spark Shared RDD examples > - > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Assignee: Manish Mishra > Fix For: 1.9 > > Attachments: profiles.png, SuiteSnapShot.png, > Teamcity_Runn_Java8_example > > > Spark Shared RDD functionality doesn't have its own examples. We need to add > an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the > RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. > Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one > of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid > different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4526) Add Spark Shared RDD examples
[ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-4526: --- Assignee: Denis Magda (was: Manish Mishra) > Add Spark Shared RDD examples > - > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > Attachments: profiles.png, SuiteSnapShot.png, > Teamcity_Runn_Java8_example > > > Spark Shared RDD functionality doesn't have its own examples. We need to add > an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the > RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. > Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one > of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid > different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3315) CPP: Add documentation for ContinuousQuery API
[ https://issues.apache.org/jira/browse/IGNITE-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864353#comment-15864353 ] Denis Magda commented on IGNITE-3315: - [~avinogradov], it's a documentation related task that can be finalized after Feb 17. In any case it will be completed before 1.9 binaries go public. > CPP: Add documentation for ContinuousQuery API > -- > > Key: IGNITE-3315 > URL: https://issues.apache.org/jira/browse/IGNITE-3315 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.6 >Reporter: Igor Sapego >Assignee: Prachi Garg >Priority: Minor > Labels: cpp > Fix For: 1.9 > > > We are going to add CountinuousQuery API to Ignite C++ with IGNITE-1443 so we > also need to add documentation section to readme.io on this topic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4619) .NET: TransactionScope documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-4619:
---
Assignee: Prachi Garg (was: Pavel Tupitsyn)
> .NET: TransactionScope documentation and example
>
>
> Key: IGNITE-4619
> URL: https://issues.apache.org/jira/browse/IGNITE-4619
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Prachi Garg
> Labels: .NET
> Fix For: 1.9
>
>
> Create documentation and example for {{TransactionScope}} support
> (IGNITE-3430).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4619) .NET: TransactionScope documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864350#comment-15864350
]
Denis Magda commented on IGNITE-4619:
-
[~avinogradov], this ticket is completed from the engineering standpoint. We're
free to release it in 1.9.
[~pgarg], please review the doc:
https://apacheignite-net.readme.io/docs/transactionscope-api
> .NET: TransactionScope documentation and example
>
>
> Key: IGNITE-4619
> URL: https://issues.apache.org/jira/browse/IGNITE-4619
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 1.9
>
>
> Create documentation and example for {{TransactionScope}} support
> (IGNITE-3430).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4645) Best effort to avoid extra copying in binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864058#comment-15864058
]
Igor Seliverstov commented on IGNITE-4645:
--
[~vozerov], answering on your message:
1) It's done for us inside {{BinaryContext#descriptorForClass}} method, it
cashes resolved class descriptors in {{descByCls}} field.
All the other issues are fixed
> Best effort to avoid extra copying in binary marshaller
> ---
>
> Key: IGNITE-4645
> URL: https://issues.apache.org/jira/browse/IGNITE-4645
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Fix For: 2.0
>
>
> If we marshal a class that contain only primitives then we can predict the
> final byte array size and avoid copies to grow array and final trimming.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4003) Slow or faulty client can stall the whole cluster.
[
https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864043#comment-15864043
]
Andrey Gura commented on IGNITE-4003:
-
Actually my changes broke client reconnect tests. It was shaded because in my
branch shmem is switched on by default. But if shmem disabled tests fail with
100% probability. Investigation in progress.
> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 1.9
>
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside.
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying
> to establish outgoing connection to the client, but fail as Docker subnet is
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may
> have left the grid or TCP connection cannot be established due to firewall
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714,
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0,
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707,
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da,
> isClient=true], topic=T4 [topic=TOPIC_CACHE,
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc,
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db,
> data=null, futId=null], policy=2]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3476)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:548)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:207)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.processForceKeyResponse(GridDhtPreloader.java:636)
[jira] [Updated] (IGNITE-4003) Slow or faulty client can stall the whole cluster.
[
https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-4003:
Fix Version/s: (was: 2.0)
1.9
> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 1.9
>
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside.
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying
> to establish outgoing connection to the client, but fail as Docker subnet is
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may
> have left the grid or TCP connection cannot be established due to firewall
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714,
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0,
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707,
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da,
> isClient=true], topic=T4 [topic=TOPIC_CACHE,
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc,
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db,
> data=null, futId=null], policy=2]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3476)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:548)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:207)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.processForceKeyResponse(GridDhtPreloader.java:636)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.access$1000(GridDhtPreloader.java:81)
> [ignite-core-1.5.23.jar:1.5
[jira] [Created] (IGNITE-4693) Add possibility to wrap Java plugin exceptions to .NET plugin exceptions
Pavel Tupitsyn created IGNITE-4693:
--
Summary: Add possibility to wrap Java plugin exceptions to .NET
plugin exceptions
Key: IGNITE-4693
URL: https://issues.apache.org/jira/browse/IGNITE-4693
Project: Ignite
Issue Type: Sub-task
Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.0
Plugins with Java part can throw custom Java exceptions, which are mapped to
{{IgniteException}}. We should add a way for plugin authors to map their custom
Java exceptions to corresponding .NET exceptions.
This can be done by adding {{IPluginProvider.ConvertException}} method and
iterating over plugins in {{ExceptionUtils.GetException}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-4692) .NET: Add ClassName and Message to JavaException
[
https://issues.apache.org/jira/browse/IGNITE-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-4692:
---
Comment: was deleted
(was: FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.)
> .NET: Add ClassName and Message to JavaException
>
>
> Key: IGNITE-4692
> URL: https://issues.apache.org/jira/browse/IGNITE-4692
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> See {{ExceptionUtils.GetException}}: we construct {{JavaException}} with
> stack trace only. If the user wants to map some custom Java exception, they
> have to parse stack trace.
> We can easily add {{JavaException.ClassName}} and {{JavaException.Message}}
> properties for easier analysis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-4692) .NET: Add ClassName and Message to JavaException
[
https://issues.apache.org/jira/browse/IGNITE-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-4692.
Resolution: Implemented
> .NET: Add ClassName and Message to JavaException
>
>
> Key: IGNITE-4692
> URL: https://issues.apache.org/jira/browse/IGNITE-4692
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> See {{ExceptionUtils.GetException}}: we construct {{JavaException}} with
> stack trace only. If the user wants to map some custom Java exception, they
> have to parse stack trace.
> We can easily add {{JavaException.ClassName}} and {{JavaException.Message}}
> properties for easier analysis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4692) .NET: Add ClassName and Message to JavaException
[
https://issues.apache.org/jira/browse/IGNITE-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863950#comment-15863950
]
Pavel Tupitsyn commented on IGNITE-4692:
Done in ignite-2.0
> .NET: Add ClassName and Message to JavaException
>
>
> Key: IGNITE-4692
> URL: https://issues.apache.org/jira/browse/IGNITE-4692
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> See {{ExceptionUtils.GetException}}: we construct {{JavaException}} with
> stack trace only. If the user wants to map some custom Java exception, they
> have to parse stack trace.
> We can easily add {{JavaException.ClassName}} and {{JavaException.Message}}
> properties for easier analysis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-3315) CPP: Add documentation for ContinuousQuery API
[ https://issues.apache.org/jira/browse/IGNITE-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-3315: Fix Version/s: (was: 2.0) 1.9 > CPP: Add documentation for ContinuousQuery API > -- > > Key: IGNITE-3315 > URL: https://issues.apache.org/jira/browse/IGNITE-3315 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.6 >Reporter: Igor Sapego >Assignee: Prachi Garg >Priority: Minor > Labels: cpp > Fix For: 1.9 > > > We are going to add CountinuousQuery API to Ignite C++ with IGNITE-1443 so we > also need to add documentation section to readme.io on this topic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4619) .NET: TransactionScope documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-4619:
---
Fix Version/s: (was: 2.0)
1.9
> .NET: TransactionScope documentation and example
>
>
> Key: IGNITE-4619
> URL: https://issues.apache.org/jira/browse/IGNITE-4619
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 1.9
>
>
> Create documentation and example for {{TransactionScope}} support
> (IGNITE-3430).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4620) CPP: Add documentation for DML
[ https://issues.apache.org/jira/browse/IGNITE-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-4620: Fix Version/s: (was: 2.0) 1.9 > CPP: Add documentation for DML > -- > > Key: IGNITE-4620 > URL: https://issues.apache.org/jira/browse/IGNITE-4620 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.8 >Reporter: Igor Sapego > Labels: cpp, documentation > Fix For: 1.9 > > > We need to add documentation for DML support once its implemented in C++ > client. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4617) CPP: Implement Field-access methods for binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-4617:
Fix Version/s: (was: 2.0)
1.9
> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 1.9
>
>
> Currently we have very limited implementation of binary objects that does not
> provide access to fields of the binary object. At least such methods as
> {{HasField}} and {{GetField}} should be implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4302) Exchange binary metadata with discovery custom messages instead of system cache
[ https://issues.apache.org/jira/browse/IGNITE-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863927#comment-15863927 ] Sergey Chugunov commented on IGNITE-4302: - Created test for case of constant flow of updates to the same binary type on constantly changing topology. Identified two issues with it: # Memory leak through *MetadataUpdateProposedMessage* which get stored in *GridEventStorageManager* but shouldn't. # Lost updates to metadata schemas. I suspect logic in *MetadataUpdateProposedListener* to be a root cause, getting closer to fix the issue. > Exchange binary metadata with discovery custom messages instead of system > cache > --- > > Key: IGNITE-4302 > URL: https://issues.apache.org/jira/browse/IGNITE-4302 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov > Fix For: 2.0 > > > h4. Notes > See [IGNITE-4157|https://issues.apache.org/jira/browse/IGNITE-4157] for more > details about context. > h4. Acceptance Criteria > # Binary metadata cache is deleted. > # Binary metadata exchange is performed using *DiscoveryCustomMessage* events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4624) ScanQuery shows poor performance.
[ https://issues.apache.org/jira/browse/IGNITE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4624: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > ScanQuery shows poor performance. > - > > Key: IGNITE-4624 > URL: https://issues.apache.org/jira/browse/IGNITE-4624 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.8 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Fix For: 2.0 > > Attachments: > Change_keyIterator_to_entryIterator_for_local_scan_squery.patch, Demo.java > > > I've found that ScanQuery use cache KeySet iterator which make cache > peek\entry calls for getting value. > It is look like we can avoid this calls by using EntrySet iterator for > iterating over local partitions. > Start point is GridCacheQueryManager.onheapIterator(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4620) CPP: Add documentation for DML
[ https://issues.apache.org/jira/browse/IGNITE-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4620: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > CPP: Add documentation for DML > -- > > Key: IGNITE-4620 > URL: https://issues.apache.org/jira/browse/IGNITE-4620 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.8 >Reporter: Igor Sapego > Labels: cpp, documentation > Fix For: 2.0 > > > We need to add documentation for DML support once its implemented in C++ > client. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-481) Add tests for Metrics to the file system tests infrastructure
[ https://issues.apache.org/jira/browse/IGNITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-481: Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Add tests for Metrics to the file system tests infrastructure > - > > Key: IGNITE-481 > URL: https://issues.apache.org/jira/browse/IGNITE-481 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky >Priority: Minor > Fix For: 2.0 > > > Need to add tests for org.apache.ignite.igfs.IgfsMetrics to the filesystem > tests. > See org.apache.ignite.IgniteFileSystem#metrics , > org.apache.ignite.IgniteFileSystem#resetMetrics . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-3542) IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.
[ https://issues.apache.org/jira/browse/IGNITE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-3542: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try. > - > > Key: IGNITE-3542 > URL: https://issues.apache.org/jira/browse/IGNITE-3542 > Project: Ignite > Issue Type: Bug > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Minor > Fix For: 2.0 > > > If integrity check failed, it means that some concurrent file system update > occurred. We should always perform re-try in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4501) Improvement of connection in a cluster of new node
[
https://issues.apache.org/jira/browse/IGNITE-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4501:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
> Issue Type: Improvement
> Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F.
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A,
> etc.
> If some node leaves topology, adjacent nodes must reconnect.
> If nodes A, B, C are in same physical place, nodes D, E, F are in other
> place, and places lost connect each other, we will have many ways of
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where
> n -- number of nodes).
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet
> : other nodes). We will use it when we connect a new node.
> * [dev list
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding
> public static final constant to TcpDiscoverySpi.
> # Alter
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
> to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs
> are equal then we should compare nodes' IDs. This way we have consistent
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This
> can be postponed and implemented after we have other points done.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4003) Slow or faulty client can stall the whole cluster.
[
https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4003:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.0
>
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside.
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying
> to establish outgoing connection to the client, but fail as Docker subnet is
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may
> have left the grid or TCP connection cannot be established due to firewall
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714,
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0,
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707,
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da,
> isClient=true], topic=T4 [topic=TOPIC_CACHE,
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc,
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db,
> data=null, futId=null], policy=2]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3476)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:548)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:207)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.processForceKeyResponse(GridDhtPreloader.java:636)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distri
[jira] [Updated] (IGNITE-4472) Web Console: Implement usage tracing
[ https://issues.apache.org/jira/browse/IGNITE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4472: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Web Console: Implement usage tracing > > > Key: IGNITE-4472 > URL: https://issues.apache.org/jira/browse/IGNITE-4472 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Shabalin >Assignee: Dmitriy Shabalin > Fix For: 2.0 > > > We need to track some kind of "activity scores" for users. > Activities: > # Configuration > # SQL > # Demo > And show that score on admin panel. > May be this could be implemented by some library. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-1338) SQL engine doesn't convert query fields name in upper case before using
[
https://issues.apache.org/jira/browse/IGNITE-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1338:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> SQL engine doesn't convert query fields name in upper case before using
> ---
>
> Key: IGNITE-1338
> URL: https://issues.apache.org/jira/browse/IGNITE-1338
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Sergey Kalashnikov
>Priority: Trivial
> Fix For: 2.0
>
> Attachments: test-cluster-2.xml
>
>
> Node can not be started if query fields name written in *lower case* and key
> fields with the *same* fields in *upper case* in cache type metadata.
> Please use attached configuration file for reproducing.
> {code}
> [14:30:28,526][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> class org.apache.ignite.IgniteCheckedException: Failed to register query
> type: TypeDescriptor [name=org.apache.ignite.Comalgorithm,
> fields={APCSBJCODE=class java.math.BigDecimal, APCID=class
> java.math.BigDecimal, AGRSBJCODE=class java.math.BigDecimal, AGRID=class
> java.math.BigDecimal, DAOSBJCODE=class java.math.BigDecimal, DAOID=class
> java.math.BigDecimal, CTPSBJCODE=class java.math.BigDecimal, CTPID=class
> java.math.BigDecimal, apcsbjcode=class java.math.BigDecimal, apcid=class
> java.math.BigDecimal, algcode=class java.math.BigDecimal,
> algisversioned=class java.lang.Short, algtype=class java.lang.Integer,
> algcalcobjecttype=class java.lang.Integer, algclasspath=class
> java.lang.String, algcomment=class java.lang.String, algopendate=class
> java.sql.Date, algclosedate=class java.sql.Date, algentstatus=class
> java.lang.Integer, agrsbjcode=class java.math.BigDecimal, agrid=class
> java.math.BigDecimal, daosbjcode=class java.math.BigDecimal, daoid=class
> java.math.BigDecimal, ctpsbjcode=class java.math.BigDecimal, ctpid=class
> java.math.BigDecimal, algusefields=class java.lang.String},
> indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED],
> FK3COMALGORITHM=IndexDescriptor [type=SORTED],
> FK4COMALGORITHM=IndexDescriptor [type=SORTED],
> SQL050208183448780=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
> keyCls=class java.lang.Object, valCls=class java.lang.Object,
> valTextIdx=false, registered=false]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1058)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:194)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:292)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1048)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:820)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:963)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546)
> at org.apache.ignite.Ignition.start(Ignition.java:346)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбца "APCSBJCODE"
> Duplicate column name "APCSBJCODE"; SQL statement:
> CREATE TABLE "cache2".org_apache_ignite_Comalgorithm (_key OTHER NOT
> NULL,_val OTHER,APCSBJCODE DECIMAL,APCID DECIMAL,AGRSBJCODE DECIMAL,AGRID
> DECIMAL,DAOSBJCODE DECIMAL,DAOID DECIMAL,CTPSBJCODE DECIMAL,CTPID
> DECIMAL,apcsbjcode DECIMAL,apcid DECIMAL,algcode DECIMAL,algisversioned
> SMALLINT,algtype INT,algcalcobjecttype INT,algclasspath VARCHAR,algcomment
> VARCHAR,algopendate DATE,algclosedate DATE,algentstatus INT,agrsbjcode
> DECIMAL,agrid DECIMAL,daosbjcode DECIMAL,daoid DECIMAL,ctpsbjcode
> DECIMAL,ctpid DECIMAL,algusefields VARCHAR) engine
> "org.apache.ignite.internal.processors.query.h2.opt.GridH2
[jira] [Updated] (IGNITE-4585) Support CLEAR command with REST
[ https://issues.apache.org/jira/browse/IGNITE-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4585: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Support CLEAR command with REST > --- > > Key: IGNITE-4585 > URL: https://issues.apache.org/jira/browse/IGNITE-4585 > Project: Ignite > Issue Type: Improvement > Components: rest >Affects Versions: 1.8 >Reporter: Sam >Priority: Minor > Fix For: 2.0 > > > CLEAR command is not supported with REST Service, but DESTROY is supported. > CLEAR is more better option than DESTROY in many cases. > http://apache-ignite-users.70518.x6.nabble.com/REST-Service-for-CLEAR-td10150.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4453) Web console: On click by any dropdown page showed as changed.
[ https://issues.apache.org/jira/browse/IGNITE-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4453: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Web console: On click by any dropdown page showed as changed. > - > > Key: IGNITE-4453 > URL: https://issues.apache.org/jira/browse/IGNITE-4453 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.9 >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4692) .NET: Add ClassName and Message to JavaException
[
https://issues.apache.org/jira/browse/IGNITE-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4692:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> .NET: Add ClassName and Message to JavaException
>
>
> Key: IGNITE-4692
> URL: https://issues.apache.org/jira/browse/IGNITE-4692
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> See {{ExceptionUtils.GetException}}: we construct {{JavaException}} with
> stack trace only. If the user wants to map some custom Java exception, they
> have to parse stack trace.
> We can easily add {{JavaException.ClassName}} and {{JavaException.Message}}
> properties for easier analysis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4395) Implement communication backpressure per policy - SYSTEM or PUBLIC
[ https://issues.apache.org/jira/browse/IGNITE-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4395: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Implement communication backpressure per policy - SYSTEM or PUBLIC > -- > > Key: IGNITE-4395 > URL: https://issues.apache.org/jira/browse/IGNITE-4395 > Project: Ignite > Issue Type: Improvement > Components: cache, compute >Affects Versions: 1.7 >Reporter: Dmitry Karachentsev >Assignee: Dmitry Karachentsev > Fix For: 2.0 > > > 1) Start two data nodes with some cache. > 2) From one node in async mode post some big number of jobs to another. That > jobs do some cache operations. > 3) Grid hangs almost immediately and all threads are sleeping except public > ones, they are waiting for response. > This happens because all cache and job messages are queued on communication > and limited with default number (1024). It looks like jobs are waiting for > cache responses that could not be received due to this limit. > Proper solution here is to have communication backpressure per policy - > SYSTEM or PUBLIC, but not single point as it is now. It could be achieved > with having two queues per communication session or (which looks a bit > easier to implement) to have separate connections. > [PR#1331|https://github.com/apache/ignite/pull/1331] with test that leads to > grid hang. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4618) CPP: Do not start JVM if it is already started
[ https://issues.apache.org/jira/browse/IGNITE-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4618: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > CPP: Do not start JVM if it is already started > -- > > Key: IGNITE-4618 > URL: https://issues.apache.org/jira/browse/IGNITE-4618 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.8 >Reporter: Vladimir Ozerov > Fix For: 2.0 > > > *Problem* > Consider the following scenario: > 1) User's app started JVM in the process somehow. > 2) User tries to start the node. > 3) Result: exception. > *Solution* > We need to check if JVM is already started. If yes - then try re-using. Note > that we are likely to fail at this point because user might forgot to pass > proper Ignite classpath. In this case we must throw extremely sensible > exception, so that user understand how to fix the problem right away. > E.g.: "Failed to start Ignite node with already started JVM due to invalid > classpath; please add the following JARs to the classpath: [PATH TO > IGNITE_HOME JARS]". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4641) Refresh client attributes during reconnect
[
https://issues.apache.org/jira/browse/IGNITE-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4641:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> Refresh client attributes during reconnect
> --
>
> Key: IGNITE-4641
> URL: https://issues.apache.org/jira/browse/IGNITE-4641
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> Currently, when client disconnects and reconnects, it is forced to do that
> with the exact same set of attributes. However, there can be a component that
> wants to update attribute(s) in {{onDisconnected}} method, so that node
> reconnects with new attributes. To make sure this happens we need to refresh
> attributes before reconnecting. Most likely this should happen in
> {{TcpDiscoveryNode.clientReconnectNode()}} method which should acquire
> attributes via {{GridKernalContext.nodeAttributes()}}.
> Typical use case is a security token that can expire. Security processor
> implementation may want to refresh the token in case of disconnect, but this
> is not possible now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4677) Incorrect connectable node detection in router mode for Java thin client
[
https://issues.apache.org/jira/browse/IGNITE-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4677:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> Incorrect connectable node detection in router mode for Java thin client
>
>
> Key: IGNITE-4677
> URL: https://issues.apache.org/jira/browse/IGNITE-4677
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: 2.0
>
>
> * In case of connect using Java client to localhost: in router mode all
> nodes listen same localhost: on other hosts will be marked as
> connectable.
> {code}
> boolean noAttrsAndMetrics = (metricsCache && attrCache) ||
> (node.attributes().isEmpty() && node.metrics() == null);
> boolean reachable = noAttrsAndMetrics || ...
> {code}
> * Under Windows org.apache.ignite.internal.util.IgniteUtils#allLocalIps
> return same mac: 00-00-00-00-00-00-00-E0 on different hosts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.
[ https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-2216: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Duplicate field names with aliases do not work in queries. > -- > > Key: IGNITE-2216 > URL: https://issues.apache.org/jira/browse/IGNITE-2216 > Project: Ignite > Issue Type: Bug > Components: cache, SQL >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Sergey Kalashnikov > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4497) CacheDefaultBinaryAffinityKeyMapper class has a wrong duplicate
[ https://issues.apache.org/jira/browse/IGNITE-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4497: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > CacheDefaultBinaryAffinityKeyMapper class has a wrong duplicate > --- > > Key: IGNITE-4497 > URL: https://issues.apache.org/jira/browse/IGNITE-4497 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.9 >Reporter: Vasiliy Sisko > Fix For: 2.0 > > > Two version of CacheDefaultBinaryAffinityKeyMapper exist. > org.apache.ignite.internal.processors.cache.binary.CacheDefaultBinaryAffinityKeyMapper > and > org.apache.ignite.internal.processors.cache.CacheDefaultBinaryAffinityKeyMapper > Version from binary project is not used in project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4668) Doesn't work "manual" yardsticks when ip of server/driver not equal ip of ethernet interface
[
https://issues.apache.org/jira/browse/IGNITE-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4668:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> Doesn't work "manual" yardsticks when ip of server/driver not equal ip of
> ethernet interface
> -
>
> Key: IGNITE-4668
> URL: https://issues.apache.org/jira/browse/IGNITE-4668
> Project: Ignite
> Issue Type: Bug
> Components: yardstick
>Affects Versions: 1.8
>Reporter: Ilya Suntsov
> Fix For: 2.0
>
>
> In scripts benchmark-manual-servers-start.sh we are checking:
> {noformat}
> for host in "${hosts[@]}";
> do
> if [ "${host}" == "localhost" ] || [ "${host}" == "127.0.0.1" ];
> then
> srv_num=$((1 + $srv_num))
> else
> ip=$(hostname --ip-address)
> host_name=$(hostname)
> if [ "${host}" == "${ip}" ] || [ "${host}" == "${host_name}"
> ]; then
> srv_num=$((1 + $srv_num))
> fi
> fi
> done
> {noformat}
> in case when ip address of real host interface that we set as server address
> not equal $(hostname --ip-address) servers doesn't start.
> I think we should collect all interfaces ip in array and check if ip from
> ${hosts[@]} (SERVER_HOSTS) equal one of them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-3315) CPP: Add documentation for ContinuousQuery API
[ https://issues.apache.org/jira/browse/IGNITE-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-3315: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > CPP: Add documentation for ContinuousQuery API > -- > > Key: IGNITE-3315 > URL: https://issues.apache.org/jira/browse/IGNITE-3315 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.6 >Reporter: Igor Sapego >Assignee: Prachi Garg >Priority: Minor > Labels: cpp > Fix For: 2.0 > > > We are going to add CountinuousQuery API to Ignite C++ with IGNITE-1443 so we > also need to add documentation section to readme.io on this topic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4617) CPP: Implement Field-access methods for binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4617:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.0
>
>
> Currently we have very limited implementation of binary objects that does not
> provide access to fields of the binary object. At least such methods as
> {{HasField}} and {{GetField}} should be implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4645) Best effort to avoid extra copying in binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4645: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Best effort to avoid extra copying in binary marshaller > --- > > Key: IGNITE-4645 > URL: https://issues.apache.org/jira/browse/IGNITE-4645 > Project: Ignite > Issue Type: Bug > Components: binary >Reporter: Yakov Zhdanov >Assignee: Igor Seliverstov > Fix For: 2.0 > > > If we marshal a class that contain only primitives then we can predict the > final byte array size and avoid copies to grow array and final trimming. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4686) Web Console: Add grouping by company on Admin panel screen
[ https://issues.apache.org/jira/browse/IGNITE-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4686: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Web Console: Add grouping by company on Admin panel screen > -- > > Key: IGNITE-4686 > URL: https://issues.apache.org/jira/browse/IGNITE-4686 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Affects Versions: 1.8 >Reporter: Alexey Kuznetsov >Assignee: Vica Abramova > Fix For: 2.0 > > > Add tab with table that will be grouped by company. > This table should has following features: > # Combo with list of companies to show only selected companies. > # Filter with company name (to quick filter). > # Columns with metrics should show totals for company. > # Instead of "Action" column show "Collapse/Expand" control. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4642) Support enforceJoinOrder flag for JDBC driver
[
https://issues.apache.org/jira/browse/IGNITE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4642:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> Support enforceJoinOrder flag for JDBC driver
> -
>
> Key: IGNITE-4642
> URL: https://issues.apache.org/jira/browse/IGNITE-4642
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc-driver
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
> Fix For: 2.0
>
>
> There is a useful {{enforceJoinOrder}} flag on {{SqlFieldsQuery}}, but it's
> not exposed on JDBC driver.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4226) Redis SET command should handle expirations
[ https://issues.apache.org/jira/browse/IGNITE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4226: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Redis SET command should handle expirations > --- > > Key: IGNITE-4226 > URL: https://issues.apache.org/jira/browse/IGNITE-4226 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.8 >Reporter: Roman Shtykh >Assignee: Roman Shtykh > Labels: redis > Fix For: 2.0 > > > Handling EX and PX parameters of SET command. > https://redis.io/commands/set -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4463) Web console: Send mail on password change from Profile page.
[ https://issues.apache.org/jira/browse/IGNITE-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4463: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Web console: Send mail on password change from Profile page. > > > Key: IGNITE-4463 > URL: https://issues.apache.org/jira/browse/IGNITE-4463 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Vasiliy Sisko > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4484) Call commit for read-only transactions.
[ https://issues.apache.org/jira/browse/IGNITE-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4484: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Call commit for read-only transactions. > --- > > Key: IGNITE-4484 > URL: https://issues.apache.org/jira/browse/IGNITE-4484 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.8 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 2.0 > > > IGNITE-3601 introduces a behavior, which is not compliant with tx isolation > semantics. > Read-only transaction doesn't throw optimisitc exception in case if entry > version were changes by other writing tx. > With the appearance of IGNITE-4285 this is no longer needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4619) .NET: TransactionScope documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4619:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> .NET: TransactionScope documentation and example
>
>
> Key: IGNITE-4619
> URL: https://issues.apache.org/jira/browse/IGNITE-4619
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Create documentation and example for {{TransactionScope}} support
> (IGNITE-3430).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4596) Web console: Add flag to disable demo cluster on agent.
[ https://issues.apache.org/jira/browse/IGNITE-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4596: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Web console: Add flag to disable demo cluster on agent. > --- > > Key: IGNITE-4596 > URL: https://issues.apache.org/jira/browse/IGNITE-4596 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4409) UUID fields of the key class deserialized in a wrong way on INSERT.
[
https://issues.apache.org/jira/browse/IGNITE-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4409:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> UUID fields of the key class deserialized in a wrong way on INSERT.
> ---
>
> Key: IGNITE-4409
> URL: https://issues.apache.org/jira/browse/IGNITE-4409
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Consider the following case. There is a class which is used as Key on C++
> side. It contains 3 fields: String, Timestamp and UUID. There is also a value
> of the type Integer. Record of the cache is being inserted with
> {{SqlFieldsQuery}}:
> {noformat}
> INSERT INTO Integer (str, ts, guid, _val) VALUES (?, ?, ?, ?)
> {noformat}
> String, Timestamp and Integer values serialized and desirialized just fine,
> but UUID value is passed further just like byte array of 17 bytes, first of
> which is 10 (UUID type header in Binary format), so later it gets converted
> here:
> {noformat}
> "main@1" prio=5 tid=0x1 nid=NA runnable
> java.lang.Thread.State: RUNNABLE
> at org.h2.value.ValueUuid.get(ValueUuid.java:68)
> at org.h2.value.Value.convertTo(Value.java:861)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.convert(DmlStatementsProcessor.java:637)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.rowToKeyValue(DmlStatementsProcessor.java:868)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:745)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:286)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:189)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1777)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1205)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:837)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inStreamOutObject(PlatformAbstractTarget.java:90)
> {noformat}
> Obviously enough, it gets deserialized wrong because of the header byte and
> as a result, we get wrong key instance in the cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4555) Make KeyValuePersistenceSettings configuration class Spring compatible
[
https://issues.apache.org/jira/browse/IGNITE-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4555:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> Make KeyValuePersistenceSettings configuration class Spring compatible
> --
>
> Key: IGNITE-4555
> URL: https://issues.apache.org/jira/browse/IGNITE-4555
> Project: Ignite
> Issue Type: Improvement
> Components: ignite-cassandra
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Igor Rudyak
> Fix For: 2.0
>
>
> Currently {{KeyValuePersistenceSettings}} uses a special XML format which is
> OK, but limits usability in following cases:
> * Spring is used for all other components of Ignite.
> * User wants to start dynamic cache and does not know persistence
> configuration in advance.
> We should add getter and setter methods to {{KeyValuePersistenceSettings}}
> and make it possible to create via Spring or directly in code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4664) Add lifecycle and injection support for TopologyValidator
[ https://issues.apache.org/jira/browse/IGNITE-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4664: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Add lifecycle and injection support for TopologyValidator > - > > Key: IGNITE-4664 > URL: https://issues.apache.org/jira/browse/IGNITE-4664 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 2.0 > > > It's might be useful to have TopologyValidator be aware of lifecycle and > provide resource injection support. > This'll help to implement more complex validation logic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-1495) Cache SQL query metadata index's fields have wrong register.
[ https://issues.apache.org/jira/browse/IGNITE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1495: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Cache SQL query metadata index's fields have wrong register. > > > Key: IGNITE-1495 > URL: https://issues.apache.org/jira/browse/IGNITE-1495 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: 1.5.0.final >Reporter: Vasiliy Sisko >Assignee: Sergey Kalashnikov > Fix For: 2.0 > > Attachments: #_IGNITE-1495_Test_for_index_s_fields.patch > > > Index's fields should have register how in table fields (In upper case). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4643) JdbcDatabaseMetadata.getIndexInfo() method not working
[
https://issues.apache.org/jira/browse/IGNITE-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4643:
-
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> JdbcDatabaseMetadata.getIndexInfo() method not working
> --
>
> Key: IGNITE-4643
> URL: https://issues.apache.org/jira/browse/IGNITE-4643
> Project: Ignite
> Issue Type: Bug
> Components: jdbc-driver
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 2.0
>
>
> {{JdbcDatabaseMetadata.getIndexInfo()}} method does not update metadata
> before creating result set. So if it's a first method invocation on this
> instance of {{JdbcDatabaseMetadata}}, it fails with NPE. Need to create tests
> and add {{updateMetaData()}} call in the beginning of the method.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4625) .NET: MixedClusterTest leaves Java-only node running
[ https://issues.apache.org/jira/browse/IGNITE-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4625: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > .NET: MixedClusterTest leaves Java-only node running > > > Key: IGNITE-4625 > URL: https://issues.apache.org/jira/browse/IGNITE-4625 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.0 > > > MixedClusterTest causes consequent tests to fail in some situations because > it leaves java-only "grid2" node running. Looks like ExecuteJavaTask does not > stop node properly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4657) Cache entry eviction can be broken if store throws exception
[ https://issues.apache.org/jira/browse/IGNITE-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4657: - Fix Version/s: (was: 1.9) 2.0 FixVersion changed to 2.0. In case issue can be done till Feb 17 please rollback this change. > Cache entry eviction can be broken if store throws exception > > > Key: IGNITE-4657 > URL: https://issues.apache.org/jira/browse/IGNITE-4657 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov > Fix For: 2.0 > > > Fix for IGNITE-4465 (commit 22b7e76c00a77a06388bcef869f29d1a572a306a) > introduced cache entry 'reservation' while entry is loaded from store. When > entry is reserved it is not evicted from cache. But currently 'reserved' > status is not cleared when cache store's methods throw exception, this should > be fixed in GridcCacheAdaptergetAllAsync0: catch exception thrown from > ctx.store().loadAll and do required cleanup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4661) Optimizations: optimize PagesList.removeDataPage
[
https://issues.apache.org/jira/browse/IGNITE-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863876#comment-15863876
]
Igor Seliverstov commented on IGNITE-4661:
--
Seems that deleting stripe in
{{org.apache.ignite.internal.processors.cache.database.freelist.PagesList#mergeNoNext}}
reduces performance. Is it really necessary? Also I've found that there is an
inconsistency between
{{org.apache.ignite.internal.processors.cache.database.freelist.PagesList#removeDataPage}}
method, which deletes the stripe in case it's empty and
{{org.apache.ignite.internal.processors.cache.database.freelist.PagesList#takeEmptyPage}}
which doesn't do that
> Optimizations: optimize PagesList.removeDataPage
>
>
> Key: IGNITE-4661
> URL: https://issues.apache.org/jira/browse/IGNITE-4661
> Project: Ignite
> Issue Type: Task
> Components: cache
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.0
>
>
> Optimization for new PageMemory approach (IGNITE-3477, branch ignite-3477).
> Currently PagesList.removeDataPage requires linear search by page ID, need
> check if it makes sense to change structure of PagesList's element from list
> to hash table.
> Here are links to proposed hash table alrorithm:
> http://codecapsule.com/2013/11/11/robin-hood-hashing
> http://codecapsule.com/2013/11/17/robin-hood-hashing-backward-shift-deletion/
> Note: with hash table approach 'take' from PagesList will require linear
> search, so we'll also need some heuristic to make it more optimal.
> For more details see:
> IgniteCacheOffheapManagerImpl.update -> FreeListImpl.insertDataRow,
> IgniteCacheOffheapManagerImpl.update -> FreeListImpl.removeDataRowByLink.
> To check result of optimization IgnitePutRandomValueSizeBenchmark can be used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-3330) CPP: Implement Cache::Invoke method.
[
https://issues.apache.org/jira/browse/IGNITE-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego resolved IGNITE-3330.
-
Resolution: Fixed
Implemented under IGNITE-1680
> CPP: Implement Cache::Invoke method.
>
>
> Key: IGNITE-3330
> URL: https://issues.apache.org/jira/browse/IGNITE-3330
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.0
>
>
> Implement {{Cache::Invoke}} method for the Ignite C++.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-4692) .NET: Add ClassName and Message to JavaException
Pavel Tupitsyn created IGNITE-4692:
--
Summary: .NET: Add ClassName and Message to JavaException
Key: IGNITE-4692
URL: https://issues.apache.org/jira/browse/IGNITE-4692
Project: Ignite
Issue Type: Improvement
Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 1.9
See {{ExceptionUtils.GetException}}: we construct {{JavaException}} with stack
trace only. If the user wants to map some custom Java exception, they have to
parse stack trace.
We can easily add {{JavaException.ClassName}} and {{JavaException.Message}}
properties for easier analysis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4673) Object array element type is written as a user type
[
https://issues.apache.org/jira/browse/IGNITE-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859318#comment-15859318
]
Taras Ledkov edited comment on IGNITE-4673 at 2/13/17 3:24 PM:
---
TC [tests
results|http://195.239.208.174/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F1512%2Fhead]
About tests results: I don't see real new failures. All failures marked as
'new' look like fluky.
was (Author: tledkov-gridgain):
Waits for TC [tests
results|http://195.239.208.174/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F1512%2Fhead]
> Object array element type is written as a user type
> ---
>
> Key: IGNITE-4673
> URL: https://issues.apache.org/jira/browse/IGNITE-4673
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> {{BinaryWriterExImpl.doWriteObjectArray}} registers {{java.lang.Object}}
> element type as a custom type instead of using {{OBJECT_TYPE_ID}}.
> As a result, platforms (.NET, C++) can not understand such an array.
> This is also suboptimal due to extra type registration and lookups.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4663) BinaryUtils.doReadObjectArray can not read array with platform-only element type
[
https://issues.apache.org/jira/browse/IGNITE-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863816#comment-15863816
]
Taras Ledkov commented on IGNITE-4663:
--
About tests results: I don't see real new failures. All failures marked as
'new' look like fluky.
> BinaryUtils.doReadObjectArray can not read array with platform-only element
> type
>
>
> Key: IGNITE-4663
> URL: https://issues.apache.org/jira/browse/IGNITE-4663
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> {{BinaryUtils.doReadObjectArray}} performs unnecessary class lookup when
> {{deserialize = false}}. When array elements are of platform-only type
> ({{platformId != 0}}), the class can never be resolved.
> * arrays of user-defined types are not supported for platforms
> * performance is suboptimal in binary mode (in Java and platforms)
> Stack trace for platforms problem:
> {code}
> Java exception occurred
> [class=org.apache.ignite.binary.BinaryInvalidTypeException, message=Unknown
> pair [platformId= 0, typeId=3184265]]
> > Apache.Ignite.Core.Common.JavaException : class
> org.apache.ignite.binary.BinaryInvalidTypeException: Unknown pair
> [platformId= 0, typeId=3184265]
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:691)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1521)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1441)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadObjectArray(BinaryUtils.java:1884)
> at
> org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1838)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readObjectDetached(BinaryReaderExImpl.java:1129)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:409)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:61)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4617) CPP: Implement Field-access methods for binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863800#comment-15863800
]
ASF GitHub Bot commented on IGNITE-4617:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1525
IGNITE-4617: Added field-access methods for BinaryObject.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4617
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1525.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 #1525
commit 8f010883948dfa3c0d99bfb37ea1b477b2978855
Author: Igor Sapego
Date: 2017-02-01T15:42:46Z
IGNITE-4617: Added stubs for HasField and GetField methods.
commit 419b2f18569c9d413b7116a1eb730c8fa0561c75
Author: Igor Sapego
Date: 2017-02-01T16:32:32Z
IGNITE-4617: Added tests.
commit ff1044f5d3c0886650652174c0bcf9b39a162702
Author: Igor Sapego
Date: 2017-02-01T16:42:17Z
Merge remote-tracking branch 'upstream/master' into ignite-4617
commit b6d4792a8680ee8c87d8de44b445540c4ebb3959
Author: Igor Sapego
Date: 2017-02-01T18:21:06Z
IGNITE-4617: Refactored BinaryObject.
commit 8ed378b21c9791282c0919d0bcfc41f052926247
Author: Igor Sapego
Date: 2017-02-03T12:25:54Z
Merge remote-tracking branch 'upstream/master' into ignite-4617
commit b2fa1ed0eb30e6ef1d5ad7d8ce07c50efcac3449
Author: Igor Sapego
Date: 2017-02-03T18:05:20Z
IGNITE-4617: HasField and GetField implemented.
commit dd92997ddff1954cd5f4ea31ca53ea1a1cc88b10
Author: Igor Sapego
Date: 2017-02-06T13:50:25Z
IGNITE-4617: Used templated id resolver where possible.
commit b94ece2a47e04be949a158fa0553c108a61f044f
Author: Igor Sapego
Date: 2017-02-06T14:36:58Z
IGNITE-4617: Fix for test.
commit cc2b68685c0111d099fbd02528aa4586b29987a7
Author: Igor Sapego
Date: 2017-02-06T16:19:40Z
IGNITE-4617: Added MetadataBinaryIdResolver
commit 0420bc765ca7bd2a255f547a973f322aee1aba17
Author: Igor Sapego
Date: 2017-02-07T13:56:05Z
IGNITE-4617: Added type id check on deserialization.
commit 578827981d70f38542795a65814b9fce659cf756
Author: Igor Sapego
Date: 2017-02-08T18:59:40Z
IGNITE-4617: Implemented local metadata retrieval
commit 73418962d1583aa54578ab77e21860ccd6a5a319
Author: Igor Sapego
Date: 2017-02-09T17:17:29Z
IGNITE-4617: Added Clone() method to BinaryIdResolver
commit f6a2abbb0223955ee19aa923b3d3b39da7b767ac
Author: Igor Sapego
Date: 2017-02-10T18:16:33Z
IGNITE-4617: Added basic id resolver
commit d46813148bf42fdc901885c630ec0722877ff7cf
Author: Igor Sapego
Date: 2017-02-13T12:18:21Z
Merge remote-tracking branch 'upstream/master' into ignite-4617
commit 82822692bb77a9da8c55b5ea0a583aa936ba646f
Author: Igor Sapego
Date: 2017-02-13T14:07:46Z
IGNITE-4617: Some refactoring.
commit 5b76b669a0b546bd4e0887874443c39e6ee26da2
Author: Igor Sapego
Date: 2017-02-13T14:13:27Z
IGNITE-4617: Removed BinaryFieldMeta
commit 3cb3eece42c56be55096150770472484edd3ed47
Author: Igor Sapego
Date: 2017-02-13T14:29:56Z
IGNITE-4617: Test added.
commit a034e291a5b33c702c6d214d02f517fdc850d6db
Author: Igor Sapego
Date: 2017-02-13T15:00:20Z
IGNITE-4617: Added stub for the GetEnumValue.
commit 7f3254ac8c278a48bf2dc82f6f542d375fca2fbc
Author: Igor Sapego
Date: 2017-02-13T15:03:48Z
IGNITE-4617: Added test for GetEnumValue
> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 1.9
>
>
> Currently we have very limited implementation of binary objects that does not
> provide access to fields of the binary object. At least such methods as
> {{HasField}} and {{GetField}} should be implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4617) CPP: Implement Field-access methods for binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863798#comment-15863798
]
Igor Sapego commented on IGNITE-4617:
-
[~vozerov],
I've added {{enumOrdinal()}} analogue (though I've decided to call it
{{GetEnumValue}}), but as enums are not currently supported by in the C++, we
only throw exceptions currently if user tries to call it. I'm not sure if it's
useful in this state. I believe, we should create separate ticke for enums
support and enum version of the {{BinaryObject}}.
> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 1.9
>
>
> Currently we have very limited implementation of binary objects that does not
> provide access to fields of the binary object. At least such methods as
> {{HasField}} and {{GetField}} should be implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-3939) Compact long zero values binary representation
[ https://issues.apache.org/jira/browse/IGNITE-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-3939: --- Assignee: Vladimir Ozerov (was: Andrew Mashenkov) > Compact long zero values binary representation > -- > > Key: IGNITE-3939 > URL: https://issues.apache.org/jira/browse/IGNITE-3939 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 1.7 >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov > Fix For: 2.0 > > > We can use separate type for Long zero values and exclude 8-byte value from > binary representation. This will reduce memory footprint and network load. > Compatibility with previous versions MUST be preserved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4541) Create test for Hadoop running in external JVM
[
https://issues.apache.org/jira/browse/IGNITE-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4541:
---
Assignee: Vladimir Ozerov (was: Ivan Veselovsky)
> Create test for Hadoop running in external JVM
> --
>
> Key: IGNITE-4541
> URL: https://issues.apache.org/jira/browse/IGNITE-4541
> Project: Ignite
> Issue Type: Task
> Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> *Problem*
> Currently we run all Hadoop tests in synthetic "single JVM" mode. This way we
> miss lots of potential issues. We need to be able to run them in real
> distributed mode, but on a single machine.
> *Simplified solution*
> 1) Start N external nodes
> 2) Submit a job to these nodes and validate the result
> We can start with simple Teragen->Terasort->Teravalidate scenario.
> Please look through {{Process}} and {{ProcessBuilder}} classes usages - most
> probably we already have all necessary infrastructure to start nodes in
> external JVM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-3244) Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
[
https://issues.apache.org/jira/browse/IGNITE-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863743#comment-15863743
]
Alexey Kuznetsov commented on IGNITE-3244:
--
The problem is co.value(this, cpy) erases array type information while
marshalling.
> Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
> ---
>
> Key: IGNITE-3244
> URL: https://issues.apache.org/jira/browse/IGNITE-3244
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.0
>
>
> If to put a custom object array into a cache like this one
> {code}
> TestObject[] arr = new TestObject[] {new TestObject(i)};
> cache.put(0, arr);
> {code}
> then it will be serialized as Object[] array in
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} method.
> This leads to the situation when object's array type is lost and on cache.get
> the code below produces {{ClassCastException}}
> {code}
> TestObject[] obj = cache.get(i);
> {code}
> The full test is already added into
> {{GridCacheBinaryObjectsAbstractSelfTest.testCustomArrays}}.
> To fix the issue we have to revisit logic of
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} and
> {{CacheObjectContext.unwrapBinary}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-3244) Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
[
https://issues.apache.org/jira/browse/IGNITE-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863741#comment-15863741
]
Alexey Kuznetsov commented on IGNITE-3244:
--
[~vozerov] If you look at CacheObjectContext#unwrapBinary() you will see at the
end : co.value(this, cpy) . Which evaluates unmarshelling
> Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
> ---
>
> Key: IGNITE-3244
> URL: https://issues.apache.org/jira/browse/IGNITE-3244
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.0
>
>
> If to put a custom object array into a cache like this one
> {code}
> TestObject[] arr = new TestObject[] {new TestObject(i)};
> cache.put(0, arr);
> {code}
> then it will be serialized as Object[] array in
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} method.
> This leads to the situation when object's array type is lost and on cache.get
> the code below produces {{ClassCastException}}
> {code}
> TestObject[] obj = cache.get(i);
> {code}
> The full test is already added into
> {{GridCacheBinaryObjectsAbstractSelfTest.testCustomArrays}}.
> To fix the issue we have to revisit logic of
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} and
> {{CacheObjectContext.unwrapBinary}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4685) Propagate platform plugin configuration to Java
[
https://issues.apache.org/jira/browse/IGNITE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-4685:
--
Assignee: Vladimir Ozerov (was: Pavel Tupitsyn)
> Propagate platform plugin configuration to Java
> ---
>
> Key: IGNITE-4685
> URL: https://issues.apache.org/jira/browse/IGNITE-4685
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Labels: .NET
> Fix For: 2.0
>
>
> {{IPluginConfiguration}} implementations should be able to propagate data to
> Java side and update corresponding {{PluginConfiguration}} there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4685) Propagate platform plugin configuration to Java
[
https://issues.apache.org/jira/browse/IGNITE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863709#comment-15863709
]
ASF GitHub Bot commented on IGNITE-4685:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1524
IGNITE-4685 Propagate platform plugin configuration to Java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4685
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1524.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 #1524
commit 58237bb9a7b4821f678baca50b048d61719b4ca4
Author: Pavel Tupitsyn
Date: 2017-02-13T13:52:40Z
IGNITE-4685 Propagate platform plugin configuration to Java
> Propagate platform plugin configuration to Java
> ---
>
> Key: IGNITE-4685
> URL: https://issues.apache.org/jira/browse/IGNITE-4685
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> {{IPluginConfiguration}} implementations should be able to propagate data to
> Java side and update corresponding {{PluginConfiguration}} there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4484) Call commit for read-only transactions.
[ https://issues.apache.org/jira/browse/IGNITE-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny reassigned IGNITE-4484: -- Assignee: Alexei Scherbakov (was: Stanilovsky Evgeny) > Call commit for read-only transactions. > --- > > Key: IGNITE-4484 > URL: https://issues.apache.org/jira/browse/IGNITE-4484 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.8 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 1.9 > > > IGNITE-3601 introduces a behavior, which is not compliant with tx isolation > semantics. > Read-only transaction doesn't throw optimisitc exception in case if entry > version were changes by other writing tx. > With the appearance of IGNITE-4285 this is no longer needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4677) Incorrect connectable node detection in router mode for Java thin client
[
https://issues.apache.org/jira/browse/IGNITE-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863707#comment-15863707
]
ASF GitHub Bot commented on IGNITE-4677:
GitHub user nva opened a pull request:
https://github.com/apache/ignite/pull/1523
IGNITE-4677 Fixed incorrect connectable node detection in router mode for
Java thin client
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4677
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1523.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 #1523
commit 631d148a2883e340c1a45f7355b8f5197da1
Author: Andrey Novikov
Date: 2017-02-09T08:26:30Z
IGNITE-4677 Fixed connectable node detection in router mode for Java thin
client.
commit e33fbb71303e4f8120c663bcf44ed3a74745981a
Author: Andrey Novikov
Date: 2017-02-09T11:51:41Z
IGNITE-4677 Fixed connectable node detection in router mode for Java thin
client.
commit 8d4213e24e03cbb98b8543c1624b7435c20fa7a5
Author: nva
Date: 2017-02-12T05:21:35Z
IGNITE-4677 Exclude virtual mac for Microsoft tunnel adapter.
> Incorrect connectable node detection in router mode for Java thin client
>
>
> Key: IGNITE-4677
> URL: https://issues.apache.org/jira/browse/IGNITE-4677
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: 1.9
>
>
> * In case of connect using Java client to localhost: in router mode all
> nodes listen same localhost: on other hosts will be marked as
> connectable.
> {code}
> boolean noAttrsAndMetrics = (metricsCache && attrCache) ||
> (node.attributes().isEmpty() && node.metrics() == null);
> boolean reachable = noAttrsAndMetrics || ...
> {code}
> * Under Windows org.apache.ignite.internal.util.IgniteUtils#allLocalIps
> return same mac: 00-00-00-00-00-00-00-E0 on different hosts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4484) Call commit for read-only transactions.
[ https://issues.apache.org/jira/browse/IGNITE-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863703#comment-15863703 ] ASF GitHub Bot commented on IGNITE-4484: GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/1522 IGNITE-4484 fix not compliant with tx isolation semantics You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4484 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1522.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 #1522 commit 28ad4d6d97d706c017209566977a7ca6cb033a6d Author: Evgeny Stanilovskiy Date: 2017-02-13T13:01:25Z IGNITE-4484 fix not compliant with tx isolation semantics > Call commit for read-only transactions. > --- > > Key: IGNITE-4484 > URL: https://issues.apache.org/jira/browse/IGNITE-4484 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.8 >Reporter: Alexei Scherbakov >Assignee: Stanilovsky Evgeny > Fix For: 1.9 > > > IGNITE-3601 introduces a behavior, which is not compliant with tx isolation > semantics. > Read-only transaction doesn't throw optimisitc exception in case if entry > version were changes by other writing tx. > With the appearance of IGNITE-4285 this is no longer needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4558) Use BinaryArrayIdentityResolver by default
[
https://issues.apache.org/jira/browse/IGNITE-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4558:
---
Assignee: Evgenii Zhuravlev (was: Vladimir Ozerov)
[~ezhuravl], my comments:
1) Please see my minor corrections.
2) From now on we never use {{Object.hashCode()}}. This is expected change, but
I think we should also apply this idea to {{BinaryObjectBuilder}} and disallow
setting hash code by hand. Let's remove {{BinaryObjectBuilder.hashCode}} method
and see if other parts of Ignite (especially DML) work fine. Also this should
simplify {{BinaryClassDescriptor.postWrite}} method a lot.
> Use BinaryArrayIdentityResolver by default
> --
>
> Key: IGNITE-4558
> URL: https://issues.apache.org/jira/browse/IGNITE-4558
> Project: Ignite
> Issue Type: Improvement
> Components: binary
>Reporter: Pavel Tupitsyn
>Assignee: Evgenii Zhuravlev
>Priority: Critical
> Fix For: 2.0
>
>
> Currently if there is no configured
> {{BinaryTypeConfiguration.IdentityResolver}}, we call Object.hashCode().
> This is not consistent with DML, and there is a warning:
> {code}
> Binary object's type does not have identity resolver explicitly set,
> therefore BinaryArrayIdentityResolver is used to generate hash codes for its
> instances, and therefore hash code of this binary object will most likely not
> match that of its non serialized form. For finer control over identity of
> this type, please update your BinaryConfiguration accordingly.
> {code}
> In 2.0 we should use {{BinaryArrayIdentityResolver}} by default.
> 2.0 migration guide has to be updated if needed:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-603) [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests
[ https://issues.apache.org/jira/browse/IGNITE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Menshikov reassigned IGNITE-603: -- Assignee: Alexander Menshikov > [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests > - > > Key: IGNITE-603 > URL: https://issues.apache.org/jira/browse/IGNITE-603 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Alexander Menshikov > Labels: Muted_test > > Test have to be uncommented and fixed or the commented code have to be > removed. > See comments at GG-3804. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4686) Web Console: Add grouping by company on Admin panel screen
[ https://issues.apache.org/jira/browse/IGNITE-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova updated IGNITE-4686: -- Component/s: UI > Web Console: Add grouping by company on Admin panel screen > -- > > Key: IGNITE-4686 > URL: https://issues.apache.org/jira/browse/IGNITE-4686 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Affects Versions: 1.8 >Reporter: Alexey Kuznetsov >Assignee: Vica Abramova > Fix For: 1.9 > > > Add tab with table that will be grouped by company. > This table should has following features: > # Combo with list of companies to show only selected companies. > # Filter with company name (to quick filter). > # Columns with metrics should show totals for company. > # Instead of "Action" column show "Collapse/Expand" control. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4686) Web Console: Add grouping by company on Admin panel screen
[ https://issues.apache.org/jira/browse/IGNITE-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova updated IGNITE-4686: -- Summary: Web Console: Add grouping by company on Admin panel screen (was: Web Console: Add grouping by company on Amin panel screen) > Web Console: Add grouping by company on Admin panel screen > -- > > Key: IGNITE-4686 > URL: https://issues.apache.org/jira/browse/IGNITE-4686 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.8 >Reporter: Alexey Kuznetsov >Assignee: Vica Abramova > Fix For: 1.9 > > > Add tab with table that will be grouped by company. > This table should has following features: > # Combo with list of companies to show only selected companies. > # Filter with company name (to quick filter). > # Columns with metrics should show totals for company. > # Instead of "Action" column show "Collapse/Expand" control. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860221#comment-15860221
]
Fred edited comment on IGNITE-3429 at 2/13/17 12:49 PM:
By chance, does anyone have some examples / tests? Upgraded to apache ignite
1.8. I configured BinaryTypeConfiguration with
(org.hibernate.cache.internal.OldCacheKeyImplementation) from above then used
files from https://issues.apache.org/jira/browse/IGNITE-1794 since on Hibernate
5.2.7. I noticed the BinaryAbstractIdentityResolver being called and returning
true but when I call the same service I noticed the database being hit. Also
tried switching to Hibernate 4.3.11 and first workaround from above with same
results.
XML Configuration from
http://apacheignite.gridgain.org/v1.6/docs/hibernate-l2-cache
```
hibernate.cache.use_query_cache=true
hibernate.cache.use_second_level_cache=true
hibernate.cache.region.factory_class=org.apache.ignite.cache.hibernate.HibernateRegionFactory
org.apache.ignite.hibernate.default_access_type=READ_ONLY
@Entity(name = "Person")
@Cache(usage = CacheConcurrencyStrategy.READ_WRITE)
public class Person
```
was (Author: fwvista):
By chance, does anyone have some examples / tests? Upgraded to apache ignite
1.8. I configured BinaryTypeConfiguration with
(org.hibernate.cache.internal.OldCacheKeyImplementation) from above then used
files from https://issues.apache.org/jira/browse/IGNITE-1794 since on Hibernate
5.2.7. I noticed the BinaryAbstractIdentityResolver being called and returning
true but when I call the same service I noticed the database being hit. Also
tried switching to Hibernate 4.3.11 and first workaround from above with same
results.
Also, getting Caused by: java.lang.NoSuchMethodException:
org.hibernate.cache.internal.OldCacheKeyImplementation.() since
org.hibernate.cache.internal.OldCacheKeyImplementation doesnt have a default
constructor.
XML Configuration from
http://apacheignite.gridgain.org/v1.6/docs/hibernate-l2-cache
```
hibernate.cache.use_query_cache=true
hibernate.cache.use_second_level_cache=true
hibernate.cache.region.factory_class=org.apache.ignite.cache.hibernate.HibernateRegionFactory
org.apache.ignite.hibernate.default_access_type=READ_ONLY
@Entity(name = "Person")
@Cache(usage = CacheConcurrencyStrategy.READ_WRITE)
public class Person
```
> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
> Issue Type: Bug
> Components: cache, Hibernate L2 cache
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>Priority: Critical
> Fix For: 2.0
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries
> in the Hibernate L2 cache. This class contains {{type}} field and custom
> {{equals}} logic where the type is used as a helper and does not participate
> in comparison. Instances of the same type are producing different hash codes
> in different JVMs, which actually breaks comparison when binary format is
> used, where byte arrays are compared.
> The issue is described in more detail here:
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-4687) Web console: Use pool for process REST request in Web Agent
[ https://issues.apache.org/jira/browse/IGNITE-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-4687. -- Assignee: (was: Andrey Novikov) Merge changes to master. > Web console: Use pool for process REST request in Web Agent > --- > > Key: IGNITE-4687 > URL: https://issues.apache.org/jira/browse/IGNITE-4687 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4645) Best effort to avoid extra copying in binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863560#comment-15863560
]
Vladimir Ozerov edited comment on IGNITE-4645 at 2/13/17 12:18 PM:
---
[~gvvinblade], my comments:
1) {{GridBinaryMarshaller}} - we perform new class descriptor lookup. Let's
make sure that it is re-used inside writer, so that we do not need to perform
it twice.
2) {{BinaryWriterSchemaHolder}} - constants should be moved to {{BinaryUtils}}.
They must have meaningful names, as currently it is impossible to understand
what they are about.
3) Moreover, {{FOOTER_PER_FIELD_SIZE_4 == FOOTER_PER_FIELD_SIZE_1 + 4}}, where
{{4}} is additional overhead caused be disabled compact footers. The same goes
for {{FOOTER_PER_FIELD_SIZE_5}} and {{FOOTER_PER_FIELD_SIZE_6}}. Please remove
these three constants and introduce separate constant for compact footer.
4) {{BinaryUtils}} - same as p.3, several values are mixed into one for
{{P_X_BYTE_SIZE}} constants. How {{P_8_BYTE_SIZE}} can be equal to {{9}}?
Instead, it should be {{8}}, and {{1}} should be moved to separate constant.
5) {{BinaryClassDescriptor}} - please avoid wildcards in imports.
6) {{BinaryClassDescriptor}} - another magic constant {{-1}}.
was (Author: vozerov):
[~gvvinblade], my comments:
1) {{GridBinaryMarshaller}} - we perform new class descriptor lookup. Let's
make sure that it is re-used inside writer, so that we do not need to perform
it twice.
2) {{BinaryWriterSchemaHolder}} - constants should be moved to {{BinaryUtils}}.
They must have meaningful names, as currently it is impossible to understand
what they are about.
3) Moreover, {{FOOTER_PER_FIELD_SIZE_4 == FOOTER_PER_FIELD_SIZE_1 + 4]}, where
{{4}} is additional overhead caused be disabled compact footers. The same goes
for {{FOOTER_PER_FIELD_SIZE_5}} and {{FOOTER_PER_FIELD_SIZE_6}}. Please remove
these three constants and introduce separate constant for compact footer.
4) {{BinaryUtils}} - same as p.3, several values are mixed into one for
{{P_X_BYTE_SIZE}} constants. How {{P_8_BYTE_SIZE}} can be equal to {{9}}?
Instead, it should be {{8}}, and {{1}} should be moved to separate constant.
5) {{BinaryClassDescriptor}} - please avoid wildcards in imports.
6) {{BinaryClassDescriptor}} - another magic constant {{-1}}.
> Best effort to avoid extra copying in binary marshaller
> ---
>
> Key: IGNITE-4645
> URL: https://issues.apache.org/jira/browse/IGNITE-4645
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Fix For: 1.9
>
>
> If we marshal a class that contain only primitives then we can predict the
> final byte array size and avoid copies to grow array and final trimming.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4674) Ignite Web Console: Support DML queries
[ https://issues.apache.org/jira/browse/IGNITE-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-4674: --- Component/s: wizards > Ignite Web Console: Support DML queries > --- > > Key: IGNITE-4674 > URL: https://issues.apache.org/jira/browse/IGNITE-4674 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Denis Magda >Assignee: Alexey Kuznetsov >Priority: Critical > Fix For: 1.9 > > > Presently it's impossible to execute DML queries from the console. Let's > enable this capability in 1.9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4158) Implement Time type for binary protocol.
[
https://issues.apache.org/jira/browse/IGNITE-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863528#comment-15863528
]
Vladimir Ozerov commented on IGNITE-4158:
-
[~daradurvs],
I have mixed feelings after review of this ticket :-) On the one hand this is
an example of great in-depth implementation of rather complex logic. Thank you
for this contribution. On the other hand it demonstrates how difficult it is to
add new special types to binary protocol. You have to change dozes of classes,
often with duplicated code. We definitely should spend some time on refactoring
of the whole binary infrastructure, because otherwise it will become (already?)
unmanageable very soon.
I added some missing parts (handling in binary builder and ODBC processor), and
merged the fix into {{ignite-2.0}} branch. Please take a look on final commit
{{00dd3d8}} if you are curios what was missed.
Also I created related tickets for .NET, CPP and ODBC parts.
Cheers,
Vladimir.
> Implement Time type for binary protocol.
>
>
> Key: IGNITE-4158
> URL: https://issues.apache.org/jira/browse/IGNITE-4158
> Project: Ignite
> Issue Type: Task
> Components: binary
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> Currently there is no support for Time type in binary protocol. However, this
> type is a commonly used SQL type, which is used in, for example, ODBC.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4645) Best effort to avoid extra copying in binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863477#comment-15863477 ] Igor Seliverstov commented on IGNITE-4645: -- Ready for merge > Best effort to avoid extra copying in binary marshaller > --- > > Key: IGNITE-4645 > URL: https://issues.apache.org/jira/browse/IGNITE-4645 > Project: Ignite > Issue Type: Bug > Components: binary >Reporter: Yakov Zhdanov >Assignee: Igor Seliverstov > Fix For: 1.9 > > > If we marshal a class that contain only primitives then we can predict the > final byte array size and avoid copies to grow array and final trimming. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4687) Web console: Use pool for process REST request in Web Agent
[ https://issues.apache.org/jira/browse/IGNITE-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-4687: -- Resolution: Fixed Assignee: Andrey Novikov (was: Vasiliy Sisko) > Web console: Use pool for process REST request in Web Agent > --- > > Key: IGNITE-4687 > URL: https://issues.apache.org/jira/browse/IGNITE-4687 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
