[jira] [Commented] (IGNITE-12234) .NET: Fix flaky tests
[
https://issues.apache.org/jira/browse/IGNITE-12234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938054#comment-16938054
]
Ignite TC Bot commented on IGNITE-12234:
{panel:title=Branch: [pull/6914/head] Base: [master] : Possible Blockers
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4635513]]
{color:#d04437}RDD{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4635469]]
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4635509]]
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxOptimisticRepeatableRead -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cassandra Store{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4635556]]
* IgniteCassandraStoreTestSuite:
CassandraDirectPersistenceTest.pojoStrategyTest - Test has low fail rate in
base branch 0,0% and is not flaky
* IgniteCassandraStoreTestSuite:
CassandraDirectPersistenceTest.pojoStrategyTransactionTest - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4635559buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Fix flaky tests
> -
>
> Key: IGNITE-12234
> URL: https://issues.apache.org/jira/browse/IGNITE-12234
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Known flaky tests:
> * CacheTestSsl.TestAsyncCompletionOrder
> * DataStorageMetricsTest.TestDataStorageMetrics
> * PersistenceTest.TestBaselineTopology
> * CancellationTest.TestTask
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9638) .NET: JVM keeps track of CLR Threads, even when they are finished
[
https://issues.apache.org/jira/browse/IGNITE-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938042#comment-16938042
]
Ignite TC Bot commented on IGNITE-9638:
---
{panel:title=Branch: [pull/6912/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4635271]]
{color:#d04437}Client Nodes{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4635208]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4635317buildTypeId=IgniteTests24Java8_RunAll]
> .NET: JVM keeps track of CLR Threads, even when they are finished
> --
>
> Key: IGNITE-9638
> URL: https://issues.apache.org/jira/browse/IGNITE-9638
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.8
>
> Attachments: IgniteRepro.zip
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When you create a Thread in C#, JVM creates corresponding thread
> "Thread-" which is visible in jstack. When C# joins this thread, it is
> not removed from JVM and is kept around. This means that jstack may show
> thousands of threads which are not there. Reproducer is attached. It is
> presumed that memory will be exhausted eventually.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12178) DEBUG logging may throw exception from toString of tx objects
[
https://issues.apache.org/jira/browse/IGNITE-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938007#comment-16938007
]
Denis Magda commented on IGNITE-12178:
--
A similar issue was reported on the user list:
http://apache-ignite-users.70518.x6.nabble.com/Exception-during-exception-handling-td29464.html
> DEBUG logging may throw exception from toString of tx objects
> -
>
> Key: IGNITE-12178
> URL: https://issues.apache.org/jira/browse/IGNITE-12178
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> See
> https://stackoverflow.com/questions/57727242/apache-ignite-failed-to-create-string-representation-of-binary-object
> {code:java}
> 0
> I am getting below exception and not able to figure out what is wrong with
> the code.
> I have simplified my pojo classes which are to be persisted to ignite cache,
> but still the complexity remains.
> All my pojos are serializable but few of them have business logic code, dao,
> application context object. These objects can't be removed. Removing these
> things from the code will require whole code refractoring.
> class org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1022)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:864)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearSingleGetResponse.toString(GridNearSingleGetResponse.java:317)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1162)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1209)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:1003)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:938)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetRequest(GridDhtCacheAdapter.java:938)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$300(GridDhtAtomicCache.java:135)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$4.apply(GridDhtAtomicCache.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$4.apply(GridDhtAtomicCache.java:252)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:189)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.toString(BinaryObjectImpl.java:920)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
>
[jira] [Created] (IGNITE-12234) .NET: Fix flaky tests
Pavel Tupitsyn created IGNITE-12234: --- Summary: .NET: Fix flaky tests Key: IGNITE-12234 URL: https://issues.apache.org/jira/browse/IGNITE-12234 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Known flaky tests: * CacheTestSsl.TestAsyncCompletionOrder * DataStorageMetricsTest.TestDataStorageMetrics * PersistenceTest.TestBaselineTopology * CancellationTest.TestTask -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9638) .NET: JVM keeps track of CLR Threads, even when they are finished
[ https://issues.apache.org/jira/browse/IGNITE-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937882#comment-16937882 ] Igor Sapego commented on IGNITE-9638: - [~ptupitsyn] Looks good to me. > .NET: JVM keeps track of CLR Threads, even when they are finished > -- > > Key: IGNITE-9638 > URL: https://issues.apache.org/jira/browse/IGNITE-9638 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.6 >Reporter: Ilya Kasnacheev >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.8 > > Attachments: IgniteRepro.zip > > Time Spent: 0.5h > Remaining Estimate: 0h > > When you create a Thread in C#, JVM creates corresponding thread > "Thread-" which is visible in jstack. When C# joins this thread, it is > not removed from JVM and is kept around. This means that jstack may show > thousands of threads which are not there. Reproducer is attached. It is > presumed that memory will be exhausted eventually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12233) Merge benchmarks sql index benchmarks from ignite-2.7 to master
[ https://issues.apache.org/jira/browse/IGNITE-12233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937857#comment-16937857 ] Ilya Suntsov commented on IGNITE-12233: --- https://github.com/apache/ignite/pull/6913 > Merge benchmarks sql index benchmarks from ignite-2.7 to master > --- > > Key: IGNITE-12233 > URL: https://issues.apache.org/jira/browse/IGNITE-12233 > Project: Ignite > Issue Type: Task > Components: yardstick >Reporter: Ilya Suntsov >Assignee: Ilya Suntsov >Priority: Major > > The following benchmarks are missed in master but exist in ignite-2.7: > * IgniteSqlUpdateFilteredBenchmark > * IgniteSqlInsertIndexedValue1Benchmark > * IgniteSqlInsertIndexedValue2Benchmark > * IgniteSqlInsertIndexedValue8Benchmark -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.
[
https://issues.apache.org/jira/browse/IGNITE-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937849#comment-16937849
]
Vyacheslav Koptilin commented on IGNITE-11868:
--
Hi [~kcheng.mvp], thanks for the contribution!
Hi [~ivan.glukos], could you please take a look and merge the change?
> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and
> therefore it can be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
[ https://issues.apache.org/jira/browse/IGNITE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937837#comment-16937837 ] Stepan Pilschikov commented on IGNITE-11008: [~kcheng.mvp] Thanks for contribution. I definitely a wrong person to help in PR process or TC things. Better to ask [~Mmuzaf] or Ignite dev list > JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH > -- > > Key: IGNITE-11008 > URL: https://issues.apache.org/jira/browse/IGNITE-11008 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: kcheng.mvp >Priority: Minor > Fix For: 2.8 > > > Found redundant spaces in > org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns > "IS_GENERATEDCOLUMN " > "BUFFER_LENGTH " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9638) .NET: JVM keeps track of CLR Threads, even when they are finished
[ https://issues.apache.org/jira/browse/IGNITE-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-9638: --- Release Note: .NET: Fixed JVM thread local leak > .NET: JVM keeps track of CLR Threads, even when they are finished > -- > > Key: IGNITE-9638 > URL: https://issues.apache.org/jira/browse/IGNITE-9638 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.6 >Reporter: Ilya Kasnacheev >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.8 > > Attachments: IgniteRepro.zip > > Time Spent: 0.5h > Remaining Estimate: 0h > > When you create a Thread in C#, JVM creates corresponding thread > "Thread-" which is visible in jstack. When C# joins this thread, it is > not removed from JVM and is kept around. This means that jstack may show > thousands of threads which are not there. Reproducer is attached. It is > presumed that memory will be exhausted eventually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-10113) Failure during build index isn't handled by failure handler
[
https://issues.apache.org/jira/browse/IGNITE-10113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937829#comment-16937829
]
Ignite TC Bot commented on IGNITE-10113:
{panel:title=Branch: [pull/6801/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC PDS 4{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4633590]]
* IgnitePdsMvccTestSuite4: ResetLostPartitionTest.testResetLostPartitions -
Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsMvccTestSuite4:
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 8{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4633592]]
* IgniteCacheTestSuite8:
GridCacheRebalancingAsyncSelfTest.testComplexRebalancing - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}MVCC Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4633594]]
* IgniteCacheMvccTestSuite7:
GridCacheRebalancingWithAsyncClearingMvccTest.testPartitionClearingNotBlockExchange
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4601030buildTypeId=IgniteTests24Java8_RunAll]
> Failure during build index isn't handled by failure handler
> ---
>
> Key: IGNITE-10113
> URL: https://issues.apache.org/jira/browse/IGNITE-10113
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Sergey Antonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
> Attachments: StopNodeOnRebuildIndexFailureTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If exception will be thrown during index build, failure handler doesn't
> handle this exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9638) .NET: JVM keeps track of CLR Threads, even when they are finished
[ https://issues.apache.org/jira/browse/IGNITE-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937828#comment-16937828 ] Pavel Tupitsyn commented on IGNITE-9638: [~isapego] PR ready, please have a look. > .NET: JVM keeps track of CLR Threads, even when they are finished > -- > > Key: IGNITE-9638 > URL: https://issues.apache.org/jira/browse/IGNITE-9638 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.6 >Reporter: Ilya Kasnacheev >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.8 > > Attachments: IgniteRepro.zip > > Time Spent: 0.5h > Remaining Estimate: 0h > > When you create a Thread in C#, JVM creates corresponding thread > "Thread-" which is visible in jstack. When C# joins this thread, it is > not removed from JVM and is kept around. This means that jstack may show > thousands of threads which are not there. Reproducer is attached. It is > presumed that memory will be exhausted eventually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12225) Add enum for cluster state
[
https://issues.apache.org/jira/browse/IGNITE-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov updated IGNITE-12225:
Description:
We have 3 cluster states at the moment: inactive, active, read-only.
For getting current cluster state and changing them {{IgniteCluster}} has
methods:
* {{boolean active()}}, {{void active(boolean active)}} - for cluster
activation/deactivation
* {{boolean readOnly()}}, {{void readOnly(boolean readOnly)}} - for
enabling/disabling read-only mode.
Also we have control.sh commans for changing cluster state:
* {{--activate}}
* {{--deactivate}}
* {{--read-only-on}}
* {{--read-only-off}}
For me current API looks unuseful. My proposal:
# Create enum {{ClusterState}} with values {{ACTIVE}}, {{INACTIVE}},
{{READ-ONLY}}.
# Add methods to {{IgniteCluster}}:
#* {{ClusterState state()}} returns current cluster state
#* {{void state(ClusterState newState)}} changes cluster state to {{newState}}
state
# Mark as deprecated the following methods in {{IgniteCluster}}: {{boolean
active()}}, {{void active(boolean active)}},
# Add new command to control.sh: {{control.sh --set-state
(ACTIVE|INACTIVE|READ-ONLY)}} [--yes]
# Add warn message that command is depricated in control.sh. Commands:
--activate, --deactivate,
# Remove commands from control.sh: --read-only-on, --read-only-off (no one
release wasn't published with this functional)
was:
We have 3 cluster states at the moment: inactive, active, read-only.
For getting current cluster state and changing them {{IgniteCluster}} has
methods:
* {{boolean active()}}, {{void active(boolean active)}} - for cluster
activation/deactivation
* {{boolean readOnly()}}, {{void readOnly(boolean readOnly)}} - for
enabling/disabling read-only mode.
Also we have control.sh commans for changing cluster state:
* {{--activate}}
* {{--deactivate}}
* {{--read-only-on}}
* {{--read-only-off}}
For me current API looks unuseful. My proposal:
# Create enum {{ClusterState}} with values {{ACTIVE}}, {{INACTIVE}},
{{READ-ONLY}}.
# Add methods to {{IgniteCluster}}:
#* {{ClusterState state()}} returns current cluster state
#* {{void state(ClusterState newState)}} changes cluster state to {{newState}}
state
# Mark as deprecated the following methods in {{IgniteCluster}}: {{boolean
active()}}, {{void active(boolean active)}},
# Add new command to control.sh: {{control.sh --set-state
(ACTIVE|INACTIVE|READ-ONLY)}} [--yes]
# Add warn message that command is depricated in control.sh. Commands:
--activate, --deactivate, --read-only-on, --read-only-off
> Add enum for cluster state
> --
>
> Key: IGNITE-12225
> URL: https://issues.apache.org/jira/browse/IGNITE-12225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
>
> We have 3 cluster states at the moment: inactive, active, read-only.
> For getting current cluster state and changing them {{IgniteCluster}} has
> methods:
> * {{boolean active()}}, {{void active(boolean active)}} - for cluster
> activation/deactivation
> * {{boolean readOnly()}}, {{void readOnly(boolean readOnly)}} - for
> enabling/disabling read-only mode.
> Also we have control.sh commans for changing cluster state:
> * {{--activate}}
> * {{--deactivate}}
> * {{--read-only-on}}
> * {{--read-only-off}}
> For me current API looks unuseful. My proposal:
> # Create enum {{ClusterState}} with values {{ACTIVE}}, {{INACTIVE}},
> {{READ-ONLY}}.
> # Add methods to {{IgniteCluster}}:
> #* {{ClusterState state()}} returns current cluster state
> #* {{void state(ClusterState newState)}} changes cluster state to
> {{newState}} state
> # Mark as deprecated the following methods in {{IgniteCluster}}: {{boolean
> active()}}, {{void active(boolean active)}},
> # Add new command to control.sh: {{control.sh --set-state
> (ACTIVE|INACTIVE|READ-ONLY)}} [--yes]
> # Add warn message that command is depricated in control.sh. Commands:
> --activate, --deactivate,
> # Remove commands from control.sh: --read-only-on, --read-only-off (no one
> release wasn't published with this functional)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12226) Improve BinaryObjectException message
[
https://issues.apache.org/jira/browse/IGNITE-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937819#comment-16937819
]
Yury Gerzhedovich commented on IGNITE-12226:
[~ktkale...@gridgain.com], the path looks ok.
> Improve BinaryObjectException message
> -
>
> Key: IGNITE-12226
> URL: https://issues.apache.org/jira/browse/IGNITE-12226
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are getting the following exception in case of different type IDs:
> {noformat}
> org.apache.ignite.binary.BinaryObjectException: Failed to get field because
> type ID of passed object differs from type ID this BinaryField belongs to
> [expected=-635374417, actual=1778229603]
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:109)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:220)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:116)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2RowDescriptor.columnValue(GridH2RowDescriptor.java:331)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue0(GridH2KeyValueRowOnheap.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue(GridH2KeyValueRowOnheap.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:350)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:56)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:4614)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:4534)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$1300(BPlusTree.java:92)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:296)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4967)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:276)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4952)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:348)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2450)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2203)
> {noformat}
> This message isn't informative. We should print more detailes about types,
> for example classname, class structure (if applicable), which field in class
> we tried to read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided
[
https://issues.apache.org/jira/browse/IGNITE-11976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937818#comment-16937818
]
Ignite TC Bot commented on IGNITE-11976:
{panel:title=Branch: [pull/6868/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4617661buildTypeId=IgniteTests24Java8_RunAll]
> @SpringResource is silently ignored if no Spring context is provided
>
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
> Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is
> null if Spring context.
> For @SpringResource to work the node needs to be started with
> IgniteSpring::start instead of Ignition::start, but the user may not know
> that.
> Need to add a warning for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.
[
https://issues.apache.org/jira/browse/IGNITE-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937809#comment-16937809
]
kcheng.mvp commented on IGNITE-11868:
-
[~slava.koptilin] TeamCity is green
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BuildApacheIgnite_IgniteTests24Java8=pull%2F6868%2Fhead=buildTypeStatusDiv
Can you help do the further process.
Thanks
> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and
> therefore it can be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12108) [IEP-35] Migrate Communication Metrics.
[ https://issues.apache.org/jira/browse/IGNITE-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937804#comment-16937804 ] Ivan Bessonov commented on IGNITE-12108: Hello [~NIzhikov], I updated the code according to your suggestions, please check it one more time. > [IEP-35] Migrate Communication Metrics. > --- > > Key: IGNITE-12108 > URL: https://issues.apache.org/jira/browse/IGNITE-12108 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 3h 50m > Remaining Estimate: 0h > > ||*Name*||*Description*|| > |communication.tcp.outboundMessagesQueueSize|Number of messages waiting to be > sent| > |communication.tcp.sentBytes|Total number of bytes received by current node| > |communication.tcp.receivedBytes|Total number of bytes sent by current node| > |communication.tcp.sentMessagesCount|Total number of messages sent by current > node| > |communication.tcp.receivedMessagesCount|Total number of messages received by > current node| > |communication.tcp.sentMessagesByType.|Total number of messages > with given type sent by current node| > |communication.tcp.receivedMessagesByType.|Total number of > messages with given type received by current node| > |communication.tcp..sentMessagesToNode|Total number of messages sent > by current node to the given node| > |communication.tcp..receivedMessagesFromNode|Total number of messages > received by current node from the given node| > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10292) ML: Replace IGFS by model storage for TensorFlow
[ https://issues.apache.org/jira/browse/IGNITE-10292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10292: - Assignee: Aleksey Zinoviev > ML: Replace IGFS by model storage for TensorFlow > > > Key: IGNITE-10292 > URL: https://issues.apache.org/jira/browse/IGNITE-10292 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Anton Dmitriev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Currently we have a TensorFlow IGFS plugin that provides a file system > functionality (see > https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/ignite). > At the same time IGFS is deprecated and would be great to replace it by a > simple model storage based on cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12233) Merge benchmarks sql index benchmarks from ignite-2.7 to master
[ https://issues.apache.org/jira/browse/IGNITE-12233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-12233: -- Description: The following benchmarks are missed in master but exist in ignite-2.7: * IgniteSqlUpdateFilteredBenchmark * IgniteSqlInsertIndexedValue1Benchmark * IgniteSqlInsertIndexedValue2Benchmark * IgniteSqlInsertIndexedValue8Benchmark was: The following benchmarks are missed in master but exist in ignite-2.7: * IgniteSqlMergeIndexedValue1Benchmark * IgniteSqlMergeIndexedValue2Benchmark * IgniteSqlMergeIndexedValue8Benchmark * IgniteSqlDeleteFilteredBenchmark * IgniteSqlUpdateBenchmark * IgniteSqlUpdateFilteredBenchmark * IgniteSqlInsertIndexedValue1Benchmark * IgniteSqlInsertIndexedValue2Benchmark * IgniteSqlInsertIndexedValue8Benchmark > Merge benchmarks sql index benchmarks from ignite-2.7 to master > --- > > Key: IGNITE-12233 > URL: https://issues.apache.org/jira/browse/IGNITE-12233 > Project: Ignite > Issue Type: Task > Components: yardstick >Reporter: Ilya Suntsov >Assignee: Ilya Suntsov >Priority: Major > > The following benchmarks are missed in master but exist in ignite-2.7: > * IgniteSqlUpdateFilteredBenchmark > * IgniteSqlInsertIndexedValue1Benchmark > * IgniteSqlInsertIndexedValue2Benchmark > * IgniteSqlInsertIndexedValue8Benchmark -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12232) NPE while node join processing
[ https://issues.apache.org/jira/browse/IGNITE-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-12232: --- Assignee: Ryabov Dmitrii > NPE while node join processing > -- > > Key: IGNITE-12232 > URL: https://issues.apache.org/jira/browse/IGNITE-12232 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: PetrovMikhail >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > > ServerImpl.RingMessageWorker#processNodeAddedMessage method throws npe > exception in case DiscoverySpiNodeAuthenticator#authenticateNode returns null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12079) [ML][Umbrella] Add advanced preprocessing techniques
[ https://issues.apache.org/jira/browse/IGNITE-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-12079: -- Priority: Major (was: Blocker) > [ML][Umbrella] Add advanced preprocessing techniques > > > Key: IGNITE-12079 > URL: https://issues.apache.org/jira/browse/IGNITE-12079 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > *Main goal:* > To reduce the gap between Apache Spark and Apache Ignite in preprocessing > operations. The reducing of the gap could help with loading Spark ML > Pipelines to Ignite ML. > > Next steps: > # Add Frequency Encoder > # Add two Imputing Strategies (MIN, MAX, COUNT, MOST_FREQUENT, > LEAST_FREQUENT) > # Add RobustScaler (will be added in Spark 3.0) > # Add CountVectorizer > # Add FeatureHasher > # Add QuantileDiscretizer > # Add Locality Sensitive Hashing (LSH) > # Add LabelEncoder > # Add RevertStringIndexing > # Add multi-column preprocessor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12232) NPE while node join processing
[ https://issues.apache.org/jira/browse/IGNITE-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PetrovMikhail updated IGNITE-12232: --- Affects Version/s: 2.7.6 > NPE while node join processing > -- > > Key: IGNITE-12232 > URL: https://issues.apache.org/jira/browse/IGNITE-12232 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: PetrovMikhail >Priority: Major > > ServerImpl.RingMessageWorker#processNodeAddedMessage method throws npe > exception in case DiscoverySpiNodeAuthenticator#authenticateNode returns null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12232) NPE while node join processing
[ https://issues.apache.org/jira/browse/IGNITE-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PetrovMikhail updated IGNITE-12232: --- Fix Version/s: 2.8 > NPE while node join processing > -- > > Key: IGNITE-12232 > URL: https://issues.apache.org/jira/browse/IGNITE-12232 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: PetrovMikhail >Priority: Major > Fix For: 2.8 > > > ServerImpl.RingMessageWorker#processNodeAddedMessage method throws npe > exception in case DiscoverySpiNodeAuthenticator#authenticateNode returns null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12233) Merge benchmarks sql index benchmarks from ignite-2.7 to master
Ilya Suntsov created IGNITE-12233: - Summary: Merge benchmarks sql index benchmarks from ignite-2.7 to master Key: IGNITE-12233 URL: https://issues.apache.org/jira/browse/IGNITE-12233 Project: Ignite Issue Type: Task Components: yardstick Reporter: Ilya Suntsov Assignee: Ilya Suntsov The following benchmarks are missed in master but exist in ignite-2.7: * IgniteSqlMergeIndexedValue1Benchmark * IgniteSqlMergeIndexedValue2Benchmark * IgniteSqlMergeIndexedValue8Benchmark * IgniteSqlDeleteFilteredBenchmark * IgniteSqlUpdateBenchmark * IgniteSqlUpdateFilteredBenchmark * IgniteSqlInsertIndexedValue1Benchmark * IgniteSqlInsertIndexedValue2Benchmark * IgniteSqlInsertIndexedValue8Benchmark -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12232) NPE while node join processing
PetrovMikhail created IGNITE-12232: -- Summary: NPE while node join processing Key: IGNITE-12232 URL: https://issues.apache.org/jira/browse/IGNITE-12232 Project: Ignite Issue Type: Bug Reporter: PetrovMikhail ServerImpl.RingMessageWorker#processNodeAddedMessage method throws npe exception in case DiscoverySpiNodeAuthenticator#authenticateNode returns null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12197) Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
[
https://issues.apache.org/jira/browse/IGNITE-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937738#comment-16937738
]
Ignite TC Bot commented on IGNITE-12197:
{panel:title=Branch: [pull/6879/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4629976buildTypeId=IgniteTests24Java8_RunAll]
> Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
> --
>
> Key: IGNITE-12197
> URL: https://issues.apache.org/jira/browse/IGNITE-12197
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> IGNITE-12027 introduces possible bug due to incorrect way for getting value
> of persistent enabled property in {{CacheGroupMetricsImpl}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12197) Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
[
https://issues.apache.org/jira/browse/IGNITE-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-12197:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
> --
>
> Key: IGNITE-12197
> URL: https://issues.apache.org/jira/browse/IGNITE-12197
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> IGNITE-12027 introduces possible bug due to incorrect way for getting value
> of persistent enabled property in {{CacheGroupMetricsImpl}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937715#comment-16937715 ] Aleksey Zinoviev edited comment on IGNITE-12054 at 9/25/19 1:37 PM: I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was refactored here [https://github.com/apache/spark/commit/f38ea00e83099a5ae8d3afdec2e896e43c2db612] and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] Also this question is considered in paper [https://www.waitingforcode.com/apache-spark-sql/writing-custom-external-catalog-listeners-apache-spark-sql/read] was (Author: zaleslaw): I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was refactored here [https://github.com/apache/spark/commit/f38ea00e83099a5ae8d3afdec2e896e43c2db612] and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Aleksey Zinoviev >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937737#comment-16937737 ] Aleksey Zinoviev commented on IGNITE-12054: --- I've added a PR with compiled version (the previous issue was resolved) [https://github.com/apache/ignite/pull/6909] But a few example and tests are broken. > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Aleksey Zinoviev >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-12054: - Assignee: Aleksey Zinoviev (was: Nikolay Izhikov) > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Aleksey Zinoviev >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937715#comment-16937715 ] Aleksey Zinoviev edited comment on IGNITE-12054 at 9/25/19 1:19 PM: I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was refactored here [https://github.com/apache/spark/commit/f38ea00e83099a5ae8d3afdec2e896e43c2db612] and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] was (Author: zaleslaw): I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was [link title|[https://github.com/apache/spark/commit/f38ea00e83099a5ae8d3afdec2e896e43c2db612]] and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Nikolay Izhikov >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937715#comment-16937715 ] Aleksey Zinoviev edited comment on IGNITE-12054 at 9/25/19 1:18 PM: I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was [link title|[https://github.com/apache/spark/commit/f38ea00e83099a5ae8d3afdec2e896e43c2db612]] and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] was (Author: zaleslaw): I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was [refactored |[https://github.com/apache/spark/commit/f38ea00e83099a5ae8d3afdec2e896e43c2db612]]and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Nikolay Izhikov >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937715#comment-16937715 ] Aleksey Zinoviev edited comment on IGNITE-12054 at 9/25/19 1:18 PM: I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was [refactored |[https://github.com/apache/spark/commit/f38ea00e83099a5ae8d3afdec2e896e43c2db612]]and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] was (Author: zaleslaw): I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was refactored and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Nikolay Izhikov >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937715#comment-16937715 ] Aleksey Zinoviev edited comment on IGNITE-12054 at 9/25/19 1:16 PM: I've started the R about 2.4 version, fixed a few minor changes and posted here a few thoughts about current problems here, in Jira comments. An ExternalCatalog was refactored and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] was (Author: zaleslaw): An ExternalCatalog was refactored and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Nikolay Izhikov >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937715#comment-16937715 ] Aleksey Zinoviev commented on IGNITE-12054: --- An ExternalCatalog was refactored and all listener properties were inherited in ExternalCatalogWithListener. Nobody yet inherited from this class on Github, the known implementations are HiveExternalCatalog and MemoryExternalCatalog (both of them doesn't support listeners and events) Also, people in Spark ML couldn't solve the same problem [http://mail-archives.apache.org/mod_mbox/spark-issues/201812.mbox/%3cjira.13144856.1520975543000.147283.1544598241...@atlassian.jira%3E] > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Nikolay Izhikov >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12231) RollbackRecord's must be flushed after logging to WAL
Andrey Gura created IGNITE-12231:
Summary: RollbackRecord's must be flushed after logging to WAL
Key: IGNITE-12231
URL: https://issues.apache.org/jira/browse/IGNITE-12231
Project: Ignite
Issue Type: Improvement
Reporter: Andrey Gura
Assignee: Andrey Gura
Fix For: 2.8
Every record or records batch logged to WAL must call {{wal().flush()}} in
order to save data on storage device.
{{TxPartitionCounterStateOnePrimaryTwoBackupsHistoryRebalanceTest.testPartialPrepare_2TX_1_1}}
test fails periodically with disabled MMAP.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12230) Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption
[ https://issues.apache.org/jira/browse/IGNITE-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937693#comment-16937693 ] Stepachev Maksim commented on IGNITE-12230: --- [~Pavlukhin], It isn't related. > Partition eviction during cache stop / deactivation may cause errors leading > to node failure and storage corruption > --- > > Key: IGNITE-12230 > URL: https://issues.apache.org/jira/browse/IGNITE-12230 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > PartitionEvictionTask may produce NullPointerException if cache / cache group > / cluser is stopping / deactivating. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lev Agafonov updated IGNITE-12032:
--
Issue Type: Improvement (was: Bug)
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Assignee: Lev Agafonov
>Priority: Minor
> Labels: newbie, usability
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11868) GridClient#data() should be deprecated/removed.
[
https://issues.apache.org/jira/browse/IGNITE-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11868:
-
Fix Version/s: 2.8
> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and
> therefore it can be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-10574) [ML] Design API for Ensemble Training
[ https://issues.apache.org/jira/browse/IGNITE-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10574: - Assignee: Aleksey Zinoviev > [ML] Design API for Ensemble Training > - > > Key: IGNITE-10574 > URL: https://issues.apache.org/jira/browse/IGNITE-10574 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Major > > Currently, we have bagging and boosting. And for boosting we have the > separate trainer(GDBTrainer), but for bagging, we have the static method > inside TrainerTransformers class. We should choose what approach is better > for us. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10843) [ML] In stacking add filter on features kept.
[ https://issues.apache.org/jira/browse/IGNITE-10843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10843: - Assignee: Aleksey Zinoviev > [ML] In stacking add filter on features kept. > - > > Key: IGNITE-10843 > URL: https://issues.apache.org/jira/browse/IGNITE-10843 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Aleksey Zinoviev >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10419) [ML] Move person dataset to SandboxMLCache class
[ https://issues.apache.org/jira/browse/IGNITE-10419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10419: - Assignee: Aleksey Zinoviev > [ML] Move person dataset to SandboxMLCache class > > > Key: IGNITE-10419 > URL: https://issues.apache.org/jira/browse/IGNITE-10419 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Major > Labels: examples > Fix For: 2.8 > > > How we have duplicated code in examples, simple cache with several Person > records. We should move this cache creation code into SandboxMLCache class -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10539) [ML] Make 'with' methods consistent
[ https://issues.apache.org/jira/browse/IGNITE-10539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10539: - Assignee: Aleksey Zinoviev > [ML] Make 'with' methods consistent > --- > > Key: IGNITE-10539 > URL: https://issues.apache.org/jira/browse/IGNITE-10539 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Aleksey Zinoviev >Priority: Major > > In some places we have 'with*' methods making inplace changes and returning > object itself (for example MLPTrainer::withLoss) while in other places we > have them creating new instances with corresponding parameter changed (for > example DatasetBuilder::withFilter, > DatasetBuilder::withUpstreamTrainsformer). This inconsistency makes user look > into javadoc each time and worsens overall API consistensy level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12229) Column not found when using CASE named column from result
[
https://issues.apache.org/jira/browse/IGNITE-12229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937687#comment-16937687
]
Ilya Kasnacheev commented on IGNITE-12229:
--
With local=true it does not seem to work either.
> Column not found when using CASE named column from result
> -
>
> Key: IGNITE-12229
> URL: https://issues.apache.org/jira/browse/IGNITE-12229
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.7.6
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> Consider the following SQL:
> {code}
> create table main (key varchar primary key, val int, grouper int);
> create table joiner (key varchar primary key, value int, grouper int);
> select m.key, case when m.grouper > j.grouper then 1 else -1 end d_grouper
> from main m join joiner j on m.key = j.key where d_grouper = 1 order by
> d_grouper;
> {code}
> Expected behavior - success.
> Observed behavior:
> {code}
> [20:31:13,498][SEVERE][jdbc-request-handler-worker-#1828][JdbcRequestHandler]
> Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
> [schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select m.key, case when
> m.grouper > j.grouper then 1 else -1 end d_grouper from main m join joiner j
> on m.key = j.key where d_grouper = 1 order by d_grouper, args=[],
> stmtType=ANY_STATEMENT_TYPE, autoCommit=true]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to parse query. Столбец "D_GROUPER" не найден
> Column "D_GROUPER" not found; SQL statement:
> select m.key, case when m.grouper > j.grouper then 1 else -1 end d_grouper
> from main m join joiner j on m.key = j.key where d_grouper = 1 order by
> d_grouper [42122-197]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2653)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:2356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2196)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2128)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2123)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2693)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2137)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Столбец "D_GROUPER" не найден
> Column "D_GROUPER" not found; SQL statement:
> select m.key, case when m.grouper > j.grouper then 1 else -1 end d_grouper
> from main m join joiner j on m.key = j.key where d_grouper = 1 order by
> d_grouper [42122-197]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at
> org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:150)
> at org.h2.expression.Comparison.optimize(Comparison.java:177)
> at org.h2.expression.ConditionAndOr.optimize(ConditionAndOr.java:130)
> at org.h2.command.dml.Select.prepare(Select.java:861)
> at org.h2.command.Parser.prepareCommand(Parser.java:283)
> at org.h2.engine.Session.prepareLocal(Session.java:611)
> at org.h2.engine.Session.prepareCommand(Session.java:549)
> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1247)
> at
> org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:76)
> at
> org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:694)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:539)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:509)
> at
>
[jira] [Assigned] (IGNITE-10527) [ML] DenseMatrix(double[] mtx, int rows) mixes args
[ https://issues.apache.org/jira/browse/IGNITE-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10527: - Assignee: Aleksey Zinoviev > [ML] DenseMatrix(double[] mtx, int rows) mixes args > --- > > Key: IGNITE-10527 > URL: https://issues.apache.org/jira/browse/IGNITE-10527 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Artem Malykh >Assignee: Aleksey Zinoviev >Priority: Major > > this(mtx, StorageConstants.ROW_STORAGE_MODE, rows) -> > this(mtx, rows, StorageConstants.ROW_STORAGE_MODE); -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10481) [ML] Examples of stacking usage
[ https://issues.apache.org/jira/browse/IGNITE-10481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10481: - Assignee: Aleksey Zinoviev > [ML] Examples of stacking usage > --- > > Key: IGNITE-10481 > URL: https://issues.apache.org/jira/browse/IGNITE-10481 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-4449) Document the usage of CacheKeyConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937678#comment-16937678
]
Ilya Kasnacheev commented on IGNITE-4449:
-
:(
> Document the usage of CacheKeyConfiguration
> ---
>
> Key: IGNITE-4449
> URL: https://issues.apache.org/jira/browse/IGNITE-4449
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Magda
>Priority: Major
>
> {{CacheKeyConfiguration}} is used for scenarios when an affinity field has to
> be specified for a key. It's one of the alternatives to {{AffinityKeyMapped}}
> annotation.
> Needs to be documented on this page
> https://apacheignite.readme.io/docs/affinity-collocation
> And might be referred from some other pages (SQL Grid, PHP Guide, etc).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12230) Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption
[ https://issues.apache.org/jira/browse/IGNITE-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937668#comment-16937668 ] Ivan Pavlukhin commented on IGNITE-12230: - [~mstepachev], what do you think is this issues related to IGNITE-11996 ? > Partition eviction during cache stop / deactivation may cause errors leading > to node failure and storage corruption > --- > > Key: IGNITE-12230 > URL: https://issues.apache.org/jira/browse/IGNITE-12230 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > PartitionEvictionTask may produce NullPointerException if cache / cache group > / cluser is stopping / deactivating. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12230) Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption
[ https://issues.apache.org/jira/browse/IGNITE-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937668#comment-16937668 ] Ivan Pavlukhin edited comment on IGNITE-12230 at 9/25/19 12:08 PM: --- [~mstepachev], what do you think is this issue related to IGNITE-11996 ? was (Author: pavlukhin): [~mstepachev], what do you think is this issues related to IGNITE-11996 ? > Partition eviction during cache stop / deactivation may cause errors leading > to node failure and storage corruption > --- > > Key: IGNITE-12230 > URL: https://issues.apache.org/jira/browse/IGNITE-12230 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > PartitionEvictionTask may produce NullPointerException if cache / cache group > / cluser is stopping / deactivating. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12230) Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption
[ https://issues.apache.org/jira/browse/IGNITE-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937664#comment-16937664 ] Stepachev Maksim commented on IGNITE-12230: --- https://github.com/apache/ignite/pull/6906 > Partition eviction during cache stop / deactivation may cause errors leading > to node failure and storage corruption > --- > > Key: IGNITE-12230 > URL: https://issues.apache.org/jira/browse/IGNITE-12230 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > PartitionEvictionTask may produce NullPointerException if cache / cache group > / cluser is stopping / deactivating. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12230) Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption
Stepachev Maksim created IGNITE-12230: - Summary: Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption Key: IGNITE-12230 URL: https://issues.apache.org/jira/browse/IGNITE-12230 Project: Ignite Issue Type: Bug Components: cache Reporter: Stepachev Maksim Assignee: Stepachev Maksim Fix For: 2.8 PartitionEvictionTask may produce NullPointerException if cache / cache group / cluser is stopping / deactivating. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11960) Throw on attemp to create existing metric
[ https://issues.apache.org/jira/browse/IGNITE-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11960: - Priority: Minor (was: Major) > Throw on attemp to create existing metric > - > > Key: IGNITE-11960 > URL: https://issues.apache.org/jira/browse/IGNITE-11960 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Minor > Labels: IEP-35 > Fix For: 2.8 > > > Currently, `MetricRegistry` returns an existing metric instance on a second > creation attempt. > We should add assert and throw in such cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11960) Throw on attemp to create existing metric
[ https://issues.apache.org/jira/browse/IGNITE-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11960: - Fix Version/s: (was: 2.8) > Throw on attemp to create existing metric > - > > Key: IGNITE-11960 > URL: https://issues.apache.org/jira/browse/IGNITE-11960 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Minor > Labels: IEP-35 > > Currently, `MetricRegistry` returns an existing metric instance on a second > creation attempt. > We should add assert and throw in such cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11981) [IEP-35] Create MU shortcut instead of static import of MetricUtils
[
https://issues.apache.org/jira/browse/IGNITE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11981:
-
Fix Version/s: (was: 2.8)
> [IEP-35] Create MU shortcut instead of static import of MetricUtils
> ---
>
> Key: IGNITE-11981
> URL: https://issues.apache.org/jira/browse/IGNITE-11981
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Minor
> Labels: IEP-35
>
> More Ignite-way of coding is the usage of short cut classes.
> We should use MU instead of static import of {{MetricUtils}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11981) [IEP-35] Create MU shortcut instead of static import of MetricUtils
[
https://issues.apache.org/jira/browse/IGNITE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11981:
-
Priority: Minor (was: Major)
> [IEP-35] Create MU shortcut instead of static import of MetricUtils
> ---
>
> Key: IGNITE-11981
> URL: https://issues.apache.org/jira/browse/IGNITE-11981
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8
>
>
> More Ignite-way of coding is the usage of short cut classes.
> We should use MU instead of static import of {{MetricUtils}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12197) Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
[
https://issues.apache.org/jira/browse/IGNITE-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12197:
-
Priority: Minor (was: Major)
> Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
> --
>
> Key: IGNITE-12197
> URL: https://issues.apache.org/jira/browse/IGNITE-12197
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> IGNITE-12027 introduces possible bug due to incorrect way for getting value
> of persistent enabled property in {{CacheGroupMetricsImpl}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12191) Add support of system view and metric to Visor
[
https://issues.apache.org/jira/browse/IGNITE-12191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12191:
-
Priority: Minor (was: Major)
> Add support of system view and metric to Visor
> --
>
> Key: IGNITE-12191
> URL: https://issues.apache.org/jira/browse/IGNITE-12191
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8
>
>
> After Ignite obtain new {{SystemView}} and {{Metric}} API we should add
> support of it to the Visor.
> User should be able to query and view any system view content or Metric
> Registry values.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12211) Client connections system view
[ https://issues.apache.org/jira/browse/IGNITE-12211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937631#comment-16937631 ] Aleksey Plekhanov commented on IGNITE-12211: [~NIzhikov], looks good to me. > Client connections system view > -- > > Key: IGNITE-12211 > URL: https://issues.apache.org/jira/browse/IGNITE-12211 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 2h > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add client connections to the system views. > System view should track JDBC, ODBC and thin connections. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12182) ExecutorService is inconsistent with Compute and Services, runs on clients
[ https://issues.apache.org/jira/browse/IGNITE-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Darlington updated IGNITE-12182: Fix Version/s: 2.8 > ExecutorService is inconsistent with Compute and Services, runs on clients > -- > > Key: IGNITE-12182 > URL: https://issues.apache.org/jira/browse/IGNITE-12182 > Project: Ignite > Issue Type: Bug > Components: compute >Affects Versions: 2.7.5 >Reporter: Stephen Darlington >Assignee: Stephen Darlington >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > In IGNITE-860 the default behaviour was changed so that compute and service > tasks would be executed only on server nodes. This is a sensible default and > it's confusing that it's not also true for jobs run using the ExecutorService. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12211) Client connections system view
[
https://issues.apache.org/jira/browse/IGNITE-12211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937581#comment-16937581
]
Ignite TC Bot commented on IGNITE-12211:
{panel:title=Branch: [pull/6898/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4630626buildTypeId=IgniteTests24Java8_RunAll]
> Client connections system view
> --
>
> Key: IGNITE-12211
> URL: https://issues.apache.org/jira/browse/IGNITE-12211
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> IGNITE-12145 finished
> We should add client connections to the system views.
> System view should track JDBC, ODBC and thin connections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10532) [ML] Add Confusion Matrix for multi-class classification
[ https://issues.apache.org/jira/browse/IGNITE-10532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10532: -- Affects Version/s: (was: 2.8) > [ML] Add Confusion Matrix for multi-class classification > > > Key: IGNITE-10532 > URL: https://issues.apache.org/jira/browse/IGNITE-10532 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Explore ability to integrate the OneVsRest with ConfusionMatrix calculation > also it can be implemented only after MultiClassEvaluator (no ticket yet) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8296) Move Spark Scala DataFrames code examples to correct directory and prefix with "Scalar" to follow convention used with other Scala examples
[ https://issues.apache.org/jira/browse/IGNITE-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-8296: - Affects Version/s: (was: 2.4) 3.0 > Move Spark Scala DataFrames code examples to correct directory and prefix > with "Scalar" to follow convention used with other Scala examples > > > Key: IGNITE-8296 > URL: https://issues.apache.org/jira/browse/IGNITE-8296 > Project: Ignite > Issue Type: Improvement > Components: spark >Affects Versions: 3.0 >Reporter: Akmal Chaudhri >Assignee: Aleksey Zinoviev >Priority: Minor > > # The Spark Scala DataFrames code examples are in the wrong directory. They > should be moved to the correct directory structure. > # The Spark Scala DataFrames code examples should follow the naming > convention used for other Scala code examples and be prefixed with "Scalar". > or move SparkScalar example and its logic to the appropriate folder in spark > folder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10575) [ML] Add examples for ensemble training
[ https://issues.apache.org/jira/browse/IGNITE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10575: -- Affects Version/s: 3.0 > [ML] Add examples for ensemble training > --- > > Key: IGNITE-10575 > URL: https://issues.apache.org/jira/browse/IGNITE-10575 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 3.0 >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10529) [ML][Umbrella] Add Confusion Matrix support for classification algorithms
[ https://issues.apache.org/jira/browse/IGNITE-10529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10529: -- Affects Version/s: (was: 2.8) 3.0 > [ML][Umbrella] Add Confusion Matrix support for classification algorithms > - > > Key: IGNITE-10529 > URL: https://issues.apache.org/jira/browse/IGNITE-10529 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > This is an umbrella ticket for Confusion Matrix Support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10531) [ML] Refactor all examples to use Binary Confusion Matrix instead of calculations by hand
[
https://issues.apache.org/jira/browse/IGNITE-10531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Zinoviev updated IGNITE-10531:
--
Affects Version/s: (was: 2.8)
3.0
> [ML] Refactor all examples to use Binary Confusion Matrix instead of
> calculations by hand
> -
>
> Key: IGNITE-10531
> URL: https://issues.apache.org/jira/browse/IGNITE-10531
> Project: Ignite
> Issue Type: Sub-task
> Components: ml
>Affects Versions: 3.0
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>Priority: Minor
> Fix For: 2.8
>
>
> Change
> // Build confusion matrix. See https://en.wikipedia.org/wiki/Confusion_matrix
> int[][] confusionMtx = \{{0, 0}, \{0, 0}};
> to usage of ConfusionMatrix
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10530) [ML] Add Confusion Matrix for Binary Classification
[ https://issues.apache.org/jira/browse/IGNITE-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10530: -- Affects Version/s: (was: 2.8) 3.0 > [ML] Add Confusion Matrix for Binary Classification > --- > > Key: IGNITE-10530 > URL: https://issues.apache.org/jira/browse/IGNITE-10530 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Add special class to build confusion matrix as a product of evaluation process -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9463) [ML] Update ML tutorial with new model composition/update features
[ https://issues.apache.org/jira/browse/IGNITE-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9463: - Affects Version/s: 2.8 > [ML] Update ML tutorial with new model composition/update features > -- > > Key: IGNITE-9463 > URL: https://issues.apache.org/jira/browse/IGNITE-9463 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > # Add example #10 with model composition (DT and Logit) > # Add example #11 with online learning for DT > # Add example #12 for bagging > # Add example #13 for boosting -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10532) [ML] Add Confusion Matrix for multi-class classification
[ https://issues.apache.org/jira/browse/IGNITE-10532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10532: -- Affects Version/s: 3.0 > [ML] Add Confusion Matrix for multi-class classification > > > Key: IGNITE-10532 > URL: https://issues.apache.org/jira/browse/IGNITE-10532 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0, 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Explore ability to integrate the OneVsRest with ConfusionMatrix calculation > also it can be implemented only after MultiClassEvaluator (no ticket yet) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9732) Add joins to Spark Dataframe examples
[
https://issues.apache.org/jira/browse/IGNITE-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Zinoviev updated IGNITE-9732:
-
Affects Version/s: (was: 2.6)
> Add joins to Spark Dataframe examples
> -
>
> Key: IGNITE-9732
> URL: https://issues.apache.org/jira/browse/IGNITE-9732
> Project: Ignite
> Issue Type: Improvement
> Components: examples, spark
>Affects Versions: 2.8
>Reporter: Valentin Kulichenko
>Assignee: Aleksey Zinoviev
>Priority: Major
> Fix For: 2.8
>
>
> {{IgniteDataFrameExample}} creates two tables - {{city}} and {{person}}, but
> only {{person}} is actually used. Need to add join examples.
> Would also be great to demonstrate the fact that optimization is working and
> joins are executed in Ignite, not Spark (using {{explain()}}, maybe?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11723) IgniteSpark integration should support skipStore option for internal dataStreamer (IgniteRdd and Ignite DataFrame)
[ https://issues.apache.org/jira/browse/IGNITE-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-11723: -- Affects Version/s: (was: 2.7) > IgniteSpark integration should support skipStore option for internal > dataStreamer (IgniteRdd and Ignite DataFrame) > -- > > Key: IGNITE-11723 > URL: https://issues.apache.org/jira/browse/IGNITE-11723 > Project: Ignite > Issue Type: Improvement > Components: spark >Affects Versions: 2.8 >Reporter: Andrey Aleksandrov >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > At the moment this option can't be set. But this integrations could be used > for initial data loading also for the caches with cache stores > implementation. > With skipStore option, we could avoid write-through behavior during this > initial data loading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Zinoviev updated IGNITE-11724:
--
Affects Version/s: (was: 2.7)
2.8
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Aleksey Zinoviev
>Priority: Major
> Fix For: 2.8
>
>
> Next code could hang in case if PairFunction logic will throw the exception:
> JavaPairRDD rdd_records = records.mapToPair(new MapFunction());
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configUrl);
> JavaIgniteRDD igniteRdd = igniteContext. Value>fromCache(cacheName);
> igniteRdd.savePairs(rdd_records);
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒ {
> val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value)
> })
> }
> finally {
> streamer.close()
> }
> })
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9732) Add joins to Spark Dataframe examples
[
https://issues.apache.org/jira/browse/IGNITE-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Zinoviev updated IGNITE-9732:
-
Affects Version/s: 2.8
> Add joins to Spark Dataframe examples
> -
>
> Key: IGNITE-9732
> URL: https://issues.apache.org/jira/browse/IGNITE-9732
> Project: Ignite
> Issue Type: Improvement
> Components: examples, spark
>Affects Versions: 2.6, 2.8
>Reporter: Valentin Kulichenko
>Assignee: Aleksey Zinoviev
>Priority: Major
> Fix For: 2.8
>
>
> {{IgniteDataFrameExample}} creates two tables - {{city}} and {{person}}, but
> only {{person}} is actually used. Need to add join examples.
> Would also be great to demonstrate the fact that optimization is working and
> joins are executed in Ignite, not Spark (using {{explain()}}, maybe?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11723) IgniteSpark integration should support skipStore option for internal dataStreamer (IgniteRdd and Ignite DataFrame)
[ https://issues.apache.org/jira/browse/IGNITE-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-11723: -- Affects Version/s: 2.8 > IgniteSpark integration should support skipStore option for internal > dataStreamer (IgniteRdd and Ignite DataFrame) > -- > > Key: IGNITE-11723 > URL: https://issues.apache.org/jira/browse/IGNITE-11723 > Project: Ignite > Issue Type: Improvement > Components: spark >Affects Versions: 2.7, 2.8 >Reporter: Andrey Aleksandrov >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > At the moment this option can't be set. But this integrations could be used > for initial data loading also for the caches with cache stores > implementation. > With skipStore option, we could avoid write-through behavior during this > initial data loading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10869) [ML] Add MultiClass classification metrics
[ https://issues.apache.org/jira/browse/IGNITE-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10869: -- Affects Version/s: (was: 2.8) > [ML] Add MultiClass classification metrics > -- > > Key: IGNITE-10869 > URL: https://issues.apache.org/jira/browse/IGNITE-10869 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Add ability to calculate multiple metrics (as binary metrics) for multiclass > classification > It can be merged with OneVsRest approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10869) [ML] Add MultiClass classification metrics
[ https://issues.apache.org/jira/browse/IGNITE-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10869: -- Affects Version/s: 3.0 > [ML] Add MultiClass classification metrics > -- > > Key: IGNITE-10869 > URL: https://issues.apache.org/jira/browse/IGNITE-10869 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0, 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Add ability to calculate multiple metrics (as binary metrics) for multiclass > classification > It can be merged with OneVsRest approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10870) [ML] Add an example for KNN/LogReg and multi-class task full Iris dataset
[ https://issues.apache.org/jira/browse/IGNITE-10870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10870: -- Affects Version/s: (was: 2.8) 3.0 > [ML] Add an example for KNN/LogReg and multi-class task full Iris dataset > - > > Key: IGNITE-10870 > URL: https://issues.apache.org/jira/browse/IGNITE-10870 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Add a one or two examples for KNN/LogReg and Iris dataset with 3 classes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-6642) [Umbrella] Integration with PMML
[ https://issues.apache.org/jira/browse/IGNITE-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-6642: - Affects Version/s: 3.0 > [Umbrella] Integration with PMML > > > Key: IGNITE-6642 > URL: https://issues.apache.org/jira/browse/IGNITE-6642 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 3.0 >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Minor > > PMML - Predictive Model Markup Language is XML based language which used in > SPARK MLlib and others platforms. > Here some additional info about PMML: > (i) http://dmg.org/pmml/v4-3/GeneralStructure.html > (i) https://github.com/jpmml/jpmml-model -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9283) [ML] Add Discrete Cosine preprocessor
[ https://issues.apache.org/jira/browse/IGNITE-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9283: - Affects Version/s: 3.0 > [ML] Add Discrete Cosine preprocessor > - > > Key: IGNITE-9283 > URL: https://issues.apache.org/jira/browse/IGNITE-9283 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Ilya Lantukh >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Add [https://en.wikipedia.org/wiki/Discrete_cosine_transform] > Please look at the MinMaxScaler or Normalization packages in preprocessing > package. > Add classes if required > 1) Preprocessor > 2) Trainer > 3) custom PartitionData if shuffling is a step of algorithm > > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9746) [ML] Add Complement Naive Bayes
[ https://issues.apache.org/jira/browse/IGNITE-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9746: - Affects Version/s: 3.0 > [ML] Add Complement Naive Bayes > --- > > Key: IGNITE-9746 > URL: https://issues.apache.org/jira/browse/IGNITE-9746 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0 >Reporter: Ravil Galeyev >Priority: Major > > Naive Bayes classifiers are a family of simple probabilistic classifiers > based on applying Bayes' theorem with strong (naive) independence assumptions > between the features. > So we want to add this algorithm to Apache Ignite ML module. > [Complement Naive > Bayes|http://scikit-learn.org/stable/modules/naive_bayes.html#complement-naive-bayes] > is an adaptation of the standard multinomial naive Bayes (MNB) algorithm > that is particularly suited for imbalanced data sets. > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9281) [ML] Starter ML tasks
[ https://issues.apache.org/jira/browse/IGNITE-9281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9281: - Affects Version/s: 3.0 > [ML] Starter ML tasks > - > > Key: IGNITE-9281 > URL: https://issues.apache.org/jira/browse/IGNITE-9281 > Project: Ignite > Issue Type: Wish > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: None > > > This ticket is an umbrella ticket for ML starter tasks. > Please, contact [~zaleslaw] to assign and get help with one of this tasks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10438) [ML] DBSCAN
[ https://issues.apache.org/jira/browse/IGNITE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10438: -- Affects Version/s: 3.0 > [ML] DBSCAN > --- > > Key: IGNITE-10438 > URL: https://issues.apache.org/jira/browse/IGNITE-10438 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 3.0 >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Trivial > > Density-based spatial clustering of applications with noise (DBSCAN) > [wiki description|https://en.wikipedia.org/wiki/DBSCAN] > We could test this algorithm on TWO_CLASSED_IRIS and IRIS (see > MLSandboxDatasets enum) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10804) [ML] Add ability to load LinReg model from Spark to Ignite via PMML
[ https://issues.apache.org/jira/browse/IGNITE-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10804: -- Affects Version/s: 3.0 > [ML] Add ability to load LinReg model from Spark to Ignite via PMML > --- > > Key: IGNITE-10804 > URL: https://issues.apache.org/jira/browse/IGNITE-10804 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0, 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > > 1) Write simple ML pipeline for Spark > 2) Convert to PMML model > 3) Load to Ignite > 4) Predict on Ignite -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10804) [ML] Add ability to load LinReg model from Spark to Ignite via PMML
[ https://issues.apache.org/jira/browse/IGNITE-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10804: -- Affects Version/s: (was: 2.8) > [ML] Add ability to load LinReg model from Spark to Ignite via PMML > --- > > Key: IGNITE-10804 > URL: https://issues.apache.org/jira/browse/IGNITE-10804 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > > 1) Write simple ML pipeline for Spark > 2) Convert to PMML model > 3) Load to Ignite > 4) Predict on Ignite -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10407) [ML][Umbrella] Add Multi-label multi-class classification trainer and model
[ https://issues.apache.org/jira/browse/IGNITE-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10407: -- Affects Version/s: 3.0 > [ML][Umbrella] Add Multi-label multi-class classification trainer and model > --- > > Key: IGNITE-10407 > URL: https://issues.apache.org/jira/browse/IGNITE-10407 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > > Improve Ignite ML ability to work with tasks for multi-labeled > multi-classification > It requiers > * extension of current API with models for Double prediction only > * addition of common OneVsRest Multi-labeled Multi-classification Model and > Trainer > * preparing apropriate datasets for example and testing > * -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10804) [ML] Add ability to load LinReg model from Spark to Ignite via PMML
[ https://issues.apache.org/jira/browse/IGNITE-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10804: -- Affects Version/s: 2.8 > [ML] Add ability to load LinReg model from Spark to Ignite via PMML > --- > > Key: IGNITE-10804 > URL: https://issues.apache.org/jira/browse/IGNITE-10804 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > > 1) Write simple ML pipeline for Spark > 2) Convert to PMML model > 3) Load to Ignite > 4) Predict on Ignite -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7327) Add CSV loading to Labeled Dataset with Loader
[ https://issues.apache.org/jira/browse/IGNITE-7327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-7327: - Affects Version/s: 3.0 > Add CSV loading to Labeled Dataset with Loader > --- > > Key: IGNITE-7327 > URL: https://issues.apache.org/jira/browse/IGNITE-7327 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Trivial > > Comment from [~dmitrievanthony] > Lots of datasets (from Kaggle for example) are supplied in CSV format with > header line. In connection with it does it make sense to: > Use some CSV parsing (it's a bit more complicated than just splitting by > comma)? > Add ability to use first header line as a source for so called feature names? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8250) Adopt Fuzzy CMeans to PartitionedDatasets
[ https://issues.apache.org/jira/browse/IGNITE-8250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-8250: - Affects Version/s: 3.0 > Adopt Fuzzy CMeans to PartitionedDatasets > - > > Key: IGNITE-8250 > URL: https://issues.apache.org/jira/browse/IGNITE-8250 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Trivial > > Add Model/Trainer, tests, example -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7025) Implement different strategies to fill missed data in LabeledDataset during loading from file
[ https://issues.apache.org/jira/browse/IGNITE-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-7025: - Affects Version/s: 3.0 > Implement different strategies to fill missed data in LabeledDataset during > loading from file > - > > Key: IGNITE-7025 > URL: https://issues.apache.org/jira/browse/IGNITE-7025 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Trivial > > For example, it can be four strategies > * Fill missed value with zero or empty string or default value for > categorical features = ZERO > * Fill missed value with mean on column/Requires an additional time to > calculate = MEAN > * Fill missed value with mode on column. Requires an additional time to > calculate = MODE > * Deletes observation with missed values. Transforms dataset and changes > indexing = DELETE -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7328) Improve Labeled Dataset loading from txt file
[ https://issues.apache.org/jira/browse/IGNITE-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-7328: - Affects Version/s: 3.0 > Improve Labeled Dataset loading from txt file > - > > Key: IGNITE-7328 > URL: https://issues.apache.org/jira/browse/IGNITE-7328 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 3.0 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Trivial > > 1. Wouldn't it be better to parse rows in-place (not to save them as strings > at first)? In current implementation we will be needed to keep a dataset in > memory twice and it might be a problem for big datasets. > 2. What about the case when a dataset contains not only a numerical data? Do > we consider this case or for such purposes some other "DatasetLoader" will be > used? > 3. Just an idea, in case we don't want to fall on bad data (99% of cases) > would be great to understand the quality of loaded dataset such as number of > missed rows/values. > 4. Does a situation when a row doesn't contain required number of columns > should be considered as "bad data" and don't break parsing with > IndexOutOfBoundException? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12226) Improve BinaryObjectException message
[
https://issues.apache.org/jira/browse/IGNITE-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937541#comment-16937541
]
Kirill Tkalenko commented on IGNITE-12226:
--
[~jooger], please do a code review.
> Improve BinaryObjectException message
> -
>
> Key: IGNITE-12226
> URL: https://issues.apache.org/jira/browse/IGNITE-12226
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are getting the following exception in case of different type IDs:
> {noformat}
> org.apache.ignite.binary.BinaryObjectException: Failed to get field because
> type ID of passed object differs from type ID this BinaryField belongs to
> [expected=-635374417, actual=1778229603]
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:109)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:220)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:116)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2RowDescriptor.columnValue(GridH2RowDescriptor.java:331)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue0(GridH2KeyValueRowOnheap.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue(GridH2KeyValueRowOnheap.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:350)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:56)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:4614)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:4534)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$1300(BPlusTree.java:92)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:296)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4967)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:276)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4952)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:348)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2450)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2203)
> {noformat}
> This message isn't informative. We should print more detailes about types,
> for example classname, class structure (if applicable), which field in class
> we tried to read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12226) Improve BinaryObjectException message
[
https://issues.apache.org/jira/browse/IGNITE-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-12226:
-
Reviewer: Yury Gerzhedovich (was: Sergey Antonov)
> Improve BinaryObjectException message
> -
>
> Key: IGNITE-12226
> URL: https://issues.apache.org/jira/browse/IGNITE-12226
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are getting the following exception in case of different type IDs:
> {noformat}
> org.apache.ignite.binary.BinaryObjectException: Failed to get field because
> type ID of passed object differs from type ID this BinaryField belongs to
> [expected=-635374417, actual=1778229603]
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:109)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:220)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:116)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2RowDescriptor.columnValue(GridH2RowDescriptor.java:331)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue0(GridH2KeyValueRowOnheap.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue(GridH2KeyValueRowOnheap.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:350)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:56)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:4614)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:4534)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$1300(BPlusTree.java:92)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:296)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4967)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:276)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4952)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:348)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2450)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2203)
> {noformat}
> This message isn't informative. We should print more detailes about types,
> for example classname, class structure (if applicable), which field in class
> we tried to read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12226) Improve BinaryObjectException message
[
https://issues.apache.org/jira/browse/IGNITE-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937538#comment-16937538
]
Sergey Antonov commented on IGNITE-12226:
-
[~ktkale...@gridgain.com] Changes looks good for me.
> Improve BinaryObjectException message
> -
>
> Key: IGNITE-12226
> URL: https://issues.apache.org/jira/browse/IGNITE-12226
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are getting the following exception in case of different type IDs:
> {noformat}
> org.apache.ignite.binary.BinaryObjectException: Failed to get field because
> type ID of passed object differs from type ID this BinaryField belongs to
> [expected=-635374417, actual=1778229603]
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:109)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:220)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:116)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2RowDescriptor.columnValue(GridH2RowDescriptor.java:331)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue0(GridH2KeyValueRowOnheap.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue(GridH2KeyValueRowOnheap.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:350)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:56)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:4614)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:4534)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$1300(BPlusTree.java:92)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:296)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4967)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:276)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4952)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:348)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2450)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2203)
> {noformat}
> This message isn't informative. We should print more detailes about types,
> for example classname, class structure (if applicable), which field in class
> we tried to read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12201) distributed sql join not working as mentioned in documentation
[
https://issues.apache.org/jira/browse/IGNITE-12201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937537#comment-16937537
]
Ivan Pavlukhin commented on IGNITE-12201:
-
Hi [~shm],
What kind of fix do you expect for this issue? Will it be enough to update
documentation?
As my understanding goes Ignite requires that index exists on a table column
which is used to be "joined" remotely. As for replicated caches, each node has
all table data so there is no need to do remote lookups for replicated tables.
I agree here that limitations here are not trivial and should be documented
well.
> distributed sql join not working as mentioned in documentation
> --
>
> Key: IGNITE-12201
> URL: https://issues.apache.org/jira/browse/IGNITE-12201
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
> Environment: Kubernetes on RHEL 7.6
>Reporter: shivakumar
>Priority: Major
> Attachments: distributed_sql_error.txt
>
>
> I am trying to do a simple cross join on two tables with non-collocated data
> (without affinity key),
> This non-collocated distributed join always fails with the error message:
>
> *"java.sql.SQLException: javax.cache.CacheException: Failed to prepare
> distributed join query: join condition does not use index "*
>
> If I create one of the tables in replicated mode and another one in
> partitioned mode this Join operation works but documentation mentions that
> Ignite supports non-collocated joins without any condition.
> And we tried with 3 tables and 1 in replicated and other 2 in partitioned
> then we observed that it failed.
> we are running the Join operations with *distributedJoins=true.*
> *We observed that if there are N tables in Join operation then (N-1) should
> be in replicated mode, is our understanding right?*
> *If our understanding is correct then to do Join operation the dimensioning
> of cluster increases by many folds which can't be used in a production
> environment.*
> *To reproduce:*
> *Ignite with 4 node cluster with native persistence enabled.*
> *create the following tables*
> {quote} {{CREATE TABLE City (}}{quote}
> {quote} {{ id LONG PRIMARY KEY, name VARCHAR)}}{quote}
> {quote} {{ WITH "backup=1";}}{quote}
> {quote} {{}}{quote}
> {quote} {{CREATE TABLE Person (}}
> {{ id LONG, name VARCHAR, city_id LONG, PRIMARY KEY (id, city_id))}}
> {{ WITH "backups=1";}}
> {{}}
> {{CREATE INDEX idx_city_name ON City (name);}}
> {{}}
> {{CREATE INDEX idx_person_name ON Person (name);}}
>
> {{INSERT INTO City (id, name) VALUES (1, 'Forest Hill');}}
> {{INSERT INTO City (id, name) VALUES (2, 'Denver');}}
> {{INSERT INTO City (id, name) VALUES (3, 'St. Petersburg');}}
> {{}}
> {{INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);}}
> {{INSERT INTO Person (id, name, city_id) VALUES (2, 'Jane Roe', 2);}}
> {{INSERT INTO Person (id, name, city_id) VALUES (3, 'Mary Major', 1);}}
> {{INSERT INTO Person (id, name, city_id) VALUES (4, 'Richard Miles', 2);}} {{
> }}{quote}
> Query to be run:
> {quote}select * from City c, Person p;{color:#66}
> {color}{quote}
> {quote}or
> {color:#80}*SELECT*{color} * *{color:#80}FROM{color}* City
> *{color:#80}AS{color}* c *{color:#80}CROSS{color}*
> *{color:#80}join{color}* Person *{color:#80}AS{color}* p;{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12228) Implement an Apache Beam runner on top of Ignite compute grid?
[ https://issues.apache.org/jira/browse/IGNITE-12228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937510#comment-16937510 ] Romain Manni-Bucau commented on IGNITE-12228: - Hi Denis, I'm a bit short these days to drive it alone but I would be very happy to join the impl phase if anybody wants to drive it. > Implement an Apache Beam runner on top of Ignite compute grid? > -- > > Key: IGNITE-12228 > URL: https://issues.apache.org/jira/browse/IGNITE-12228 > Project: Ignite > Issue Type: Wish >Reporter: Romain Manni-Bucau >Priority: Major > > Apache Ignite provides a compute grid. > It is therefore feasible to use that to execute a DAG pipeline. > Therefore implementing a Apache Beam runner executing a DAG on an ignite > cluster would be very valuable for users and would provide a very interesting > alternative to Spark, Dataflow etc...which would be very valuable when using > data from ignite itself. > Hoping it can help, here is Hazelcast Jet implementation which is not that > far even if Jet is a bit more advanced in term of DAG support: > [https://github.com/apache/beam/tree/master/runners/jet-experimental/src/main/java/org/apache/beam/runners/jet] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12226) Improve BinaryObjectException message
[
https://issues.apache.org/jira/browse/IGNITE-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937462#comment-16937462
]
Ignite TC Bot commented on IGNITE-12226:
{panel:title=Branch: [pull/6903/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4630381buildTypeId=IgniteTests24Java8_RunAll]
> Improve BinaryObjectException message
> -
>
> Key: IGNITE-12226
> URL: https://issues.apache.org/jira/browse/IGNITE-12226
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are getting the following exception in case of different type IDs:
> {noformat}
> org.apache.ignite.binary.BinaryObjectException: Failed to get field because
> type ID of passed object differs from type ID this BinaryField belongs to
> [expected=-635374417, actual=1778229603]
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:109)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:220)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:116)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2RowDescriptor.columnValue(GridH2RowDescriptor.java:331)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue0(GridH2KeyValueRowOnheap.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue(GridH2KeyValueRowOnheap.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:350)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:56)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:4614)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:4534)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$1300(BPlusTree.java:92)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:296)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4967)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:276)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4952)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:348)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2450)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2203)
> {noformat}
> This message isn't informative. We should print more detailes about types,
> for example classname, class structure (if applicable), which field in class
> we tried to read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937450#comment-16937450 ] Lev Agafonov commented on IGNITE-11312: --- [~surajsn], [~slukyanov] Guys, if you don't object - I would like to pick up and resolve this ticket. > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[
https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937437#comment-16937437
]
Ignite TC Bot commented on IGNITE-11312:
{panel:title=Branch: [pull/6900/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4632091buildTypeId=IgniteTests24Java8_RunAll]
> JDBC: Thin driver doesn't reports incorrect property names
> --
>
> Key: IGNITE-11312
> URL: https://issues.apache.org/jira/browse/IGNITE-11312
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Reporter: Stanislav Lukyanov
>Assignee: Suraj Singh
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> JDBC driver reports the properties it supports via getPropertyInfo method. It
> currently reports the property names as simple strings, like
> "enforceJoinOrder". However, when the properties are processed on connect
> they are looked up with prefix "ignite.jdbc", e.g.
> "ignite.jdbc.enforceJoinOrder".
> Because of this UI tools like DBeaver can't properly pass the properties to
> Ignite. For example, when "enforceJoinOrder" is set to true in "Connection
> settings" -> "Driver properties" menu of DBeaver it has no effect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
