[jira] [Commented] (IGNITE-15012) Adapting historical rebalance to segment release
[ https://issues.apache.org/jira/browse/IGNITE-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17377077#comment-17377077 ] Kirill Tkalenko commented on IGNITE-15012: -- [~slava.koptilin] Please make code review. > Adapting historical rebalance to segment release > > > Key: IGNITE-15012 > URL: https://issues.apache.org/jira/browse/IGNITE-15012 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.12 > > Time Spent: 2h > Remaining Estimate: 0h > > It is necessary to adapt the historical rebalance to the release of WAL > segments after their reservation. Since IGNITE-14952 will be automatically > released when the maximum is reached. > This following proposal is part (*in bold*) of a discussion at [dev > list|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]: > Main proposal: > When theDataStorageConfiguration#getMaxWalArchiveSize is reached, cancel and > do not give the reservation of the WAL segments until we reach > DataStorageConfiguration#getWalArchiveSize. In this case, *if there is no > segment for historical rebalance, we will automatically switch to full > rebalance.* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15012) Adapting historical rebalance to segment release
[
https://issues.apache.org/jira/browse/IGNITE-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17377027#comment-17377027
]
Ignite TC Bot commented on IGNITE-15012:
{panel:title=Branch: [pull/9206/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9206/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 4{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=6076456]]
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testNoReserveHistoryForPreloading -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testReleaseBeforeReleaseHistoryForExchange
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testImmediateReleaseSegment -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testReleaseDuringRebalanceIterator -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testReleaseBeforeRebalanceIterator -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testReleaseSegmentAfterSearchAndReserveCheckpoints
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testReleaseBeforeReleaseHistoryForPreloading
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
ReleaseSegmentOnHistoricalRebalanceTest.testNoReserveSegment - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6076483buildTypeId=IgniteTests24Java8_RunAll]
> Adapting historical rebalance to segment release
>
>
> Key: IGNITE-15012
> URL: https://issues.apache.org/jira/browse/IGNITE-15012
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> It is necessary to adapt the historical rebalance to the release of WAL
> segments after their reservation. Since IGNITE-14952 will be automatically
> released when the maximum is reached.
> This following proposal is part (*in bold*) of a discussion at [dev
> list|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]:
> Main proposal:
> When theDataStorageConfiguration#getMaxWalArchiveSize is reached, cancel and
> do not give the reservation of the WAL segments until we reach
> DataStorageConfiguration#getWalArchiveSize. In this case, *if there is no
> segment for historical rebalance, we will automatically switch to full
> rebalance.*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14999) Support snapshot encryption with same master-key.
[ https://issues.apache.org/jira/browse/IGNITE-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-14999: -- Description: This PR suggests support of encrypted snapshots with same master key. Changes: 1. Added encrypted file IO to the snapshot deltas to get ability to assemble encrypted snapshot data. 2. Added general-purpose records to snapshot meta to transfer encryption keys (encrypted by master key). 3. To keep consistency of the keys and encrypted data between snapshot and the persistent store, blocked re-encryption and master key change during snapshot operations and opposite. 4. Snapshot tests now have ‘encrypted’ option. was: This PR suggests support of encrypted snapshots with same master key. Main changes: 1. Added encrypted file IO to the snapshot deltas to get ability to assemble encrypted snapshot data. 2. Added general-purpose records to snapshot meta to transfer encryption keys. The keys are encrypted with master key. 3. To keep consistency of the keys and encrypted data between snapshot and the persistent store, blocked re-encryption, master key change during snapshot operations and opposite 4. Snapshot tests now have ‘encrypted’ option. > Support snapshot encryption with same master-key. > - > > Key: IGNITE-14999 > URL: https://issues.apache.org/jira/browse/IGNITE-14999 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > This PR suggests support of encrypted snapshots with same master key. > Changes: > 1. Added encrypted file IO to the snapshot deltas to get ability to assemble > encrypted snapshot data. > 2. Added general-purpose records to snapshot meta to transfer encryption keys > (encrypted by master key). > 3. To keep consistency of the keys and encrypted data between snapshot and > the persistent store, blocked re-encryption and master key change during > snapshot operations and opposite. > 4. Snapshot tests now have ‘encrypted’ option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14999) Support snapshot encryption with same master-key.
[ https://issues.apache.org/jira/browse/IGNITE-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-14999: -- Description: This PR suggests support of encrypted snapshots with same master key. Main changes: 1. Added encrypted file IO to the snapshot deltas to get ability to assemble encrypted snapshot data. 2. Added general-purpose records to snapshot meta to transfer encryption keys. The keys are encrypted with master key. 3. To keep consistency of the keys and encrypted data between snapshot and the persistent store, blocked re-encryption, master key change during snapshot operations and opposite 4. Snapshot tests now have ‘encrypted’ option. was: This PR suggests support of encrypted snapshots with same master key. Main changes: 1. Added encrypted file IO to the snapshot deltas to get ability to assemble encrypted snapshot data. 2. Added general-purpose records to snapshot meta to transfer encryption keys. The keys are encrypted with master key. 3. Blocked re-encryption, master key change during snapshot operations and opposite to keep consistency of the keys and encrypted data between snapshot and the persistent storage. 4. Most of the snapshot tests are now have ‘encrypted’ option. > Support snapshot encryption with same master-key. > - > > Key: IGNITE-14999 > URL: https://issues.apache.org/jira/browse/IGNITE-14999 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > This PR suggests support of encrypted snapshots with same master key. > Main changes: > 1. Added encrypted file IO to the snapshot deltas to get ability to assemble > encrypted snapshot data. > 2. Added general-purpose records to snapshot meta to transfer encryption > keys. The keys are encrypted with master key. > 3. To keep consistency of the keys and encrypted data between snapshot and > the persistent store, blocked re-encryption, master key change during > snapshot operations and opposite > 4. Snapshot tests now have ‘encrypted’ option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14999) Support snapshot encryption with same master-key.
[ https://issues.apache.org/jira/browse/IGNITE-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-14999: -- Description: This PR suggests support of encrypted snapshots with same master key. Main changes: 1. Added encrypted file IO to the snapshot deltas to get ability to assemble encrypted snapshot data. 2. Added general-purpose records to snapshot meta to transfer encryption keys. The keys are encrypted with master key. 3. Blocked re-encryption, master key change during snapshot operations and opposite to keep consistency of the keys and encrypted data between snapshot and the persistent storage. 4. Most of the snapshot tests are now have ‘encrypted’ option. > Support snapshot encryption with same master-key. > - > > Key: IGNITE-14999 > URL: https://issues.apache.org/jira/browse/IGNITE-14999 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > This PR suggests support of encrypted snapshots with same master key. > Main changes: > 1. Added encrypted file IO to the snapshot deltas to get ability to assemble > encrypted snapshot data. > 2. Added general-purpose records to snapshot meta to transfer encryption > keys. The keys are encrypted with master key. > 3. Blocked re-encryption, master key change during snapshot operations and > opposite to keep consistency of the keys and encrypted data between snapshot > and the persistent storage. > 4. Most of the snapshot tests are now have ‘encrypted’ option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15076) Calcite. ignite.[sh|bat] node runner script failed to start instance.
[
https://issues.apache.org/jira/browse/IGNITE-15076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny updated IGNITE-15076:
Labels: calcite calcite2-required calcite3-required (was: calcite)
> Calcite. ignite.[sh|bat] node runner script failed to start instance.
> -
>
> Key: IGNITE-15076
> URL: https://issues.apache.org/jira/browse/IGNITE-15076
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
>
> Found that node runner script failed with trace:
> {noformat}
> java.lang.ExceptionInInitializerError
> at
> org.apache.calcite.tools.Frameworks$ConfigBuilder.(Frameworks.java:241)
> at
> org.apache.calcite.tools.Frameworks$ConfigBuilder.(Frameworks.java:217)
> at
> org.apache.calcite.tools.Frameworks.newConfigBuilder(Frameworks.java:201)
> at
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.(CalciteQueryProcessor.java:73)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.util.IgniteUtils.inClassPath(IgniteUtils.java:1754)
> at
> org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:181)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1267)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2141)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1787)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1172)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1066)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:952)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:851)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:721)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:690)
> at org.apache.ignite.Ignition.start(Ignition.java:353)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:367)
> Caused by: java.lang.NullPointerException
> at
> sun.reflect.annotation.TypeAnnotationParser.mapTypeAnnotations(TypeAnnotationParser.java:356)
> at
> sun.reflect.annotation.AnnotatedTypeFactory$AnnotatedTypeBaseImpl.(AnnotatedTypeFactory.java:139)
> at
> sun.reflect.annotation.AnnotatedTypeFactory.buildAnnotatedType(AnnotatedTypeFactory.java:65)
> at
> sun.reflect.annotation.TypeAnnotationParser.buildAnnotatedType(TypeAnnotationParser.java:79)
> at
> java.lang.reflect.Executable.getAnnotatedReturnType0(Executable.java:640)
> at java.lang.reflect.Method.getAnnotatedReturnType(Method.java:648)
> at
> org.apache.calcite.util.ImmutableBeans.makeDef(ImmutableBeans.java:146)
> at
> org.apache.calcite.util.ImmutableBeans.access$000(ImmutableBeans.java:55)
> at
> org.apache.calcite.util.ImmutableBeans$1.load(ImmutableBeans.java:68)
> at
> org.apache.calcite.util.ImmutableBeans$1.load(ImmutableBeans.java:65)
> at
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3527)
> at
> com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2276)
> at
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2154)
> at
> com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2044)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3951)
> at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3973)
> at
> com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4957)
> at
> org.apache.calcite.util.ImmutableBeans.create_(ImmutableBeans.java:95)
> at
> org.apache.calcite.util.ImmutableBeans.create(ImmutableBeans.java:76)
> at
> org.apache.calcite.sql.validate.SqlValidator$Config.(SqlValidator.java:792)
> ... 19 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15076) Calcite. ignite.[sh|bat] node runner script failed to start instance.
Stanilovsky Evgeny created IGNITE-15076:
---
Summary: Calcite. ignite.[sh|bat] node runner script failed to
start instance.
Key: IGNITE-15076
URL: https://issues.apache.org/jira/browse/IGNITE-15076
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
Found that node runner script failed with trace:
{noformat}
java.lang.ExceptionInInitializerError
at
org.apache.calcite.tools.Frameworks$ConfigBuilder.(Frameworks.java:241)
at
org.apache.calcite.tools.Frameworks$ConfigBuilder.(Frameworks.java:217)
at
org.apache.calcite.tools.Frameworks.newConfigBuilder(Frameworks.java:201)
at
org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.(CalciteQueryProcessor.java:73)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.ignite.internal.util.IgniteUtils.inClassPath(IgniteUtils.java:1754)
at
org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:181)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1267)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2141)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1787)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1172)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1066)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:952)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:851)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:721)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:690)
at org.apache.ignite.Ignition.start(Ignition.java:353)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:367)
Caused by: java.lang.NullPointerException
at
sun.reflect.annotation.TypeAnnotationParser.mapTypeAnnotations(TypeAnnotationParser.java:356)
at
sun.reflect.annotation.AnnotatedTypeFactory$AnnotatedTypeBaseImpl.(AnnotatedTypeFactory.java:139)
at
sun.reflect.annotation.AnnotatedTypeFactory.buildAnnotatedType(AnnotatedTypeFactory.java:65)
at
sun.reflect.annotation.TypeAnnotationParser.buildAnnotatedType(TypeAnnotationParser.java:79)
at
java.lang.reflect.Executable.getAnnotatedReturnType0(Executable.java:640)
at java.lang.reflect.Method.getAnnotatedReturnType(Method.java:648)
at
org.apache.calcite.util.ImmutableBeans.makeDef(ImmutableBeans.java:146)
at
org.apache.calcite.util.ImmutableBeans.access$000(ImmutableBeans.java:55)
at org.apache.calcite.util.ImmutableBeans$1.load(ImmutableBeans.java:68)
at org.apache.calcite.util.ImmutableBeans$1.load(ImmutableBeans.java:65)
at
com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3527)
at
com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2276)
at
com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2154)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2044)
at com.google.common.cache.LocalCache.get(LocalCache.java:3951)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3973)
at
com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4957)
at
org.apache.calcite.util.ImmutableBeans.create_(ImmutableBeans.java:95)
at org.apache.calcite.util.ImmutableBeans.create(ImmutableBeans.java:76)
at
org.apache.calcite.sql.validate.SqlValidator$Config.(SqlValidator.java:792)
... 19 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15075) Calcite. TRIM function doesn't support multicharacter trim
Yury Gerzhedovich created IGNITE-15075:
--
Summary: Calcite. TRIM function doesn't support multicharacter
trim
Key: IGNITE-15075
URL: https://issues.apache.org/jira/browse/IGNITE-15075
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Yury Gerzhedovich
Most databases support syntaxis with a few characters for trimming, like a
{code:sql}
SELECT trim(both '123' from '123PostgreSQL123');
{code}
Currently, we support only a single character for trimming. Will be good to
support it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15074) Fix documentation for support encrypted snapshots
Vladimir Steshin created IGNITE-15074: - Summary: Fix documentation for support encrypted snapshots Key: IGNITE-15074 URL: https://issues.apache.org/jira/browse/IGNITE-15074 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15068) Ignite giving stale data - when data is inserted/updated and immediately read (from the same client node)
[
https://issues.apache.org/jira/browse/IGNITE-15068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanmay Ambre updated IGNITE-15068:
--
Issue Type: Bug (was: Task)
> Ignite giving stale data - when data is inserted/updated and immediately read
> (from the same client node)
> -
>
> Key: IGNITE-15068
> URL: https://issues.apache.org/jira/browse/IGNITE-15068
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.9, 2.9.1
>Reporter: Tanmay Ambre
>Priority: Major
>
> Hi,
> We have a 18 node (server) cluster for Ignite. We have multiple client nodes
> that connect to ignite and use the cache api to get and put data.
> One of the client node is a Kafka streams application. This application
> receives an event and for each event:
> # we lookup the data using the key in ignite. i.e. cache.get(key)
> # we update the data if we find an entry in ignite i.e. cache.put(key, value)
> # we insert the data if we don't find an entry in ignite i.e. cache.put(key,
> value)
> This application processes more than 30 million events per day. In some
> scenarios we get multiple events for the same key "consecutively" i.e. the
> time difference between consecutive events is not more than 10 to 20
> milliseconds. We are sure they are processed sequentially as they go to the
> same Kafka partition.
> What we have observed is sometimes, the step #1 gives us an old copy of the
> data (not the one which was updated as part of #2).
>
> for e.g. when we get the first event we have following value:
> Key = 1, value = \{version: 1}
> when we get the second event for the same key, we update ignite as:
> Key = 1, value = \{version: 2} //increment version by 1
> when we get the third event for the same key and when we lookup the data in
> ignite instead of getting \{version: 2}, we get {color:#ff}{version:
> 1}{color}
> also sometimes, when we get the second event - we {color:#ff}don't even
> find the entry in ignite{color} (i.e. \{version:1})
> Our caches have the following configuration
> backups = 1
> atomicityMode = ATOMIC
> writeSynchronizationPolicy = PRIMARY_SYNC
> readFromBackup = true (default - we are not setting this)
>
> Is there something wrong? Should we set "readFromBackup = false"?
> unfortunately it is very difficult to replicate since it happens just 50 to
> 100 times in a day (i.e. out of 30 million events).
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15073) C++ Extend platforms API to call Java versioned entry processor
[
https://issues.apache.org/jira/browse/IGNITE-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandr Shapkin updated IGNITE-15073:
--
Affects Version/s: 2.11
> C++ Extend platforms API to call Java versioned entry processor
> ---
>
> Key: IGNITE-15073
> URL: https://issues.apache.org/jira/browse/IGNITE-15073
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.11
>Reporter: Alexandr Shapkin
>Priority: Major
>
> In case of a mixed cluster (Java server and C++ client for sample) it's not
> possible to use an entry processor since it requires a native
> platform-specific implementation to be defined on both sides.
> Let's extend platforms interop API to have a new methods
> cache.invokeJava("key", "java_task_name", args) similar to
> compute.ExecuteJavaTask.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15073) C++ Extend platforms API to call Java versioned entry processor
Alexandr Shapkin created IGNITE-15073:
-
Summary: C++ Extend platforms API to call Java versioned entry
processor
Key: IGNITE-15073
URL: https://issues.apache.org/jira/browse/IGNITE-15073
Project: Ignite
Issue Type: Improvement
Components: platforms
Reporter: Alexandr Shapkin
In case of a mixed cluster (Java server and C++ client for sample) it's not
possible to use an entry processor since it requires a native platform-specific
implementation to be defined on both sides.
Let's extend platforms interop API to have a new methods
cache.invokeJava("key", "java_task_name", args) similar to
compute.ExecuteJavaTask.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15037) Calcite engine. CURRENT_DATE/TIME/TIMESTAMP fails with NPE
[
https://issues.apache.org/jira/browse/IGNITE-15037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376493#comment-17376493
]
Taras Ledkov commented on IGNITE-15037:
---
[~alex_pl], the patch is OK with me.
> Calcite engine. CURRENT_DATE/TIME/TIMESTAMP fails with NPE
> --
>
> Key: IGNITE-15037
> URL: https://issues.apache.org/jira/browse/IGNITE-15037
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The call of the functions
> - CURRENT_TIME
> - CURRENT_DATE
> - CURRENT_TIMESTAMP
> fail with NPE:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.calcite.runtime.SqlFunctions.currentTimestamp(SqlFunctions.java:2480)
> at SC.execute(Unknown Source)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl$ProjectImpl.apply(ExpressionFactoryImpl.java:387)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ProjectNode.push(ProjectNode.java:63)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:107)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:239)
> ... 4 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15041) Travis failed on ignite-spark compilation
[ https://issues.apache.org/jira/browse/IGNITE-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Gidaspov updated IGNITE-15041: - Fix Version/s: 2.11 > Travis failed on ignite-spark compilation > - > > Key: IGNITE-15041 > URL: https://issues.apache.org/jira/browse/IGNITE-15041 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15031) Calcite engine. Parser fails on REPLACE function
[
https://issues.apache.org/jira/browse/IGNITE-15031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-15031:
--
Assignee: Aleksey Plekhanov
> Calcite engine. Parser fails on REPLACE function
>
>
> Key: IGNITE-15031
> URL: https://issues.apache.org/jira/browse/IGNITE-15031
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
>
> The {{REPLACE}} function is declared at the calcite engine
> ({{SqlStdOperatorTable#REPLACE}})
> but parser fails on the query:
> {{SELECT REPLACE('A', 'B' 'C')}}
> with error: {{Encountered "" at line 1, column 8.}}
> Tests:
> {{function/string/test_replace.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15037) Calcite engine. CURRENT_DATE/TIME/TIMESTAMP fails with NPE
[
https://issues.apache.org/jira/browse/IGNITE-15037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376481#comment-17376481
]
Aleksey Plekhanov commented on IGNITE-15037:
[~tledkov-gridgain] can you please have a look at the patch?
> Calcite engine. CURRENT_DATE/TIME/TIMESTAMP fails with NPE
> --
>
> Key: IGNITE-15037
> URL: https://issues.apache.org/jira/browse/IGNITE-15037
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The call of the functions
> - CURRENT_TIME
> - CURRENT_DATE
> - CURRENT_TIMESTAMP
> fail with NPE:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.calcite.runtime.SqlFunctions.currentTimestamp(SqlFunctions.java:2480)
> at SC.execute(Unknown Source)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl$ProjectImpl.apply(ExpressionFactoryImpl.java:387)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ProjectNode.push(ProjectNode.java:63)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:107)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:239)
> ... 4 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14866) Calcite. Check SQL function works
[ https://issues.apache.org/jira/browse/IGNITE-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich reassigned IGNITE-14866: -- Assignee: Yury Gerzhedovich > Calcite. Check SQL function works > - > > Key: IGNITE-14866 > URL: https://issues.apache.org/jira/browse/IGNITE-14866 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: calcite2-required, calcite3-required > > We need to write tests on existing simple SQL functions (nor aggregation or > window functions) and have a list of supported functions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14951) Schema update. Rename column.
[ https://issues.apache.org/jira/browse/IGNITE-14951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376471#comment-17376471 ] Taras Ledkov commented on IGNITE-14951: --- [~amashenkov] the patch is OK with me. > Schema update. Rename column. > - > > Key: IGNITE-14951 > URL: https://issues.apache.org/jira/browse/IGNITE-14951 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Implement evolution converters for rename column schema operation. > Configuration changes should trigger a new schema version adding to schema > history. > Assumes, all nodes will use a new schema after the upgrade. > An old row can be upgraded on-fly using evolution converters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14794) Add JMX command and metrics for automatic snapshot restore operation.
[
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14794:
--
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Add JMX command and metrics for automatic snapshot restore operation.
> --
>
> Key: IGNITE-14794
> URL: https://issues.apache.org/jira/browse/IGNITE-14794
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add JMX command to restore a cache group from the snapshot.
> Suggested methods
> {code:java}
> @MXBeanDescription("Restore cluster-wide snapshot.")
> public void restoreSnapshot(
> @MXBeanParameter(name = "snpName", description = "Snapshot name.")
> String name,
> @MXBeanParameter(name = "cacheGroupNames", description = "Optional
> comma-separated list of cache group names.") String cacheGroupNames);
> @MXBeanDescription("Cancel previously started snapshot restore
> operation.")
> public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
> description = "Snapshot name.") String name);
> {code}
> Since the automatic snapshot restore operation can take a long time, we must
> be able to track its progress using metrics.
> Suggested metrics:
> {noformat}
> start time
> total partitions
> copied partitions
> end time
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13810) Append additional log and metrics info regarding cache expiration.
[ https://issues.apache.org/jira/browse/IGNITE-13810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376425#comment-17376425 ] Stanilovsky Evgeny commented on IGNITE-13810: - [~ksirotkin] do you have any progress here ? > Append additional log and metrics info regarding cache expiration. > --- > > Key: IGNITE-13810 > URL: https://issues.apache.org/jira/browse/IGNITE-13810 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.9 >Reporter: Stanilovsky Evgeny >Assignee: Konstantin Sirotkin >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > Currently we have no any additional information regarding > _cache.withExpiryPolicy_ execution. Additionally it would be very useful to > have a corresponding metric. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14833) Bring back checksum support
[ https://issues.apache.org/jira/browse/IGNITE-14833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-14833: -- Assignee: Vladislav Pyatkov > Bring back checksum support > --- > > Key: IGNITE-14833 > URL: https://issues.apache.org/jira/browse/IGNITE-14833 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently checksum support is disabled. > It has to be fixed and enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14952) Releasing WAL segments when reaching DataStorageConfiguration#maxWalArchiveSize
[ https://issues.apache.org/jira/browse/IGNITE-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376398#comment-17376398 ] Kirill Tkalenko commented on IGNITE-14952: -- Fresh building after adding a log message: https://ci.ignite.apache.org/viewLog.html?buildId=6075750=IgniteTests24Java8_BuildApacheIgnite=buildResultsDiv_IgniteTests24Java8=pull%2F9198%2 > Releasing WAL segments when reaching > DataStorageConfiguration#maxWalArchiveSize > --- > > Key: IGNITE-14952 > URL: https://issues.apache.org/jira/browse/IGNITE-14952 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > When the *DataStorageConfiguration#maxWalArchiveSize* is reached, release the > WAL segments to avoid overflowing the WAL archive. > Do not allow segment reservations to a > *DataStorageConfiguration#minWalArchiveSize*. > Subtask from > [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15072) Make documentation java code snippets compilable
Aleksey Plekhanov created IGNITE-15072: -- Summary: Make documentation java code snippets compilable Key: IGNITE-15072 URL: https://issues.apache.org/jira/browse/IGNITE-15072 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Aleksey Plekhanov The whole purpose of having code snippets in separate java files is to ensure they work (at least compile). But currently, we have a lot of compilation errors introduced in the 2.10 and 2.11 Ignite versions (it was compilable in 2.9). We should fix compilation errors in documentation code snippets and add checks to Travis or TC to maintain it compilable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15071) Fix "update version" script to change version in documentation code snippets
[
https://issues.apache.org/jira/browse/IGNITE-15071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376363#comment-17376363
]
Aleksey Plekhanov commented on IGNITE-15071:
[~agidaspov], can you please have a look? As a 2.11 release manager, you will
need to change the master branch version to 2.12.0-SNAPSHOT (see 6.3.2 step in
"Release Process"). We forgot to include code-snippets to change version
scripts and without the attached patch, it should be done manually.
To check the patch you can run the script with the command
{{./scripts/update-versions.sh 2.12.0-SNAPSHOT}} and then check that version in
{{docs/_docs/code-snippets/java/pom.xml}} is also changed.
> Fix "update version" script to change version in documentation code snippets
>
>
> Key: IGNITE-15071
> URL: https://issues.apache.org/jira/browse/IGNITE-15071
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The script should be modified to automatically update Ignite version in
> "docs/_docs/code-snippets/java/pom.xml"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15071) Fix "update version" script to change version in documentation code snippets
Aleksey Plekhanov created IGNITE-15071: -- Summary: Fix "update version" script to change version in documentation code snippets Key: IGNITE-15071 URL: https://issues.apache.org/jira/browse/IGNITE-15071 Project: Ignite Issue Type: Improvement Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov The script should be modified to automatically update Ignite version in "docs/_docs/code-snippets/java/pom.xml" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15037) Calcite engine. CURRENT_DATE/TIME/TIMESTAMP fails with NPE
[
https://issues.apache.org/jira/browse/IGNITE-15037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-15037:
--
Assignee: Aleksey Plekhanov
> Calcite engine. CURRENT_DATE/TIME/TIMESTAMP fails with NPE
> --
>
> Key: IGNITE-15037
> URL: https://issues.apache.org/jira/browse/IGNITE-15037
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
>
> The call of the functions
> - CURRENT_TIME
> - CURRENT_DATE
> - CURRENT_TIMESTAMP
> fail with NPE:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.calcite.runtime.SqlFunctions.currentTimestamp(SqlFunctions.java:2480)
> at SC.execute(Unknown Source)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl$ProjectImpl.apply(ExpressionFactoryImpl.java:387)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ProjectNode.push(ProjectNode.java:63)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:107)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:239)
> ... 4 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15070) Install Ignite to Solaris Sparc
Ivan Gurov created IGNITE-15070: --- Summary: Install Ignite to Solaris Sparc Key: IGNITE-15070 URL: https://issues.apache.org/jira/browse/IGNITE-15070 Project: Ignite Issue Type: Bug Components: examples Affects Versions: 2.10 Environment: OS: Oracle Solaris 11.4 SPARC Java HotSpot(TM) 64-Bit Server VM (25.291-b10) for solaris-sparc JRE (1.8.0_291-b10) Reporter: Ivan Gurov Fix For: None Hello. We have a project that is built on Oracle Solaris 11.4 SPARC. You need to connect to the Ignite server using a c++thin client. I tried to run the "thin-client-put-get-example" example and got the following error: A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x53455930, pid=28054, tid=0x0001 The log file contains the following information: siginfo: si_signo: 10 (SIGBUS), si_code: 1 (BUS_ADRALN), si_addr: 0x000101b6c68c There is an assumption that the problem is related to the system architecture: RISC -- This message was sent by Atlassian Jira (v8.3.4#803005)
