[jira] [Issue Comment Deleted] (IGNITE-2422) Unable to deserialize BinaryObjectBuilder
[
https://issues.apache.org/jira/browse/IGNITE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Kozlov updated IGNITE-2422:
--
Comment: was deleted
(was: [~dmagda] I'm sorry, hurried to the test.
{{BinaryObjectBuilder}} and {{BinaryObjectBuilderImpl}} classes are not checked
{{Serializable.class.isAssignableFrom(cls)}} (true if a class implements
serializable and false otherwise), so I thought it would be better to add a
serializable and clonable in {{BinaryObjectBuilder}}.
Then it turns out that it is necessary to remove the check from the
{{ClassesGenerator}} (I think it is not good)?)
> Unable to deserialize BinaryObjectBuilder
> -
>
> Key: IGNITE-2422
> URL: https://issues.apache.org/jira/browse/IGNITE-2422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Labels: important
> Fix For: 2.0
>
> Attachments: ExampleNodeStartup.java
>
>
> Presently it's possible to serialize {{BinaryObjectBuilder}} but it will lead
> to the errors at deserialization stage.
> After a brief investigation I see that this happens because neither
> {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {{org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}
> presents in {{META-INF/classnames.properties}} file.
> If you try to update
> {{ignite/modules/core/src/main/resources/META-INF/classnames.properties}} by
> building the project from scratch and copying-pasting generated content from
> built {{classnames.properties}}, then you will still see that there are still
> no entries for {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}.
> Looks like that {{ClassesGenerator}} misses these and other possible classes
> by some reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2422) Unable to deserialize BinaryObjectBuilder
[
https://issues.apache.org/jira/browse/IGNITE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829486#comment-15829486
]
Maksim Kozlov commented on IGNITE-2422:
---
[~dmagda] I'm sorry, hurried to the test.
{{BinaryObjectBuilder}} and {{BinaryObjectBuilderImpl}} classes are not checked
{{Serializable.class.isAssignableFrom(cls)}} (true if a class implements
serializable and false otherwise), so I thought it would be better to add a
serializable and clonable in {{BinaryObjectBuilder}}.
Then it turns out that it is necessary to remove the check from the
{{ClassesGenerator}} (I think it is not good)?
> Unable to deserialize BinaryObjectBuilder
> -
>
> Key: IGNITE-2422
> URL: https://issues.apache.org/jira/browse/IGNITE-2422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Labels: important
> Fix For: 2.0
>
> Attachments: ExampleNodeStartup.java
>
>
> Presently it's possible to serialize {{BinaryObjectBuilder}} but it will lead
> to the errors at deserialization stage.
> After a brief investigation I see that this happens because neither
> {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {{org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}
> presents in {{META-INF/classnames.properties}} file.
> If you try to update
> {{ignite/modules/core/src/main/resources/META-INF/classnames.properties}} by
> building the project from scratch and copying-pasting generated content from
> built {{classnames.properties}}, then you will still see that there are still
> no entries for {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}.
> Looks like that {{ClassesGenerator}} misses these and other possible classes
> by some reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4561) Improve JdbcTypesTransformer to make mapping more flexible
[ https://issues.apache.org/jira/browse/IGNITE-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-4561: --- Assignee: Valentin Kulichenko > Improve JdbcTypesTransformer to make mapping more flexible > -- > > Key: IGNITE-4561 > URL: https://issues.apache.org/jira/browse/IGNITE-4561 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Valentin Kulichenko >Priority: Minor > Fix For: 2.0 > > > Need move logic with query parameter transformation from: > org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#fillParameter to: > org.apache.ignite.cache.store.jdbc.JdbcTypesTransformer > Need extend JdbcTypesTransformer#getColumnValue by adding information about > cache, type, field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4561) Improve JdbcTypesTransformer to make mapping more flexible
[ https://issues.apache.org/jira/browse/IGNITE-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829385#comment-15829385 ] Andrey Novikov commented on IGNITE-4561: [~vkulichenko] As I know you have some idea about JdbcTypesTransformer API improvement. Could you share your thoughts in regards to the proper fix? > Improve JdbcTypesTransformer to make mapping more flexible > -- > > Key: IGNITE-4561 > URL: https://issues.apache.org/jira/browse/IGNITE-4561 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.8 >Reporter: Andrey Novikov >Priority: Minor > Fix For: 2.0 > > > Need move logic with query parameter transformation from: > org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#fillParameter to: > org.apache.ignite.cache.store.jdbc.JdbcTypesTransformer > Need extend JdbcTypesTransformer#getColumnValue by adding information about > cache, type, field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4561) Improve JdbcTypesTransformer to make mapping more flexible
Andrey Novikov created IGNITE-4561: -- Summary: Improve JdbcTypesTransformer to make mapping more flexible Key: IGNITE-4561 URL: https://issues.apache.org/jira/browse/IGNITE-4561 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 1.8 Reporter: Andrey Novikov Priority: Minor Fix For: 2.0 Need move logic with query parameter transformation from: org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#fillParameter to: org.apache.ignite.cache.store.jdbc.JdbcTypesTransformer Need extend JdbcTypesTransformer#getColumnValue by adding information about cache, type, field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 ] Manish Mishra updated IGNITE-4526: -- Attachment: SuiteSnapShot.png SparkTestSuite Results on TeamCity > 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: 2.0 > > Attachments: SuiteSnapShot.png > > > 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.4#6332)
[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=15829376#comment-15829376 ] Manish Mishra commented on IGNITE-4526: --- [~dmagda] I've made changes to the same PR according to latest improvement suggestions. About Special Suite for Spark on TeamCity, Yes I ran it there and the result Snapshot is attached(SuiteSnapShot). Please review these changes when you get time. > 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: 2.0 > > > 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.4#6332)
[jira] [Commented] (IGNITE-4548) Invalid mapping of enum to varchar on load/store operation.
[
https://issues.apache.org/jira/browse/IGNITE-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829311#comment-15829311
]
Vasiliy Sisko commented on IGNITE-4548:
---
Tested postgres and oracle.
> Invalid mapping of enum to varchar on load/store operation.
> ---
>
> Key: IGNITE-4548
> URL: https://issues.apache.org/jira/browse/IGNITE-4548
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 1.9
>
>
> http://stackoverflow.com/questions/41609207/ignite-cachejdbcpojostorefactory-using-enum-fields
> On load of data when type contain enum field that mapped in varchar in
> database sometimes kind of type is incorrectly detected as binary.
> Pojo contain string transformer methods.
> {code}
> private OrderSide side; // OrderSide is an enum
> public String getSideAsString() {
> return this.side.name();
> }
> public void setSideAsString(String s) {
> this.side = OrderSide.valueOf(s);
> }
> {code}
> and enum column described as:
> {code}
> new JdbcTypeField(Types.VARCHAR, "side", String.class, "sideAsString")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4520) Web console: allow agent to connect through proxy
[
https://issues.apache.org/jira/browse/IGNITE-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Novikov updated IGNITE-4520:
---
Assignee: Pavel Konstantinov (was: Andrey Novikov)
> Web console: allow agent to connect through proxy
> -
>
> Key: IGNITE-4520
> URL: https://issues.apache.org/jira/browse/IGNITE-4520
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.9
>
>
> We currently assume that web agent will have direct access to console server.
> Sometimes this is not true and any external Internet access is done through
> SOCKS or HTTP proxy, potentially with authentication.
> We should add settings required for proxy (type, address, login, password)
> and implement the support. {{java.net.Proxy}} class can be used for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4520) Web console: allow agent to connect through proxy
[
https://issues.apache.org/jira/browse/IGNITE-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829204#comment-15829204
]
Andrey Novikov commented on IGNITE-4520:
Documentation fixed
> Web console: allow agent to connect through proxy
> -
>
> Key: IGNITE-4520
> URL: https://issues.apache.org/jira/browse/IGNITE-4520
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.9
>
>
> We currently assume that web agent will have direct access to console server.
> Sometimes this is not true and any external Internet access is done through
> SOCKS or HTTP proxy, potentially with authentication.
> We should add settings required for proxy (type, address, login, password)
> and implement the support. {{java.net.Proxy}} class can be used for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4536) Update metrics for new offheap storage
[ https://issues.apache.org/jira/browse/IGNITE-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4536: Description: Since the new implementation of offheap storage and memory pools, we need to actualize existing cache metrics 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was:Since the new implementation of offheap storage and memory pools, we need to actualize existing cache metrics > Update metrics for new offheap storage > -- > > Key: IGNITE-4536 > URL: https://issues.apache.org/jira/browse/IGNITE-4536 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Alexey Goncharuk > Fix For: 2.0 > > > Since the new implementation of offheap storage and memory pools, we need to > actualize existing cache metrics > 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.4#6332)
[jira] [Updated] (IGNITE-4217) .NET: EventType.SwapspaceAll inconsistent naming
[ https://issues.apache.org/jira/browse/IGNITE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4217: Description: Should be SwapSpaceAll, similar to other events and SwapSpace classes 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was:Should be SwapSpaceAll, similar to other events and SwapSpace classes > .NET: EventType.SwapspaceAll inconsistent naming > > > Key: IGNITE-4217 > URL: https://issues.apache.org/jira/browse/IGNITE-4217 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .NET, breaking-api > Fix For: 2.0 > > > Should be SwapSpaceAll, similar to other events and SwapSpace classes > 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.4#6332)
[jira] [Updated] (IGNITE-3207) Rename IgniteConfiguration.gridName
[ https://issues.apache.org/jira/browse/IGNITE-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3207: Description: We have got a TON of questions on gridName property. Everyone thinks that clusters are formed based on the gridName, that is, nodes with the same grid name will join one cluster, and nodes with a different name will be in a separate cluster. Let's do the following: * Deprecate IgniteConfiguration.gridName * Add IgniteConfiguration.localInstanceName * Rename related parameters in Ignition class (and other places, if present) * Update Javadoc: clearly state that this name only works locally and has no effect on topology. 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was: We have got a TON of questions on gridName property. Everyone thinks that clusters are formed based on the gridName, that is, nodes with the same grid name will join one cluster, and nodes with a different name will be in a separate cluster. Let's do the following: * Deprecate IgniteConfiguration.gridName * Add IgniteConfiguration.localInstanceName * Rename related parameters in Ignition class (and other places, if present) * Update Javadoc: clearly state that this name only works locally and has no effect on topology. > Rename IgniteConfiguration.gridName > --- > > Key: IGNITE-3207 > URL: https://issues.apache.org/jira/browse/IGNITE-3207 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Alexandr Fedotov > Labels: important > Fix For: 2.0 > > > We have got a TON of questions on gridName property. Everyone thinks that > clusters are formed based on the gridName, that is, nodes with the same grid > name will join one cluster, and nodes with a different name will be in a > separate cluster. > Let's do the following: > * Deprecate IgniteConfiguration.gridName > * Add IgniteConfiguration.localInstanceName > * Rename related parameters in Ignition class (and other places, if present) > * Update Javadoc: clearly state that this name only works locally and has no > effect on topology. > 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.4#6332)
[jira] [Updated] (IGNITE-3469) Get rid of deprecated APIs and entities
[ https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3469: Description: There are more than 220 deprecated elements in Ignite code kept for the sake of backward compatibility. We need to cleanup the code for Ignite 2.0 release. 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was: There are more than 220 deprecated elements in Ignite code kept for the sake of backward compatibility. We need to cleanup the code for Ignite 2.0 release. > Get rid of deprecated APIs and entities > --- > > Key: IGNITE-3469 > URL: https://issues.apache.org/jira/browse/IGNITE-3469 > Project: Ignite > Issue Type: Task >Reporter: Alexey Goncharuk > Labels: important > Fix For: 2.0 > > > There are more than 220 deprecated elements in Ignite code kept for the sake > of backward compatibility. We need to cleanup the code for Ignite 2.0 release. > 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.4#6332)
[jira] [Updated] (IGNITE-3548) .NET: Rename ILifecycleBean
[ https://issues.apache.org/jira/browse/IGNITE-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3548: Description: Bean is a Java term. Either rename this interface to something like ILifecycle, or rework the lifecycle notifications to C# event handlers. 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was: Bean is a Java term. Either rename this interface to something like ILifecycle, or rework the lifecycle notifications to C# event handlers. > .NET: Rename ILifecycleBean > --- > > Key: IGNITE-3548 > URL: https://issues.apache.org/jira/browse/IGNITE-3548 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .net, breaking-api > Fix For: 2.0 > > > Bean is a Java term. > Either rename this interface to something like ILifecycle, or rework the > lifecycle notifications to C# event handlers. > 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.4#6332)
[jira] [Updated] (IGNITE-3570) .NET: Rename Boolean to Bool
[ https://issues.apache.org/jira/browse/IGNITE-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3570: Description: Currently there is an inconsistency, some members are Bool, some are Boolean. Let's rename everything to Bool, since it's shorter, and system type alias is `bool`. 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was: Currently there is an inconsistency, some members are Bool, some are Boolean. Let's rename everything to Bool, since it's shorter, and system type alias is `bool`. > .NET: Rename Boolean to Bool > > > Key: IGNITE-3570 > URL: https://issues.apache.org/jira/browse/IGNITE-3570 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .net, breaking-api > Fix For: 2.0 > > > Currently there is an inconsistency, some members are Bool, some are Boolean. > Let's rename everything to Bool, since it's shorter, and system type alias is > `bool`. > 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.4#6332)
[jira] [Updated] (IGNITE-3539) .NET: Remove deprecated code
[ https://issues.apache.org/jira/browse/IGNITE-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3539: Description: Look for [Obsolete] attributes 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was:Look for [Obsolete] attributes > .NET: Remove deprecated code > > > Key: IGNITE-3539 > URL: https://issues.apache.org/jira/browse/IGNITE-3539 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .net, breaking-api > Fix For: 2.0 > > > Look for [Obsolete] attributes > 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.4#6332)
[jira] [Updated] (IGNITE-3506) .NET: Fix ContinuousQuery, QueryBase, and SqlFieldsQuery class constants
[ https://issues.apache.org/jira/browse/IGNITE-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3506: Description: 1) Abbreviations should not be used 2) Constants in generic class are not good 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was: 1) Abbreviations should not be used 2) Constants in generic class are not good > .NET: Fix ContinuousQuery, QueryBase, and SqlFieldsQuery class constants > > > Key: IGNITE-3506 > URL: https://issues.apache.org/jira/browse/IGNITE-3506 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .net, breaking-api > Fix For: 2.0 > > > 1) Abbreviations should not be used > 2) Constants in generic class are not good > 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.4#6332)
[jira] [Updated] (IGNITE-3503) .NET: Remove "Default" prefix from BinaryConfiguration properties
[ https://issues.apache.org/jira/browse/IGNITE-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3503: Description: It does not make much sense and makes property names too long. 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was:It does not make much sense and makes property names too long. > .NET: Remove "Default" prefix from BinaryConfiguration properties > - > > Key: IGNITE-3503 > URL: https://issues.apache.org/jira/browse/IGNITE-3503 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .net, breaking-api > Fix For: 2.0 > > > It does not make much sense and makes property names too long. > 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.4#6332)
[jira] [Updated] (IGNITE-4558) Use BinaryArrayIdentityResolver by default
[
https://issues.apache.org/jira/browse/IGNITE-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4558:
Description:
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
was:
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.
> 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
>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.4#6332)
[jira] [Updated] (IGNITE-3488) Prohibit null as name in all the components (cache name first of all).
[ https://issues.apache.org/jira/browse/IGNITE-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3488: Description: Need to create a list of all the affected components. 2.0 migration guide has to be updated: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide was:Need to create a list of all the affected components. > Prohibit null as name in all the components (cache name first of all). > -- > > Key: IGNITE-3488 > URL: https://issues.apache.org/jira/browse/IGNITE-3488 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.8 >Reporter: Sergi Vladykin >Priority: Critical > Labels: important > Fix For: 2.0 > > > Need to create a list of all the affected components. > 2.0 migration guide has to be updated: > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4548) Invalid mapping of enum to varchar on load/store operation.
[
https://issues.apache.org/jira/browse/IGNITE-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829118#comment-15829118
]
Valentin Kulichenko commented on IGNITE-4548:
-
[~kuaw26]
Changes are OK, but {{JdbcTypesTransformer}} API became even more confusing
then before. In particular, why the new name is called {{getParameterValue}}?
It actually converts Java field value to DB field value, right?
Do we need this API change in the first place? I believe it's better to just
fix the bug first and then propose API change in a separate ticket and properly
design it.
Bottom line - I don't like the public API change, but I don't want to block the
bug fix because of that. Is it possible to separate these changes?
> Invalid mapping of enum to varchar on load/store operation.
> ---
>
> Key: IGNITE-4548
> URL: https://issues.apache.org/jira/browse/IGNITE-4548
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 1.9
>
>
> http://stackoverflow.com/questions/41609207/ignite-cachejdbcpojostorefactory-using-enum-fields
> On load of data when type contain enum field that mapped in varchar in
> database sometimes kind of type is incorrectly detected as binary.
> Pojo contain string transformer methods.
> {code}
> private OrderSide side; // OrderSide is an enum
> public String getSideAsString() {
> return this.side.name();
> }
> public void setSideAsString(String s) {
> this.side = OrderSide.valueOf(s);
> }
> {code}
> and enum column described as:
> {code}
> new JdbcTypeField(Types.VARCHAR, "side", String.class, "sideAsString")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1794) Ignite should support Hibernate 5
[
https://issues.apache.org/jira/browse/IGNITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829111#comment-15829111
]
Valentin Kulichenko commented on IGNITE-1794:
-
It looks like this change is not backward compatible and moreover completely
drops support for Hibernate 4. [~mpereyma], can you please confirm this? If so,
I think we should create two separate modules for Hibernate 4 and 5 to support
both.
> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Assignee: Mykola Pereyma
> Labels: newbie
> Attachments: HibernateCollectionRegionForIgnite.java,
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java,
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4.
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws
> CacheException;}}
> Original user list:
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3537) Add tests checking that data structures work inside user transactions
[ https://issues.apache.org/jira/browse/IGNITE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828900#comment-15828900 ] ASF GitHub Bot commented on IGNITE-3537: Github user javaller closed the pull request at: https://github.com/apache/ignite/pull/1441 > Add tests checking that data structures work inside user transactions > - > > Key: IGNITE-3537 > URL: https://issues.apache.org/jira/browse/IGNITE-3537 > Project: Ignite > Issue Type: Task > Components: data structures >Reporter: Semen Boikov >Assignee: Vadim >Priority: Minor > Labels: newbie > > Need create tests to check that Ignite data structures work inside user > transaction. Now data structures should use independent transactions, test > should jus check that there are no exceptions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3537) Add tests checking that data structures work inside user transactions
[ https://issues.apache.org/jira/browse/IGNITE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828902#comment-15828902 ] ASF GitHub Bot commented on IGNITE-3537: GitHub user javaller reopened a pull request: https://github.com/apache/ignite/pull/1441 IGNITE-3537 Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, IgniteAtomicLong. Added new testcases ( testIsolation method ) into classes GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, IgniteCountDownLatchAbstractSelfTest, GridCacheAtomicStampedApiSelfAbstractTest, GridCacheAtomicReferenceApiSelfAbstractTest, IgniteAtomicLongApiAbstractSelfTest. You can merge this pull request into a Git repository by running: $ git pull https://github.com/javaller/ignite master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1441.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 #1441 commit e41a92f051594953f5f67c86e3c2878dfbb2e4e2 Author: javaller Date: 2016-12-15T14:27:01Z test commit & push commit 9f204b1d9d2cd3a12e1cbe0c487b42da96963a78 Author: javaller Date: 2016-12-18T14:38:37Z Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, IgniteAtomicLong. Added new testcases ( testIsolation methon ) into classes GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, IgniteCountDownLatchAbstractSelfTest, GridCacheAtomicStampedApiSelfAbstractTest, GridCacheAtomicReferenceApiSelfAbstractTest, IgniteAtomicLongApiAbstractSelfTest. commit 6b74e31b73db61b04c9bbd7dc99297049c39d81f Author: javaller Date: 2016-12-18T18:47:58Z IGNITE-3537: Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, IgniteAtomicLong. Added new testcases ( testIsolation method ) into classes GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, IgniteCountDownLatchAbstractSelfTest, GridCacheAtomicStampedApiSelfAbstractTest, GridCacheAtomicReferenceApiSelfAbstractTest, IgniteAtomicLongApiAbstractSelfTest. commit 29311621a121ab280176ccfef12704d0a84f8601 Author: javaller Date: 2016-12-18T18:48:53Z Merge remote-tracking branch 'origin/master' > Add tests checking that data structures work inside user transactions > - > > Key: IGNITE-3537 > URL: https://issues.apache.org/jira/browse/IGNITE-3537 > Project: Ignite > Issue Type: Task > Components: data structures >Reporter: Semen Boikov >Assignee: Vadim >Priority: Minor > Labels: newbie > > Need create tests to check that Ignite data structures work inside user > transaction. Now data structures should use independent transactions, test > should jus check that there are no exceptions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3537) Add tests checking that data structures work inside user transactions
[ https://issues.apache.org/jira/browse/IGNITE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828899#comment-15828899 ] ASF GitHub Bot commented on IGNITE-3537: GitHub user javaller opened a pull request: https://github.com/apache/ignite/pull/1441 IGNITE-3537 Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, IgniteAtomicLong. Added new testcases ( testIsolation method ) into classes GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, IgniteCountDownLatchAbstractSelfTest, GridCacheAtomicStampedApiSelfAbstractTest, GridCacheAtomicReferenceApiSelfAbstractTest, IgniteAtomicLongApiAbstractSelfTest. You can merge this pull request into a Git repository by running: $ git pull https://github.com/javaller/ignite master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1441.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 #1441 commit e41a92f051594953f5f67c86e3c2878dfbb2e4e2 Author: javaller Date: 2016-12-15T14:27:01Z test commit & push commit 9f204b1d9d2cd3a12e1cbe0c487b42da96963a78 Author: javaller Date: 2016-12-18T14:38:37Z Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, IgniteAtomicLong. Added new testcases ( testIsolation methon ) into classes GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, IgniteCountDownLatchAbstractSelfTest, GridCacheAtomicStampedApiSelfAbstractTest, GridCacheAtomicReferenceApiSelfAbstractTest, IgniteAtomicLongApiAbstractSelfTest. commit 6b74e31b73db61b04c9bbd7dc99297049c39d81f Author: javaller Date: 2016-12-18T18:47:58Z IGNITE-3537: Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, IgniteAtomicLong. Added new testcases ( testIsolation method ) into classes GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, IgniteCountDownLatchAbstractSelfTest, GridCacheAtomicStampedApiSelfAbstractTest, GridCacheAtomicReferenceApiSelfAbstractTest, IgniteAtomicLongApiAbstractSelfTest. commit 29311621a121ab280176ccfef12704d0a84f8601 Author: javaller Date: 2016-12-18T18:48:53Z Merge remote-tracking branch 'origin/master' > Add tests checking that data structures work inside user transactions > - > > Key: IGNITE-3537 > URL: https://issues.apache.org/jira/browse/IGNITE-3537 > Project: Ignite > Issue Type: Task > Components: data structures >Reporter: Semen Boikov >Assignee: Vadim >Priority: Minor > Labels: newbie > > Need create tests to check that Ignite data structures work inside user > transaction. Now data structures should use independent transactions, test > should jus check that there are no exceptions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1794) Ignite should support Hibernate 5
[
https://issues.apache.org/jira/browse/IGNITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1794:
Assignee: Mykola Pereyma
> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Assignee: Mykola Pereyma
> Labels: newbie
> Attachments: HibernateCollectionRegionForIgnite.java,
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java,
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4.
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws
> CacheException;}}
> Original user list:
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1794) Ignite should support Hibernate 5
[
https://issues.apache.org/jira/browse/IGNITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828843#comment-15828843
]
Denis Magda commented on IGNITE-1794:
-
[~vkulichenko], please review the pull-request.
> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Assignee: Mykola Pereyma
> Labels: newbie
> Attachments: HibernateCollectionRegionForIgnite.java,
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java,
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4.
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws
> CacheException;}}
> Original user list:
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1794) Ignite should support Hibernate 5
[
https://issues.apache.org/jira/browse/IGNITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828842#comment-15828842
]
Denis Magda commented on IGNITE-1794:
-
[~mpereyma], sorry for a long reply. I've found this ticket by chance. Please
send a message to the @dev list asking for review explicitly. For now I'm
moving the ticket into "patch available" state.
> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
> Labels: newbie
> Attachments: HibernateCollectionRegionForIgnite.java,
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java,
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4.
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws
> CacheException;}}
> Original user list:
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions
[ https://issues.apache.org/jira/browse/IGNITE-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828777#comment-15828777 ] Alexei Scherbakov edited comment on IGNITE-4523 at 1/18/17 9:13 PM: I've found out what current implementation doens't work with distributed joins. But I think this feature should be compatible with it. Could anyone take a look at current PR state while I'm looking deeper into dsitributed joins code? TC looks OK: http://ci.ignite.apache.org/viewQueued.html?itemId=424438 was (Author: ascherbakov): I've found out what current implementation doens't work with distributed queries. But I think this feature should be compatible with it. Could anyone take a look at current PR state while I'm looking deeper into dsitributed queries code? TC looks OK: http://ci.ignite.apache.org/viewQueued.html?itemId=424438 > Allow distributed SQL query execution over explicit set of partitions > - > > Key: IGNITE-4523 > URL: https://issues.apache.org/jira/browse/IGNITE-4523 > Project: Ignite > Issue Type: Improvement > Components: cache, SQL >Affects Versions: 1.8 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 1.9 > > > 3Currently distributed SQL query is executed on all nodes containing primary > partitions for a cache, sending map query requests on all nodes in grid. > Sometimes we know in advance which partitions hold a data for query, on > example, in case of custom affinity function. > Therefore it's possible to reduce number of nodes receiving map query request > by providing explicit set of partitions, which will give significant > performance advantage and traffic reduction in case of very large clusters. > Internally we already have such functionality, so the only necessary thing is > to provide public API for what. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4537) Update Notifier must not transfer system properties
[ https://issues.apache.org/jira/browse/IGNITE-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828778#comment-15828778 ] Denis Magda commented on IGNITE-4537: - In general, OS and Java version should be enough. However, let me think over a bit. > Update Notifier must not transfer system properties > --- > > Key: IGNITE-4537 > URL: https://issues.apache.org/jira/browse/IGNITE-4537 > Project: Ignite > Issue Type: Bug >Reporter: Denis Magda >Assignee: Dmitry Karachentsev >Priority: Critical > Fix For: 1.9 > > > Apache Ignite Update Notifier that is used for sending updates about new > Apache Ignite versions gathers and transfers all system properties. > The script must not do this. Instead, it has to get only those system > properties like Java version, OS versions that are needed. Otherwise, the > script might send sensitive information like passwords stored in the system > properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions
[ https://issues.apache.org/jira/browse/IGNITE-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828777#comment-15828777 ] Alexei Scherbakov commented on IGNITE-4523: --- I've found out what current implementation doens't work with distributed queries. But I think this feature should be compatible with it. Could anyone take a look at current PR state while I'm looking deeper into dsitributed queries code? TC looks OK: http://ci.ignite.apache.org/viewQueued.html?itemId=424438 > Allow distributed SQL query execution over explicit set of partitions > - > > Key: IGNITE-4523 > URL: https://issues.apache.org/jira/browse/IGNITE-4523 > Project: Ignite > Issue Type: Improvement > Components: cache, SQL >Affects Versions: 1.8 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 1.9 > > > 3Currently distributed SQL query is executed on all nodes containing primary > partitions for a cache, sending map query requests on all nodes in grid. > Sometimes we know in advance which partitions hold a data for query, on > example, in case of custom affinity function. > Therefore it's possible to reduce number of nodes receiving map query request > by providing explicit set of partitions, which will give significant > performance advantage and traffic reduction in case of very large clusters. > Internally we already have such functionality, so the only necessary thing is > to provide public API for what. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4556) .NET: DML documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828770#comment-15828770
]
Denis Magda commented on IGNITE-4556:
-
Thanks Pavel. Will take a look tomorrow.
> .NET: DML documentation and example
> ---
>
> Key: IGNITE-4556
> URL: https://issues.apache.org/jira/browse/IGNITE-4556
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Denis Magda
> Labels: .NET, DML
> Fix For: 1.9
>
>
> See [~dmagda] comment in IGNITE-4045:
> {code}
> In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
> for Java and document only those pieces that are related to .NET. For the
> rest you can refer to Java doc from .NET doc.
> In addition, it will be great if you add a DML example similar to the one we
> have in Java.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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=15828741#comment-15828741 ] Denis Magda commented on IGNITE-4526: - [~manish__mishra], this is excellent progress! Please consider my latest minor comments for this example and please switch to the next more advanced example. BTW, we have a special suite for Spark on TeamCity http://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests_IgniteRdd&branch_IgniteTests=%3Cdefault%3E&tab=buildTypeStatusDiv Did you try to run this suite there? This is something that you have to do at the final stage (before the changes get merged to main repository). > 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: 2.0 > > > 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.4#6332)
[jira] [Commented] (IGNITE-4530) Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
[
https://issues.apache.org/jira/browse/IGNITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828695#comment-15828695
]
Aliaksandr Kazlou commented on IGNITE-4530:
---
Thank you, [~dmagda]!
> Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
>
>
> Key: IGNITE-4530
> URL: https://issues.apache.org/jira/browse/IGNITE-4530
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Aliaksandr Kazlou
> Fix For: 2.0, 1.9
>
>
> {{TcpDiscoveryS3IpFinder}} accepts credentials in a form of
> {{AWSCredentials}} only. This might not be enough for all the cases. In a
> situation when the credentials get expired a special instance of
> {{AWSCredentialsProvider}} can renew them automatically.
> However, the credentials will not be updated if {{StaticCredentialsProvider}}
> is used. This provider is created automatically if user provides raw
> {{AWSCredentials}}.
> We need to add new method to {{TcpDiscoveryS3IpFinder}} that will accept
> {{AWSCredentialsProvider}}:
> {code}
> public void setAwsCredentialsProvider(AWSCredentialsProvider provider) {
> {code}
> A new test has to be added to {{TcpDiscoveryS3IpFinderSelfTest}} as well.
> For more details refer to a discussion on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-td9824.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-4530) Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
[
https://issues.apache.org/jira/browse/IGNITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-4530.
---
> Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
>
>
> Key: IGNITE-4530
> URL: https://issues.apache.org/jira/browse/IGNITE-4530
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Aliaksandr Kazlou
> Fix For: 2.0, 1.9
>
>
> {{TcpDiscoveryS3IpFinder}} accepts credentials in a form of
> {{AWSCredentials}} only. This might not be enough for all the cases. In a
> situation when the credentials get expired a special instance of
> {{AWSCredentialsProvider}} can renew them automatically.
> However, the credentials will not be updated if {{StaticCredentialsProvider}}
> is used. This provider is created automatically if user provides raw
> {{AWSCredentials}}.
> We need to add new method to {{TcpDiscoveryS3IpFinder}} that will accept
> {{AWSCredentialsProvider}}:
> {code}
> public void setAwsCredentialsProvider(AWSCredentialsProvider provider) {
> {code}
> A new test has to be added to {{TcpDiscoveryS3IpFinderSelfTest}} as well.
> For more details refer to a discussion on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-td9824.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4530) Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
[
https://issues.apache.org/jira/browse/IGNITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4530:
Affects Version/s: 1.8
> Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
>
>
> Key: IGNITE-4530
> URL: https://issues.apache.org/jira/browse/IGNITE-4530
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Aliaksandr Kazlou
> Fix For: 2.0, 1.9
>
>
> {{TcpDiscoveryS3IpFinder}} accepts credentials in a form of
> {{AWSCredentials}} only. This might not be enough for all the cases. In a
> situation when the credentials get expired a special instance of
> {{AWSCredentialsProvider}} can renew them automatically.
> However, the credentials will not be updated if {{StaticCredentialsProvider}}
> is used. This provider is created automatically if user provides raw
> {{AWSCredentials}}.
> We need to add new method to {{TcpDiscoveryS3IpFinder}} that will accept
> {{AWSCredentialsProvider}}:
> {code}
> public void setAwsCredentialsProvider(AWSCredentialsProvider provider) {
> {code}
> A new test has to be added to {{TcpDiscoveryS3IpFinderSelfTest}} as well.
> For more details refer to a discussion on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-td9824.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4530) Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
[
https://issues.apache.org/jira/browse/IGNITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4530:
Fix Version/s: 1.9
2.0
> Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
>
>
> Key: IGNITE-4530
> URL: https://issues.apache.org/jira/browse/IGNITE-4530
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Aliaksandr Kazlou
> Fix For: 2.0, 1.9
>
>
> {{TcpDiscoveryS3IpFinder}} accepts credentials in a form of
> {{AWSCredentials}} only. This might not be enough for all the cases. In a
> situation when the credentials get expired a special instance of
> {{AWSCredentialsProvider}} can renew them automatically.
> However, the credentials will not be updated if {{StaticCredentialsProvider}}
> is used. This provider is created automatically if user provides raw
> {{AWSCredentials}}.
> We need to add new method to {{TcpDiscoveryS3IpFinder}} that will accept
> {{AWSCredentialsProvider}}:
> {code}
> public void setAwsCredentialsProvider(AWSCredentialsProvider provider) {
> {code}
> A new test has to be added to {{TcpDiscoveryS3IpFinderSelfTest}} as well.
> For more details refer to a discussion on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-td9824.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4530) Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
[
https://issues.apache.org/jira/browse/IGNITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828669#comment-15828669
]
Denis Magda commented on IGNITE-4530:
-
[~akazlou], great job! I've merged your changes to the master. They will go to
the next Apache Ignite release.
Also, I've added you to the contributors' list.
https://ignite.apache.org/community/resources.html#people
Look forward to more commits from your side ;)
> Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
>
>
> Key: IGNITE-4530
> URL: https://issues.apache.org/jira/browse/IGNITE-4530
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Aliaksandr Kazlou
>
> {{TcpDiscoveryS3IpFinder}} accepts credentials in a form of
> {{AWSCredentials}} only. This might not be enough for all the cases. In a
> situation when the credentials get expired a special instance of
> {{AWSCredentialsProvider}} can renew them automatically.
> However, the credentials will not be updated if {{StaticCredentialsProvider}}
> is used. This provider is created automatically if user provides raw
> {{AWSCredentials}}.
> We need to add new method to {{TcpDiscoveryS3IpFinder}} that will accept
> {{AWSCredentialsProvider}}:
> {code}
> public void setAwsCredentialsProvider(AWSCredentialsProvider provider) {
> {code}
> A new test has to be added to {{TcpDiscoveryS3IpFinderSelfTest}} as well.
> For more details refer to a discussion on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-td9824.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2422) Unable to deserialize BinaryObjectBuilder
[
https://issues.apache.org/jira/browse/IGNITE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828608#comment-15828608
]
Denis Magda commented on IGNITE-2422:
-
[~dreamx], the test created by you passes as is without applying changes you
did for {{BinaryObjectBuilder}}.
Please refer to the attached source in order to recreate a valid test that will
fail all the time until a fix is made up.
In any case, I don't see how making {{BinaryObjectBuilder}} serializable and
clonable may fix the issue. Please refer to my previous comment that states
what needs to be fixed exactly.
> Unable to deserialize BinaryObjectBuilder
> -
>
> Key: IGNITE-2422
> URL: https://issues.apache.org/jira/browse/IGNITE-2422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Labels: important
> Fix For: 2.0
>
> Attachments: ExampleNodeStartup.java
>
>
> Presently it's possible to serialize {{BinaryObjectBuilder}} but it will lead
> to the errors at deserialization stage.
> After a brief investigation I see that this happens because neither
> {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {{org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}
> presents in {{META-INF/classnames.properties}} file.
> If you try to update
> {{ignite/modules/core/src/main/resources/META-INF/classnames.properties}} by
> building the project from scratch and copying-pasting generated content from
> built {{classnames.properties}}, then you will still see that there are still
> no entries for {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}.
> Looks like that {{ClassesGenerator}} misses these and other possible classes
> by some reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1466) CPP: Implement binary objects support.
[
https://issues.apache.org/jira/browse/IGNITE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828511#comment-15828511
]
Igor Sapego commented on IGNITE-1466:
-
I've implemented very simple first approach which is very lightweight wrapper
over the memory with only one method yet - {{Deserialize}}. However I've added
sufficient number of tests to check that this approach is usable with any
objects. Next I'm going to implement some methods that are necessary to
implement hashing function over this class. This is required to implement
IGNITE-1446, which is blocked by this ticket currently.
> CPP: Implement binary objects support.
> --
>
> Key: IGNITE-1466
> URL: https://issues.apache.org/jira/browse/IGNITE-1466
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Labels: cpp, roadmap
>
> We need to support portable objects in the same way as it is done in .Net and
> Java: if some flag ({{keepBinary}}) is set, then we should return not real
> object, but rather a wrapper around it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-4487) NPE on query execution
[
https://issues.apache.org/jira/browse/IGNITE-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk closed IGNITE-4487.
> NPE on query execution
> --
>
> Key: IGNITE-4487
> URL: https://issues.apache.org/jira/browse/IGNITE-4487
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Alexander Menshikov
> Fix For: 1.9
>
> Attachments: IgniteThread.java, Main.java
>
>
> NPE may be thrown when called destroyCache() and started querying.
> Attached example reproduces this case when
> GridDiscoveryManager#removeCacheFilter called but cache state haven't been
> changed to STOPPED
> org.apache.ignite.internal.processors.cache.GridCacheGateway#onStopped.
> {code:none}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> null
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:740)
> at
> com.intellica.evam.engine.event.future.FutureEventWorker.processFutureEvents(FutureEventWorker.java:117)
> at
> com.intellica.evam.engine.event.future.FutureEventWorker.run(FutureEventWorker.java:66)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1693)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:494)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:732)
> ... 2 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.init(GridCacheQueryAdapter.java:712)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:677)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:628)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:548)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$2.applyx(IgniteCacheProxy.java:497)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$2.applyx(IgniteCacheProxy.java:495)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1670)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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=15828400#comment-15828400 ] Sergey Chugunov commented on IGNITE-4302: - Working on multiple on-going updates to the same typeId, expect to finish it tomorrow. > 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.4#6332)
[jira] [Commented] (IGNITE-3837) ODBC: Escape sequences: Support CONVERT function.
[
https://issues.apache.org/jira/browse/IGNITE-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828360#comment-15828360
]
Pavel Tupitsyn commented on IGNITE-3837:
Please see my minor comments in upsource.
> ODBC: Escape sequences: Support CONVERT function.
> -
>
> Key: IGNITE-3837
> URL: https://issues.apache.org/jira/browse/IGNITE-3837
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Pavel Tupitsyn
> Labels: odbc
> Fix For: 1.9
>
>
> Need to implement parsing of the CONVERT function:
> https://msdn.microsoft.com/en-us/library/ms715381(v=vs.85).aspx.
> Note the type conversion (e.g. {{SQL_VARCHAR}} -> {{VARCHAR}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4556) .NET: DML documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828323#comment-15828323
]
ASF GitHub Bot commented on IGNITE-4556:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1439
IGNITE-4556 .NET: DML example
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-4556
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1439.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 #1439
commit e44fa85ddd2e2f3058d6bfa32ea868cd5e6008df
Author: Pavel Tupitsyn
Date: 2017-01-18T16:03:55Z
IGNITE-4556 .NET: DML example
> .NET: DML documentation and example
> ---
>
> Key: IGNITE-4556
> URL: https://issues.apache.org/jira/browse/IGNITE-4556
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, DML
> Fix For: 1.9
>
>
> See [~dmagda] comment in IGNITE-4045:
> {code}
> In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
> for Java and document only those pieces that are related to .NET. For the
> rest you can refer to Java doc from .NET doc.
> In addition, it will be great if you add a DML example similar to the one we
> have in Java.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4499) TcpDiscoverySpi is not reliable in some network split scenarios.
[
https://issues.apache.org/jira/browse/IGNITE-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828296#comment-15828296
]
Andrey Gura commented on IGNITE-4499:
-
Fixed. Current solution: Node should be kicked out from topology (forcibly
failed). At this moment this valid only for TCP connection, not shmem.
{{TcpCommunicationSpi}} fails node in case if it can connect to remote node
(server or client) and all retries are failed. Serve node can fail both server
or client node. Client nodes can fail only other clients nodes. It is
implemented in {{ctreateTcpClient()}} method.
{{TcpDiscoveryNodeFailedMessage}} will be handled by {{TcpDiscoverySpi}} in a
special manner in case of forcible node fail. All nodes will not handle this
message if it isn't verified by coordinator. It allows to avoid of topology
crashes in cases, for example, when two nodes try to kick out each other
(changes in {{ServerImpl}} class).
Client node now can receive {{TcpDiscoveryNodeFailedMessage}} in case of
forcible fail. In this case client reconnection will be performed with delay.
> TcpDiscoverySpi is not reliable in some network split scenarios.
>
>
> Key: IGNITE-4499
> URL: https://issues.apache.org/jira/browse/IGNITE-4499
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Andrey Gura
> Fix For: 2.0
>
>
> Where is a possible caveat in current discovery implementation using ring of
> nodes.
> Imagine grid consisting of nodes A B C D
> Let them form the ring:
> A-B-C-D-A
> If network connectivity issues will arise between nodes A-C and B-D
> discovery spi will never know it and will continue to assume the topology is
> valid.
> On other side, TcpCommunicationSpi will try to run transaction on this
> topology and never will succeed.
> We must drop nodes from topology on communication spi errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4487) NPE on query execution
[
https://issues.apache.org/jira/browse/IGNITE-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828288#comment-15828288
]
ASF GitHub Bot commented on IGNITE-4487:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1388
> NPE on query execution
> --
>
> Key: IGNITE-4487
> URL: https://issues.apache.org/jira/browse/IGNITE-4487
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Alexander Menshikov
> Fix For: 1.8
>
> Attachments: IgniteThread.java, Main.java
>
>
> NPE may be thrown when called destroyCache() and started querying.
> Attached example reproduces this case when
> GridDiscoveryManager#removeCacheFilter called but cache state haven't been
> changed to STOPPED
> org.apache.ignite.internal.processors.cache.GridCacheGateway#onStopped.
> {code:none}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> null
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:740)
> at
> com.intellica.evam.engine.event.future.FutureEventWorker.processFutureEvents(FutureEventWorker.java:117)
> at
> com.intellica.evam.engine.event.future.FutureEventWorker.run(FutureEventWorker.java:66)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1693)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:494)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:732)
> ... 2 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.init(GridCacheQueryAdapter.java:712)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:677)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:628)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:548)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$2.applyx(IgniteCacheProxy.java:497)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$2.applyx(IgniteCacheProxy.java:495)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1670)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4556) .NET: DML documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828099#comment-15828099
]
Pavel Tupitsyn edited comment on IGNITE-4556 at 1/18/17 3:34 PM:
-
* QueryDmlExample added
* Readme.io categories reordered, hidden page created:
https://apacheignite-net.readme.io/docs/distributed-dml
was (Author: ptupitsyn):
Readme.io categories reordered, hidden page created:
https://apacheignite-net.readme.io/docs/distributed-dml
> .NET: DML documentation and example
> ---
>
> Key: IGNITE-4556
> URL: https://issues.apache.org/jira/browse/IGNITE-4556
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, DML
> Fix For: 1.9
>
>
> See [~dmagda] comment in IGNITE-4045:
> {code}
> In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
> for Java and document only those pieces that are related to .NET. For the
> rest you can refer to Java doc from .NET doc.
> In addition, it will be great if you add a DML example similar to the one we
> have in Java.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4269) Implement batch statements in JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828269#comment-15828269 ] Alexander Paschenko edited comment on IGNITE-4269 at 1/18/17 3:28 PM: -- Fixed in *ignite-4169* branch, TC is on the run. was (Author: al.psc): Fixed in ignite-4269 branch, TC is on the run. > Implement batch statements in JDBC driver > - > > Key: IGNITE-4269 > URL: https://issues.apache.org/jira/browse/IGNITE-4269 > Project: Ignite > Issue Type: New Feature > Components: SQL >Affects Versions: 1.8 >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko > Fix For: 1.9 > > > In the course of review of initial DML implementation, it has been agreed > that the first attempt to implement batching (via series of individual > queries) is rather incorrect (effectively series of individual queries > instead of one larger query). So it's been decided not to include batching > into initial release and rather implement it the right way shortly in nearest > releases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4269) Implement batch statements in JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828269#comment-15828269 ] Alexander Paschenko commented on IGNITE-4269: - Fixed in ignite-4269 branch, TC is on the run. > Implement batch statements in JDBC driver > - > > Key: IGNITE-4269 > URL: https://issues.apache.org/jira/browse/IGNITE-4269 > Project: Ignite > Issue Type: New Feature > Components: SQL >Affects Versions: 1.8 >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko > Fix For: 1.9 > > > In the course of review of initial DML implementation, it has been agreed > that the first attempt to implement batching (via series of individual > queries) is rather incorrect (effectively series of individual queries > instead of one larger query). So it's been decided not to include batching > into initial release and rather implement it the right way shortly in nearest > releases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4557) Wrong method is called on rebalancing.
[
https://issues.apache.org/jira/browse/IGNITE-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny updated IGNITE-4557:
---
Assignee: Semen Boikov (was: Stanilovsky Evgeny)
> Wrong method is called on rebalancing.
> --
>
> Key: IGNITE-4557
> URL: https://issues.apache.org/jira/browse/IGNITE-4557
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 2.0
>
>
> During rebalancing the following code might be called from
> {{GridDhtPartitionDemander:695}}:
> {noformat}
> for (Integer miss : supply.missed()) {
> if (cctx.affinity().localNode(miss, topVer))
> fut.partitionMissed(id, miss);
> }
> {noformat}
> The problem is in wrong polymorphic call to
> {noformat}
> public boolean localNode(Object key, AffinityTopologyVersion topVer)
> {noformat}
> Instead the following must be called:
> {noformat}
> public boolean localNode(int part, AffinityTopologyVersion topVer)
> {noformat}
> Also a codebase must be verified for existing similar problems and its better
> to rename both methods to keyLocalNode and partitionLocalNode to avoid
> confusion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4557) Wrong method is called on rebalancing.
[
https://issues.apache.org/jira/browse/IGNITE-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny reassigned IGNITE-4557:
--
Assignee: Stanilovsky Evgeny (was: Alexei Scherbakov)
> Wrong method is called on rebalancing.
> --
>
> Key: IGNITE-4557
> URL: https://issues.apache.org/jira/browse/IGNITE-4557
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Fix For: 2.0
>
>
> During rebalancing the following code might be called from
> {{GridDhtPartitionDemander:695}}:
> {noformat}
> for (Integer miss : supply.missed()) {
> if (cctx.affinity().localNode(miss, topVer))
> fut.partitionMissed(id, miss);
> }
> {noformat}
> The problem is in wrong polymorphic call to
> {noformat}
> public boolean localNode(Object key, AffinityTopologyVersion topVer)
> {noformat}
> Instead the following must be called:
> {noformat}
> public boolean localNode(int part, AffinityTopologyVersion topVer)
> {noformat}
> Also a codebase must be verified for existing similar problems and its better
> to rename both methods to keyLocalNode and partitionLocalNode to avoid
> confusion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1543) SqlQuery returns empty result set when custom PortableIdMapper
[
https://issues.apache.org/jira/browse/IGNITE-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kalashnikov resolved IGNITE-1543.
Resolution: Cannot Reproduce
Assignee: (was: Sergey Kalashnikov)
The issue is not present anymore
> SqlQuery returns empty result set when custom PortableIdMapper
> --
>
> Key: IGNITE-1543
> URL: https://issues.apache.org/jira/browse/IGNITE-1543
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Minor
> Fix For: 1.9
>
> Attachments: ClientTest.java
>
>
> Set custom {{PortableIdMapper}} for a type. Let this mapper to return some
> predefined id for this type (like 12345).
> Then execute SQL to get all the entries of this type. The query will return
> an empty result set.
> Seems that at some point of execution SQL engine or some other part of the
> platform uses default type to id mapping ignoring given {{PotableIdMapper}}.
> To reproduce:
> - Start a server node with portable marshaller enabled;
> - run the code attached (ClientTest.java).
> Add a test to our test suites.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1543) SqlQuery returns empty result set when custom PortableIdMapper
[
https://issues.apache.org/jira/browse/IGNITE-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828164#comment-15828164
]
Sergey Kalashnikov commented on IGNITE-1543:
I have refreshed the reproducer code since it was pretty outdated and would not
compile.
The issue is gone. The code I used is below.
{code}
package org.apache.ignite.examples.misc.client;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.Ignition;
import org.apache.ignite.binary.BinaryIdMapper;
import org.apache.ignite.binary.BinaryObject;
import org.apache.ignite.binary.BinaryObjectBuilder;
import org.apache.ignite.binary.BinaryTypeConfiguration;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheTypeFieldMetadata;
import org.apache.ignite.cache.CacheTypeMetadata;
import org.apache.ignite.cache.QueryEntity;
import org.apache.ignite.cache.query.SqlQuery;
import org.apache.ignite.configuration.BinaryConfiguration;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.TransactionConfiguration;
import org.apache.ignite.internal.binary.BinaryMarshaller;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder;
import java.util.*;
public class ClientTest {
public static void main(String[] args) {
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setPeerClassLoadingEnabled(true);
BinaryMarshaller marshaller = new BinaryMarshaller();
BinaryTypeConfiguration typeCfg = new BinaryTypeConfiguration();
typeCfg.setTypeName("company");
typeCfg.setIdMapper(new BinaryIdMapper() {
@Override public int typeId(String clsName) {
System.out.println("Company mapper!!");
//Comment out this comparision and query will return non empty
result set!
if (clsName.equals("company"))
return 123;
return 0;
}
@Override public int fieldId(int typeId, String fieldName) {
return 0;
}
});
BinaryConfiguration bcfg = new BinaryConfiguration();
bcfg.setTypeConfigurations(Arrays.asList(typeCfg));
cfg.setBinaryConfiguration(bcfg);
cfg.setMarshaller(marshaller);
TransactionConfiguration trCfg = new TransactionConfiguration();
trCfg.setTxSerializableEnabled(true);
cfg.setTransactionConfiguration(trCfg);
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryMulticastIpFinder ipFinder = new
TcpDiscoveryMulticastIpFinder();
spi.setIpFinder(ipFinder);
ipFinder.setAddresses(Arrays.asList("127.0.0.1:47500..47509"));
cfg.setDiscoverySpi(spi);
CacheConfiguration compCacheCfg = new CacheConfiguration();
compCacheCfg.setName("company");
compCacheCfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
boolean useQueryEntity = false;
if (!useQueryEntity) {
CacheTypeMetadata typeMetadata = new CacheTypeMetadata();
typeMetadata.setKeyType(Integer.class);
typeMetadata.setValueType("company");
CacheTypeFieldMetadata addrFieldMeta = new CacheTypeFieldMetadata();
addrFieldMeta.setJavaName("addr");
addrFieldMeta.setJavaType(String.class);
typeMetadata.setValueFields(Arrays.asList(addrFieldMeta));
typeMetadata.setQueryFields(new HashMap>() {{
put("addr", String.class);
}});
compCacheCfg.setTypeMetadata(Arrays.asList(typeMetadata));
} else {
compCacheCfg.setQueryEntities(new ArrayList() {{
QueryEntity e = new QueryEntity();
e.setKeyType("java.lang.Integer");
e.setValueType("company");
e.setFields(new LinkedHashMap(){{
put("addr", "java.lang.String");
}});
add(e);
}});
}
cfg.setCacheConfiguration(compCacheCfg);
Ignite ignite = Ignition.start(cfg);
BinaryObjectBuilder builder = ignite.binary().builder("company");
builder.setField("addr", "USA");
IgniteCache cache =
ignite.cache("company").withKeepBinary();
cache.put(0, builder.build());
System.out.println("Object after modifications: " + cache.get(0));
List results = cache.query(new SqlQuery<>("company", "SELECT * FROM
company")).getAll();
System.out.println("Query result: " + results);
System.out.println("Query size: " + results.size());
assert (results.size() == 1);
ignite.close();
}
}
{code}
> SqlQuery retur
[jira] [Assigned] (IGNITE-4036) Near cache is not expired together with corresponding server cache
[ https://issues.apache.org/jira/browse/IGNITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev reassigned IGNITE-4036: --- Assignee: Dmitry Karachentsev (was: Andrew Mashenkov) > Near cache is not expired together with corresponding server cache > -- > > Key: IGNITE-4036 > URL: https://issues.apache.org/jira/browse/IGNITE-4036 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.7 >Reporter: Sergej Sidorov >Assignee: Dmitry Karachentsev > Fix For: 1.9 > > > Steps to reproduce: > 1. Configure server cache with expiry time > 2. Start server node > 3. Configure client node with near cache > 4. Start client node > 5. Put elements to cache > 6. Wait for the expiry of the cache > 7. Check cache state (server/client) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3837) ODBC: Escape sequences: Support CONVERT function.
[
https://issues.apache.org/jira/browse/IGNITE-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-3837:
Assignee: Pavel Tupitsyn (was: Igor Sapego)
> ODBC: Escape sequences: Support CONVERT function.
> -
>
> Key: IGNITE-3837
> URL: https://issues.apache.org/jira/browse/IGNITE-3837
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Pavel Tupitsyn
> Labels: odbc
> Fix For: 1.9
>
>
> Need to implement parsing of the CONVERT function:
> https://msdn.microsoft.com/en-us/library/ms715381(v=vs.85).aspx.
> Note the type conversion (e.g. {{SQL_VARCHAR}} -> {{VARCHAR}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3837) ODBC: Escape sequences: Support CONVERT function.
[
https://issues.apache.org/jira/browse/IGNITE-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828116#comment-15828116
]
Igor Sapego commented on IGNITE-3837:
-
Looks good to me. Pavel, can you take a look?
> ODBC: Escape sequences: Support CONVERT function.
> -
>
> Key: IGNITE-3837
> URL: https://issues.apache.org/jira/browse/IGNITE-3837
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: odbc
> Fix For: 1.9
>
>
> Need to implement parsing of the CONVERT function:
> https://msdn.microsoft.com/en-us/library/ms715381(v=vs.85).aspx.
> Note the type conversion (e.g. {{SQL_VARCHAR}} -> {{VARCHAR}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4556) .NET: DML documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828099#comment-15828099
]
Pavel Tupitsyn commented on IGNITE-4556:
Readme.io categories reordered, hidden page created:
https://apacheignite-net.readme.io/docs/distributed-dml
> .NET: DML documentation and example
> ---
>
> Key: IGNITE-4556
> URL: https://issues.apache.org/jira/browse/IGNITE-4556
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, DML
> Fix For: 1.9
>
>
> See [~dmagda] comment in IGNITE-4045:
> {code}
> In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
> for Java and document only those pieces that are related to .NET. For the
> rest you can refer to Java doc from .NET doc.
> In addition, it will be great if you add a DML example similar to the one we
> have in Java.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4550) Move service deployment to certain test
[ https://issues.apache.org/jira/browse/IGNITE-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828083#comment-15828083 ] ASF GitHub Bot commented on IGNITE-4550: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1437 IGNITE-4550: Move service deployment to certain test Fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4550 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1437.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 #1437 commit 7724b62bf44e7bd8cbb8ce1fb3aa20b96f1fa410 Author: Andrey V. Mashenkov Date: 2017-01-18T13:48:07Z Fixed. commit 8c48cff7202d4f83b40ac3708db4baeafaf0cae6 Author: Andrey V. Mashenkov Date: 2017-01-18T13:48:33Z Fixed. > Move service deployment to certain test > --- > > Key: IGNITE-4550 > URL: https://issues.apache.org/jira/browse/IGNITE-4550 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.8 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Fix For: 1.9 > > > GridCacheAbstractFullApiSelfTest has service deployment in beforeTest() > method. > It look like there is no need to do this for all tests and service deployment > should be moved to testTransformResourceInjection(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2422) Unable to deserialize BinaryObjectBuilder
[
https://issues.apache.org/jira/browse/IGNITE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828059#comment-15828059
]
Maksim Kozlov edited comment on IGNITE-2422 at 1/18/17 1:39 PM:
[~dmagda] I update PR, review please.
was (Author: dreamx):
[~dmagda] I update PR, please review.
> Unable to deserialize BinaryObjectBuilder
> -
>
> Key: IGNITE-2422
> URL: https://issues.apache.org/jira/browse/IGNITE-2422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Labels: important
> Fix For: 2.0
>
> Attachments: ExampleNodeStartup.java
>
>
> Presently it's possible to serialize {{BinaryObjectBuilder}} but it will lead
> to the errors at deserialization stage.
> After a brief investigation I see that this happens because neither
> {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {{org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}
> presents in {{META-INF/classnames.properties}} file.
> If you try to update
> {{ignite/modules/core/src/main/resources/META-INF/classnames.properties}} by
> building the project from scratch and copying-pasting generated content from
> built {{classnames.properties}}, then you will still see that there are still
> no entries for {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}.
> Looks like that {{ClassesGenerator}} misses these and other possible classes
> by some reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2422) Unable to deserialize BinaryObjectBuilder
[
https://issues.apache.org/jira/browse/IGNITE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828059#comment-15828059
]
Maksim Kozlov commented on IGNITE-2422:
---
[~dmagda] I update PR, please review.
> Unable to deserialize BinaryObjectBuilder
> -
>
> Key: IGNITE-2422
> URL: https://issues.apache.org/jira/browse/IGNITE-2422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Labels: important
> Fix For: 2.0
>
> Attachments: ExampleNodeStartup.java
>
>
> Presently it's possible to serialize {{BinaryObjectBuilder}} but it will lead
> to the errors at deserialization stage.
> After a brief investigation I see that this happens because neither
> {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {{org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}
> presents in {{META-INF/classnames.properties}} file.
> If you try to update
> {{ignite/modules/core/src/main/resources/META-INF/classnames.properties}} by
> building the project from scratch and copying-pasting generated content from
> built {{classnames.properties}}, then you will still see that there are still
> no entries for {{org.apache.ignite.binary.BinaryObjectBuilder}} nor
> {org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}.
> Looks like that {{ClassesGenerator}} misses these and other possible classes
> by some reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4046) C++: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828043#comment-15828043
]
Igor Sapego edited comment on IGNITE-4046 at 1/18/17 1:31 PM:
--
After some studying, it seems that most flexible and optimized way to introduce
identity resolvers to C++ is to add {{IdentityResolver}} interface, and
introduce {{BynaryType::GetIdentityResolver}} method for user types.
{{IdentityResolver}} should be something like this:
{code}
class IdenntityResolver
{
public:
virtual int32_t GetHashCode(const BinaryObject& obj) = 0;
}
{code}
As you can see, {{BinaryObject}} type used here. It is used for the efficiency
reasons, which Pavel has pointed out. {{BinaryObject}} however is not
implemented currently for C++ client, so if there are no objections I'm going
to add it as a blocking issue for this one.
was (Author: isapego):
After some studying, it seems that most flexible and optimized way to introduce
identity resolvers to C++ is to add {{IdentityResolver}} interface, and
introduce {{BynaryType::GetIdentityResolver}} method for user types.
{{IdentityResolver}} should be something like this:
{code}
class IdenntityResolver
{
virtual int32_t GetHashCode(const BinaryObject& obj) = 0;
}
{code}
As you can see, {{BinaryObject}} type used here. It is used for the efficiency
reasons, which Pavel has pointed out. {{BinaryObject}} however is not
implemented currently for C++ client, so if there are no objections I'm going
to add it as a blocking issue for this one.
> C++: Support DML API
>
>
> Key: IGNITE-4046
> URL: https://issues.apache.org/jira/browse/IGNITE-4046
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Labels: roadmap
> Fix For: 1.9
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.C++
> by doing the following:
> - Implement DML API;
> - Enhance {{query_example.cpp}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.C++ readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4046) C++: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828043#comment-15828043
]
Igor Sapego commented on IGNITE-4046:
-
After some studying, it seems that most flexible and optimized way to introduce
identity resolvers to C++ is to add {{IdentityResolver}} interface, and
introduce {{BynaryType::GetIdentityResolver}} method for user types.
{{IdentityResolver}} should be something like this:
{code}
class IdenntityResolver
{
virtual int32_t GetHashCode(const BinaryObject& obj) = 0;
}
{code}
As you can see, {{BinaryObject}} type used here. It is used for the efficiency
reasons, which Pavel has pointed out. {{BinaryObject}} however is not
implemented currently for C++ client, so if there are no objections I'm going
to add it as a blocking issue for this one.
> C++: Support DML API
>
>
> Key: IGNITE-4046
> URL: https://issues.apache.org/jira/browse/IGNITE-4046
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Labels: roadmap
> Fix For: 1.9
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.C++
> by doing the following:
> - Implement DML API;
> - Enhance {{query_example.cpp}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.C++ readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (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 updated IGNITE-4558:
Priority: Critical (was: Major)
> 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
>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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4219) Hive job submission failed with exception ”java.io.UTFDataFormatException“
[
https://issues.apache.org/jira/browse/IGNITE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828040#comment-15828040
]
Vladimir Ozerov commented on IGNITE-4219:
-
Reviewed, performed some minor fixes. Waiting for TC.
> Hive job submission failed with exception ”java.io.UTFDataFormatException“
> --
>
> Key: IGNITE-4219
> URL: https://issues.apache.org/jira/browse/IGNITE-4219
> Project: Ignite
> Issue Type: Bug
> Components: hadoop
>Reporter: Andrew Mashenkov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 1.9
>
>
> Long property passing to Hadoop causes an exception:
> {code}
> Caused by: java.io.UTFDataFormatException
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:2144)
>
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:1987)
>
>at java.io.ObjectOutputStream.writeUTF(ObjectOutputStream.java:865)
>at
> org.apache.ignite.internal.util.IgniteUtils.writeUTFStringNullable(IgniteUtils.java:5029)
>
>at
> org.apache.ignite.internal.util.IgniteUtils.writeStringMap(IgniteUtils.java:4989)
>
>at
> org.apache.ignite.internal.processors.hadoop.HadoopDefaultJobInfo.writeExternal(HadoopDefaultJobInfo.java:137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Deleted] (IGNITE-4559) .NET: Use BinaryArrayIdentityResolver by default
[ https://issues.apache.org/jira/browse/IGNITE-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn deleted IGNITE-4559: --- > .NET: Use BinaryArrayIdentityResolver by default > > > Key: IGNITE-4559 > URL: https://issues.apache.org/jira/browse/IGNITE-4559 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn > Labels: .NET > > Same as IGNITE-4558 for .NET -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4560) .NET: Use BinaryArrayIdentityResolver by default
Pavel Tupitsyn created IGNITE-4560: -- Summary: .NET: Use BinaryArrayIdentityResolver by default Key: IGNITE-4560 URL: https://issues.apache.org/jira/browse/IGNITE-4560 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Fix For: 2.0 Same as IGNITE-4558 for .NET -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4559) .NET: Use BinaryArrayIdentityResolver by default
Pavel Tupitsyn created IGNITE-4559: -- Summary: .NET: Use BinaryArrayIdentityResolver by default Key: IGNITE-4559 URL: https://issues.apache.org/jira/browse/IGNITE-4559 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Fix For: 2.0 Same as IGNITE-4558 for .NET -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1466) CPP: Implement binary objects support.
[
https://issues.apache.org/jira/browse/IGNITE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-1466:
---
Assignee: Igor Sapego
> CPP: Implement binary objects support.
> --
>
> Key: IGNITE-1466
> URL: https://issues.apache.org/jira/browse/IGNITE-1466
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Labels: cpp, roadmap
>
> We need to support portable objects in the same way as it is done in .Net and
> Java: if some flag ({{keepBinary}}) is set, then we should return not real
> object, but rather a wrapper around it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4558) Use BinaryArrayIdentityResolver by default
Pavel Tupitsyn created IGNITE-4558:
--
Summary: 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
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3920) Hadoop: remove PayloadAware interface.
[
https://issues.apache.org/jira/browse/IGNITE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828033#comment-15828033
]
Taras Ledkov commented on IGNITE-3920:
--
Alexey, please review the changes too
> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
> Issue Type: Task
> Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations
> directly from {{IgfsImpl}}. It means that we no longer need
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}}
> to the client.
> Let's remove them all together.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4557) Wrong method is called on rebalancing.
[
https://issues.apache.org/jira/browse/IGNITE-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-4557:
--
Description:
During rebalancing the following code might be called from
{{GridDhtPartitionDemander:695}}:
{noformat}
for (Integer miss : supply.missed()) {
if (cctx.affinity().localNode(miss, topVer))
fut.partitionMissed(id, miss);
}
{noformat}
The problem is in wrong polymorphic call to
{noformat}
public boolean localNode(Object key, AffinityTopologyVersion topVer)
{noformat}
Instead the following must be called:
{noformat}
public boolean localNode(int part, AffinityTopologyVersion topVer)
{noformat}
Also a codebase must be verified for existing similar problems and its better
to rename both methods to keyLocalNode and partitionLocalNode to avoid
confusion.
was:
During rebalancing the following code might be called from
{{GridDhtPartitionDemander:695}}:
{noformat}
for (Integer miss : supply.missed()) {
if (cctx.affinity().localNode(miss, topVer))
fut.partitionMissed(id, miss);
}
{noformat}
The problem is in wrong polymorphic call to
{noformat}
public boolean localNode(Object key, AffinityTopologyVersion topVer)}}
{noformat}
Instead the following must be called:
{noformat}
public boolean localNode(int part, AffinityTopologyVersion topVer);.
{noformat}
Also a codebase must be verified for existing similar problems and its better
to rename both methods to keyLocalNode and partitionLocalNode to avoid
confusion.
> Wrong method is called on rebalancing.
> --
>
> Key: IGNITE-4557
> URL: https://issues.apache.org/jira/browse/IGNITE-4557
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Critical
> Fix For: 2.0
>
>
> During rebalancing the following code might be called from
> {{GridDhtPartitionDemander:695}}:
> {noformat}
> for (Integer miss : supply.missed()) {
> if (cctx.affinity().localNode(miss, topVer))
> fut.partitionMissed(id, miss);
> }
> {noformat}
> The problem is in wrong polymorphic call to
> {noformat}
> public boolean localNode(Object key, AffinityTopologyVersion topVer)
> {noformat}
> Instead the following must be called:
> {noformat}
> public boolean localNode(int part, AffinityTopologyVersion topVer)
> {noformat}
> Also a codebase must be verified for existing similar problems and its better
> to rename both methods to keyLocalNode and partitionLocalNode to avoid
> confusion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4557) Wrong method is called on rebalancing.
Alexei Scherbakov created IGNITE-4557:
-
Summary: Wrong method is called on rebalancing.
Key: IGNITE-4557
URL: https://issues.apache.org/jira/browse/IGNITE-4557
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.6
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
Priority: Critical
Fix For: 2.0
During rebalancing the following code might be called from
{{GridDhtPartitionDemander:695}}:
{noformat}
for (Integer miss : supply.missed()) {
if (cctx.affinity().localNode(miss, topVer))
fut.partitionMissed(id, miss);
}
{noformat}
The problem is in wrong polymorphic call to
{noformat}
public boolean localNode(Object key, AffinityTopologyVersion topVer)}}
{noformat}
Instead the following must be called:
{noformat}
public boolean localNode(int part, AffinityTopologyVersion topVer);.
{noformat}
Also a codebase must be verified for existing similar problems and its better
to rename both methods to keyLocalNode and partitionLocalNode to avoid
confusion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3920) Hadoop: remove PayloadAware interface.
[
https://issues.apache.org/jira/browse/IGNITE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3920:
Assignee: Alexey Kuznetsov (was: Taras Ledkov)
> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
> Issue Type: Task
> Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations
> directly from {{IgfsImpl}}. It means that we no longer need
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}}
> to the client.
> Let's remove them all together.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4169) Data streamer mode for DML
[ https://issues.apache.org/jira/browse/IGNITE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4169: Fix Version/s: (was: 2.0) 1.9 > Data streamer mode for DML > -- > > Key: IGNITE-4169 > URL: https://issues.apache.org/jira/browse/IGNITE-4169 > Project: Ignite > Issue Type: New Feature > Components: SQL >Affects Versions: 1.8 >Reporter: Alexander Paschenko >Assignee: Vladimir Ozerov > Fix For: 1.9 > > > SQL INSERT and MERGE are supposed to support data streamer mode which should > be turned on by JDBC connection string param. > Note: particular details of usage means and implementation of this mode, as > well as urgency of this feature are yet to be discussed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4552) Optimize GridDhtLocalPartition.rmvQueue
[ https://issues.apache.org/jira/browse/IGNITE-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4552: Fix Version/s: (was: 2,0) 2.0 > Optimize GridDhtLocalPartition.rmvQueue > --- > > Key: IGNITE-4552 > URL: https://issues.apache.org/jira/browse/IGNITE-4552 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6 >Reporter: Alexei Scherbakov > Fix For: 2.0 > > > Current implementation stores deferred entry removals in rmvQueue for > consistency guaranties. > This can lead to significant heap over-usage(I observed several Gbs) in case > of many caches with removals, because currently queue is cleared lazily after > reaching max capacity(200_000 by default). > This can be mitigated by using lower IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE, > but can lead to consistency issues in case of frequent cache updates. > Possible optimizations: > * Use single fixed size queue per all caches to overcome limitations of > IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE workaround. > * Do queue cleaning in background > * Move queue to an off-heap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4550) Move service deployment to certain test
[ https://issues.apache.org/jira/browse/IGNITE-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-4550: Assignee: Andrew Mashenkov > Move service deployment to certain test > --- > > Key: IGNITE-4550 > URL: https://issues.apache.org/jira/browse/IGNITE-4550 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.8 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Fix For: 1.9 > > > GridCacheAbstractFullApiSelfTest has service deployment in beforeTest() > method. > It look like there is no need to do this for all tests and service deployment > should be moved to testTransformResourceInjection(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4506) Implement thread-per-partition processing for atomic cache updates
[ https://issues.apache.org/jira/browse/IGNITE-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4506: Fix Version/s: (was: 2,0) 2.0 > Implement thread-per-partition processing for atomic cache updates > -- > > Key: IGNITE-4506 > URL: https://issues.apache.org/jira/browse/IGNITE-4506 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Semen Boikov >Assignee: Konstantin Dudkov > Fix For: 2.0 > > > Need implement thread-per-partition processing for atomic cache updates. > For single key requests remote request should be already processed by striped > executor, need fix case when update is mapped on local node - in this case it > is processed from calling thread. > For batched updates need implement per-partition mapping and processing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4363) Inner properties mutation broken in SQL UPDATE
[
https://issues.apache.org/jira/browse/IGNITE-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4363:
Fix Version/s: (was: 2.0)
1.9
> Inner properties mutation broken in SQL UPDATE
> --
>
> Key: IGNITE-4363
> URL: https://issues.apache.org/jira/browse/IGNITE-4363
> Project: Ignite
> Issue Type: Bug
> Components: binary, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 1.9
>
>
> Discovered in course of working on IGNITE-4340.
> Say, we have following type for cache values
> {code:java}
> static final class AllTypes implements Serializable {
> /**
> * Data Long.
> */
> @QuerySqlField
> Long longCol;
> /**
> * Inner type object.
> */
> @QuerySqlField
> InnerType innerTypeCol;
> /** */
> static final class InnerType implements Serializable {
> /** */
> @QuerySqlField
> Long innerLongCol;
> /** */
> @QuerySqlField
> String innerStrCol;
>}
> }
> {code}
> Queries like this fail for both optimized and binary marshaller:
> {code:sql}
> UPDATE AllTypes set innerLongCol = ?
> {code}
> For optimized, current DML implementation mutates existing inner property
> thus confusing DML statements re-run logic (query re-runs because engine sees
> value as concurrently modified, though the only change is its own, and
> ultimately fails). The solution is to clone inner objects and set new
> property values on them because we need to have old value pristine.
> For binary, current DML implementation does not honor properties hierarchy
> and, for above example, just sets {{innerLongCol}} field on {{AllTypes}}
> binary object and not its child {{InnerType}} object. Thus, index will be
> updated and SELECTs for that column will return correct value for that field,
> but inner state of target property {{innerTypeCol}} does not change, and
> {{AllTypes}} object gets its own odd field {{innerLongCol}} which it does not
> know how to do with (no metadata about it in type descriptor).
> The patch for both problems is ready and lying on my shelf waiting for 1.8
> release to happen to be applied. Then this will ultimately be fixed with the
> rest of known problems/improvements (Jira issues for them will follow).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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=15827969#comment-15827969 ] Vladimir Ozerov commented on IGNITE-3315: - [~dmagda], please take a look. > 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: Vladimir Ozerov >Priority: Minor > Labels: cpp, roadmap > 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.4#6332)
[jira] [Updated] (IGNITE-4490) Optimize DML for fast INSERT and MERGE
[
https://issues.apache.org/jira/browse/IGNITE-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4490:
Fix Version/s: (was: 2.0)
1.9
> Optimize DML for fast INSERT and MERGE
> --
>
> Key: IGNITE-4490
> URL: https://issues.apache.org/jira/browse/IGNITE-4490
> Project: Ignite
> Issue Type: Improvement
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 1.9
>
>
> It's possible to avoid any SQL querying and map some INSERT and MERGE
> statements to cache operations in a way similar to that of UPDATE and DELETE
> - i.e. don't make queries when there are no expressions to evaluate in the
> query and enhance update plans to perform direct cache operations when INSERT
> and MERGE affect columns {{_key}} and {{_val}} only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4537) Update Notifier must not transfer system properties
[
https://issues.apache.org/jira/browse/IGNITE-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827967#comment-15827967
]
Dmitry Karachentsev commented on IGNITE-4537:
-
Denis,
I suppose to filter property keys with condition:
{code}
key.startsWith("IGNITE_") || key.startsWith("java.")
|| key.startsWith("sun.") || key.startsWith("os.")
|| key.startsWith("file.") || key.startsWith("user.")
|| "path.separator".equals(key)
{code}
Is it OK or we should make it more strict and hardcode some standard properties?
> Update Notifier must not transfer system properties
> ---
>
> Key: IGNITE-4537
> URL: https://issues.apache.org/jira/browse/IGNITE-4537
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 1.9
>
>
> Apache Ignite Update Notifier that is used for sending updates about new
> Apache Ignite versions gathers and transfers all system properties.
> The script must not do this. Instead, it has to get only those system
> properties like Java version, OS versions that are needed. Otherwise, the
> script might send sensitive information like passwords stored in the system
> properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3837) ODBC: Escape sequences: Support CONVERT function.
[
https://issues.apache.org/jira/browse/IGNITE-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3837:
Fix Version/s: (was: 2.0)
1.9
> ODBC: Escape sequences: Support CONVERT function.
> -
>
> Key: IGNITE-3837
> URL: https://issues.apache.org/jira/browse/IGNITE-3837
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: odbc
> Fix For: 1.9
>
>
> Need to implement parsing of the CONVERT function:
> https://msdn.microsoft.com/en-us/library/ms715381(v=vs.85).aspx.
> Note the type conversion (e.g. {{SQL_VARCHAR}} -> {{VARCHAR}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4219) Hive job submission failed with exception ”java.io.UTFDataFormatException“
[
https://issues.apache.org/jira/browse/IGNITE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4219:
Fix Version/s: (was: 2.0)
1.9
> Hive job submission failed with exception ”java.io.UTFDataFormatException“
> --
>
> Key: IGNITE-4219
> URL: https://issues.apache.org/jira/browse/IGNITE-4219
> Project: Ignite
> Issue Type: Bug
> Components: hadoop
>Reporter: Andrew Mashenkov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 1.9
>
>
> Long property passing to Hadoop causes an exception:
> {code}
> Caused by: java.io.UTFDataFormatException
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:2144)
>
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:1987)
>
>at java.io.ObjectOutputStream.writeUTF(ObjectOutputStream.java:865)
>at
> org.apache.ignite.internal.util.IgniteUtils.writeUTFStringNullable(IgniteUtils.java:5029)
>
>at
> org.apache.ignite.internal.util.IgniteUtils.writeStringMap(IgniteUtils.java:4989)
>
>at
> org.apache.ignite.internal.processors.hadoop.HadoopDefaultJobInfo.writeExternal(HadoopDefaultJobInfo.java:137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3543) IGFS: Merge isRetryForSecondary() and verifyIntegrity() methods.
[
https://issues.apache.org/jira/browse/IGNITE-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3543:
Fix Version/s: (was: 2.0)
1.9
> IGFS: Merge isRetryForSecondary() and verifyIntegrity() methods.
>
>
> Key: IGNITE-3543
> URL: https://issues.apache.org/jira/browse/IGNITE-3543
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.9
>
>
> There are two methods with very similar semantics:
> 1) {{IgfsPathIds.verifyIntegrity}}
> 2) {{IgfsMetaManager.isRetryForSecondary}}
> The latter method ensures that if path is incomplete, then the last existing
> item do not have reference to child with expected name, but unexpected ID.
> Semantically this situation means that concurrent update occurred.
> Instead of heaving two identical methods, we should merge these checks in a
> single method {{IgfsPathIds.verifyIntegrity}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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: Vladimir Ozerov >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.4#6332)
[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 ] Vladimir Ozerov updated IGNITE-3542: Fix Version/s: (was: 2.0) 1.9 > 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: 1.9 > > > 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.4#6332)
[jira] [Commented] (IGNITE-4520) Web console: allow agent to connect through proxy
[
https://issues.apache.org/jira/browse/IGNITE-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827944#comment-15827944
]
Pavel Konstantinov commented on IGNITE-4520:
I found a typo in the documentation - for HTTP you are wrote 'https' in the
shell example.
> Web console: allow agent to connect through proxy
> -
>
> Key: IGNITE-4520
> URL: https://issues.apache.org/jira/browse/IGNITE-4520
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.9
>
>
> We currently assume that web agent will have direct access to console server.
> Sometimes this is not true and any external Internet access is done through
> SOCKS or HTTP proxy, potentially with authentication.
> We should add settings required for proxy (type, address, login, password)
> and implement the support. {{java.net.Proxy}} class can be used for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4520) Web console: allow agent to connect through proxy
[
https://issues.apache.org/jira/browse/IGNITE-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-4520:
---
Assignee: Andrey Novikov (was: Pavel Konstantinov)
> Web console: allow agent to connect through proxy
> -
>
> Key: IGNITE-4520
> URL: https://issues.apache.org/jira/browse/IGNITE-4520
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Andrey Novikov
>Priority: Critical
> Fix For: 1.9
>
>
> We currently assume that web agent will have direct access to console server.
> Sometimes this is not true and any external Internet access is done through
> SOCKS or HTTP proxy, potentially with authentication.
> We should add settings required for proxy (type, address, login, password)
> and implement the support. {{java.net.Proxy}} class can be used for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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 ] Dmitriy Shabalin updated IGNITE-4472: - Assignee: Andrey Novikov (was: Dmitriy Shabalin) > 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: Andrey Novikov > > 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.4#6332)
[jira] [Commented] (IGNITE-4472) Web Console: Implement usage tracing
[ https://issues.apache.org/jira/browse/IGNITE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827870#comment-15827870 ] Dmitriy Shabalin commented on IGNITE-4472: -- Added new events and new logic to output activities data to admin panel > 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 > > 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.4#6332)
[jira] [Updated] (IGNITE-1443) CPP: Implement cache continuous queries.
[ https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1443: Fix Version/s: (was: 2.0) 1.9 > CPP: Implement cache continuous queries. > > > Key: IGNITE-1443 > URL: https://issues.apache.org/jira/browse/IGNITE-1443 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov > Labels: cpp, important, roadmap > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4397) .NET: Support BinaryFieldsIdentityResolver
[ https://issues.apache.org/jira/browse/IGNITE-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827856#comment-15827856 ] Pavel Tupitsyn commented on IGNITE-4397: String, Guid, DateTime done. Only decimals remain. > .NET: Support BinaryFieldsIdentityResolver > -- > > Key: IGNITE-4397 > URL: https://issues.apache.org/jira/browse/IGNITE-4397 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.9 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.0 > > > IGNITE-4045 introduced DML API with Binary resolver as the only option. > Field resolver is partially implemented and hidden. It requires GetHashCode > implementations with Java algorithms for all basic types: > bool, byte/sbyte, short/ushort, char, int/uint, long/ulong, float, double, > string, decimal, Guid, DateTime -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4537) Update Notifier must not transfer system properties
[ https://issues.apache.org/jira/browse/IGNITE-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev reassigned IGNITE-4537: --- Assignee: Dmitry Karachentsev (was: Denis Magda) > Update Notifier must not transfer system properties > --- > > Key: IGNITE-4537 > URL: https://issues.apache.org/jira/browse/IGNITE-4537 > Project: Ignite > Issue Type: Bug >Reporter: Denis Magda >Assignee: Dmitry Karachentsev >Priority: Critical > Fix For: 1.9 > > > Apache Ignite Update Notifier that is used for sending updates about new > Apache Ignite versions gathers and transfers all system properties. > The script must not do this. Instead, it has to get only those system > properties like Java version, OS versions that are needed. Otherwise, the > script might send sensitive information like passwords stored in the system > properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3878) Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent
[ https://issues.apache.org/jira/browse/IGNITE-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827695#comment-15827695 ] Maksim Kozlov commented on IGNITE-3878: --- [~yzhdanov] I'm fix this comment. What is meant by "more test cases", ex. add test which read data from backup node? > Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent > -- > > Key: IGNITE-3878 > URL: https://issues.apache.org/jira/browse/IGNITE-3878 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Maksim Kozlov >Priority: Minor > > In some cases useful know where (on primary or backup nodes) was invoked a > continuous query filter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3878) Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent
[ https://issues.apache.org/jira/browse/IGNITE-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827695#comment-15827695 ] Maksim Kozlov edited comment on IGNITE-3878 at 1/18/17 9:18 AM: [~yzhdanov] I'm fix this comment PR. What is meant by "more test cases", ex. add test which read data from backup node? was (Author: dreamx): [~yzhdanov] I'm fix this comment. What is meant by "more test cases", ex. add test which read data from backup node? > Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent > -- > > Key: IGNITE-3878 > URL: https://issues.apache.org/jira/browse/IGNITE-3878 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Maksim Kozlov >Priority: Minor > > In some cases useful know where (on primary or backup nodes) was invoked a > continuous query filter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4525) Near reader is not created when value is loaded from store
[ https://issues.apache.org/jira/browse/IGNITE-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev resolved IGNITE-4525. - Resolution: Fixed > Near reader is not created when value is loaded from store > -- > > Key: IGNITE-4525 > URL: https://issues.apache.org/jira/browse/IGNITE-4525 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.8 >Reporter: Valentin Kulichenko >Assignee: Dmitry Karachentsev > Fix For: 2.0 > > Attachments: NearCacheTest.java > > > When client with a near cache get value that is not in cache yet, it's loaded > from store and the value is saved in near cache. However reader on primary > node is not created, and when it's updated on server side, near cache is not > synchronized. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827681#comment-15827681
]
Pavel Tupitsyn commented on IGNITE-4045:
Sure, IGNITE-4556 created.
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Reporter: Denis Magda
> Labels: roadmap
> Fix For: 1.9
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready
> (https://apacheignite.readme.io/docs/distributed-dml).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4556) .NET: DML documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-4556:
---
Description:
See [~dmagda] comment in IGNITE-4045:
{code}
In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
for Java and document only those pieces that are related to .NET. For the rest
you can refer to Java doc from .NET doc.
In addition, it will be great if you add a DML example similar to the one we
have in Java.
{code}
was:
See [~dmagda] comment in IGNITE-4045:
{code}
In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
for Java and document only those pieces that are related to .NET. For the rest
you can refer to Java doc from .NET doc.
In addition, it will be great if you add a DML example similar to the one we
have in Java.
{code}
> .NET: DML documentation and example
> ---
>
> Key: IGNITE-4556
> URL: https://issues.apache.org/jira/browse/IGNITE-4556
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, DML
> Fix For: 1.9
>
>
> See [~dmagda] comment in IGNITE-4045:
> {code}
> In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
> for Java and document only those pieces that are related to .NET. For the
> rest you can refer to Java doc from .NET doc.
> In addition, it will be great if you add a DML example similar to the one we
> have in Java.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4556) .NET: DML documentation and example
Pavel Tupitsyn created IGNITE-4556:
--
Summary: .NET: DML documentation and example
Key: IGNITE-4556
URL: https://issues.apache.org/jira/browse/IGNITE-4556
Project: Ignite
Issue Type: Improvement
Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 1.9
See [~dmagda] comment in IGNITE-4045:
{code}
In general, it makes sense to introduce SQL Grid paragraph in .NET as we did
for Java and document only those pieces that are related to .NET. For the rest
you can refer to Java doc from .NET doc.
In addition, it will be great if you add a DML example similar to the one we
have in Java.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
