[jira] [Created] (IGNITE-18488) SQL: SUBSTRING function does not support NULL values
Andrey Khitrin created IGNITE-18488:
---
Summary: SQL: SUBSTRING function does not support NULL values
Key: IGNITE-18488
URL: https://issues.apache.org/jira/browse/IGNITE-18488
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 3.0.0-beta1
Reporter: Andrey Khitrin
ANSI99 SQL specification ("6.18 ") says the following:
{code:java}
3) If is specified, then:
a) Let C be the value of the , ..., and let S be
the value of the .
b) If is specified, then let L be the value of ...
c) If either C, S, or L is the null value, then the result of the is the null value.
{code}
So, we should expect the following behavior:
{code:sql}
SUBSTRING('text' FROM 1 FOR NULL) -> NULL
SUBSTRING('text' FROM NULL FOR 2) -> NULL
SUBSTRING(NULL FROM 1 FOR 2) -> NULL
{code}
Instead, we got errors for these queries:
{code:sql}
sql-cli> SELECT SUBSTRING('text' FROM 1 FOR NULL);
SQL query execution error
Exception while executing query [query=SELECT SUBSTRING('text' FROM 1 FOR
NULL);]. Error message:From line 1, column 8 to line 1, column 40: Cannot apply
'SUBSTRING' to arguments of type 'SUBSTRING( FROM FOR
)'. Supported form(s): 'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
sql-cli> SELECT SUBSTRING('text' FROM NULL FOR 2);
SQL query execution error
Exception while executing query [query=SELECT SUBSTRING('text' FROM NULL FOR
2);]. Error message:From line 1, column 8 to line 1, column 40: Cannot apply
'SUBSTRING' to arguments of type 'SUBSTRING( FROM FOR
)'. Supported form(s): 'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
'SUBSTRING( FROM )'
'SUBSTRING( FROM FOR )'
sql-cli> SELECT SUBSTRING(NULL FROM 1 FOR 2);
(client freezes, no answer at all)
{code}
*Important*: the last query causes {{NullPointerException}} within DB:
{code:java}
2022-12-30 07:32:46:210 +
[WARNING][node1-srv-worker-1][ClientInboundMessageHandler] Error processing
client request
java.lang.NullPointerException
at
org.apache.ignite.internal.sql.SqlColumnTypeConverter.columnTypeToClass(SqlColumnTypeConverter.java:42)
at
org.apache.ignite.client.handler.JdbcQueryCursorHandlerImpl.createColumnMetadata(JdbcQueryCursorHandlerImpl.java:162)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
at
java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at
org.apache.ignite.client.handler.JdbcQueryCursorHandlerImpl.queryMetadataAsync(JdbcQueryCursorHandlerImpl.java:133)
at
org.apache.ignite.client.handler.requests.jdbc.ClientJdbcQueryMetadataRequest.process(ClientJdbcQueryMetadataRequest.java:47)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:454)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:336)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.channelRead(ClientInboundMessageHandler.java:187)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:327)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:299)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at
[jira] [Commented] (IGNITE-18199) Make punch holes in partitions files during restoration of snapshot
[
https://issues.apache.org/jira/browse/IGNITE-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653040#comment-17653040
]
Ignite TC Bot commented on IGNITE-18199:
{panel:title=Branch: [pull/10468/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10468/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Disk Page Compressions 1{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6978817]]
* {color:#013220}IgnitePdsCompressionTestSuite:
SnapshotCompressionBasicTest.testRestoreFullSnapshot_OnLargerTopology[Encryption=false]
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6978819buildTypeId=IgniteTests24Java8_RunAll]
> Make punch holes in partitions files during restoration of snapshot
> ---
>
> Key: IGNITE-18199
> URL: https://issues.apache.org/jira/browse/IGNITE-18199
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.14
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: ise
> Fix For: 2.15
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-16037) Benchmark Ignite 3 transactions
[ https://issues.apache.org/jira/browse/IGNITE-16037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-16037. -- Resolution: Won't Fix > Benchmark Ignite 3 transactions > --- > > Key: IGNITE-16037 > URL: https://issues.apache.org/jira/browse/IGNITE-16037 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > > Need to benchmark and evaluate the current approach of Ignite transactions. > Is it suitable with SQL? Is the new approach comparable with Ignite 2 > transactions? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14884) Shutdown policy and well-defined scale down protocol
[ https://issues.apache.org/jira/browse/IGNITE-14884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14884. -- Resolution: Won't Fix > Shutdown policy and well-defined scale down protocol > > > Key: IGNITE-14884 > URL: https://issues.apache.org/jira/browse/IGNITE-14884 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14882) Define minimal list of required metrics to monitor baseline and cluster state
[ https://issues.apache.org/jira/browse/IGNITE-14882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14882. -- Resolution: Won't Fix > Define minimal list of required metrics to monitor baseline and cluster state > - > > Key: IGNITE-14882 > URL: https://issues.apache.org/jira/browse/IGNITE-14882 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14880) Partition loss policies. Provide a useful and convenient way to list unavailable/offline partitions
[ https://issues.apache.org/jira/browse/IGNITE-14880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14880. -- Resolution: Won't Fix > Partition loss policies. Provide a useful and convenient way to list > unavailable/offline partitions > --- > > Key: IGNITE-14880 > URL: https://issues.apache.org/jira/browse/IGNITE-14880 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14878) Introduce table space/group concept
[ https://issues.apache.org/jira/browse/IGNITE-14878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14878. -- Resolution: Won't Fix > Introduce table space/group concept > --- > > Key: IGNITE-14878 > URL: https://issues.apache.org/jira/browse/IGNITE-14878 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14883) Managing metastorage group via CLI
[ https://issues.apache.org/jira/browse/IGNITE-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14883. -- Resolution: Won't Fix > Managing metastorage group via CLI > -- > > Key: IGNITE-14883 > URL: https://issues.apache.org/jira/browse/IGNITE-14883 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14881) Managing baseline via CLI
[ https://issues.apache.org/jira/browse/IGNITE-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14881. -- Resolution: Won't Fix > Managing baseline via CLI > - > > Key: IGNITE-14881 > URL: https://issues.apache.org/jira/browse/IGNITE-14881 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14877) Introduce API in order to manage metastorage group
[ https://issues.apache.org/jira/browse/IGNITE-14877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14877. -- Resolution: Won't Fix > Introduce API in order to manage metastorage group > -- > > Key: IGNITE-14877 > URL: https://issues.apache.org/jira/browse/IGNITE-14877 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14875) Define API of cluster node and move it from network component to the public API
[ https://issues.apache.org/jira/browse/IGNITE-14875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14875. -- Resolution: Won't Fix > Define API of cluster node and move it from network component to the public > API > --- > > Key: IGNITE-14875 > URL: https://issues.apache.org/jira/browse/IGNITE-14875 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14879) Create custom policies to adjust list of data nodes (baseline nodes)
[ https://issues.apache.org/jira/browse/IGNITE-14879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14879. -- Resolution: Won't Fix > Create custom policies to adjust list of data nodes (baseline nodes) > > > Key: IGNITE-14879 > URL: https://issues.apache.org/jira/browse/IGNITE-14879 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14876) Define Ignite Cluster API: cluster/node states, run-levels and their semantics
[ https://issues.apache.org/jira/browse/IGNITE-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14876. -- Resolution: Won't Fix > Define Ignite Cluster API: cluster/node states, run-levels and their semantics > -- > > Key: IGNITE-14876 > URL: https://issues.apache.org/jira/browse/IGNITE-14876 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14874) Need to define/Introduce consistent identifier term
[ https://issues.apache.org/jira/browse/IGNITE-14874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14874. -- Resolution: Won't Fix > Need to define/Introduce consistent identifier term > --- > > Key: IGNITE-14874 > URL: https://issues.apache.org/jira/browse/IGNITE-14874 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > > Currently, ignite node uses "name" as its primary identifier (along with > internal id). Need to get an agreement which term should be used: "name", > "instanceName", "consistentId" and update code in accordance with it. > I saw the property ClusterNode#name is using like a consistent id. We are > using other term in the network module and CLI : > RecoveryServerHandshakeManager#consistentId > RecoveryClientHandshakeManager#consistentId > HandshakeStartMessageBuilder#consistentId(java.lang.String) > ConnectionManager#consistentId > StopNodeCommandSpec#consistentIds > I’m assuming only one term should stay into after. Also, this change has to > apply to documentation(read.me). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14716) Introduce and adapt baseline topology concept into AI3.0
[ https://issues.apache.org/jira/browse/IGNITE-14716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14716. -- Resolution: Duplicate This functionality will be covered by the distribution zones concept. See IGNITE-17924 for details. > Introduce and adapt baseline topology concept into AI3.0 > > > Key: IGNITE-14716 > URL: https://issues.apache.org/jira/browse/IGNITE-14716 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > > Need to adapt the concept of baseline topology (introduced by > [IEP-4|https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches]) > to Ignite 3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14233) Metrics framework
[ https://issues.apache.org/jira/browse/IGNITE-14233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14233. -- Resolution: Duplicate duplicates https://issues.apache.org/jira/browse/IGNITE-17353 > Metrics framework > - > > Key: IGNITE-14233 > URL: https://issues.apache.org/jira/browse/IGNITE-14233 > Project: Ignite > Issue Type: New Feature >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > > Need to adapt and port metrics framework from AI2.x to AI3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17833) [Native Persistence 3.0] Implement partition destruction for volatile PageMemory
[ https://issues.apache.org/jira/browse/IGNITE-17833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy reassigned IGNITE-17833: -- Assignee: Roman Puchkovskiy > [Native Persistence 3.0] Implement partition destruction for volatile > PageMemory > > > Key: IGNITE-17833 > URL: https://issues.apache.org/jira/browse/IGNITE-17833 > Project: Ignite > Issue Type: Task >Reporter: Ivan Bessonov >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > > At the moment, the partition destruction operation does not work quite > correctly, we just go through all the records and explicitly delete them. > But, this operation is synchronous and doesn't destroy other associated > resources, like tree itself or indexes. > *Thoughts:* > We need to destroy all resources associated with the volatile partition, but > we do not need to wait for the destruction of resources. > It is enough for us to untie resources (structure roots) and delete them in > the background. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18451) Node stop may hang if an index is not created yet
[ https://issues.apache.org/jira/browse/IGNITE-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-18451: --- Reviewer: Aleksandr Polovtcev > Node stop may hang if an index is not created yet > - > > Key: IGNITE-18451 > URL: https://issues.apache.org/jira/browse/IGNITE-18451 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > # Start and init a cluster of 3 nodes > # Via node 0, create a table with 3 replicas > # Do some stuff > # Stop the cluster > The cluster cannot be stoppled, stop of node 2 seems to hang forever. There > is a thread: > "%itrst_tsimwkpn_2%JRaft-FSMCaller-Disruptor-_stripe_3-0" #253053 daemon > prio=5 os_prio=0 cpu=0,59ms elapsed=1169,99s tid=0x7fb4867e3000 > nid=0xa1668 waiting on condition [0x7fb4832f] > java.lang.Thread.State: WAITING (parking) > at jdk.internal.misc.Unsafe.park(java.base@11.0.6/Native Method) > - parking to wait for <0x000707d9a508> (a > java.util.concurrent.CompletableFuture$Signaller) > at > java.util.concurrent.locks.LockSupport.park(java.base@11.0.6/LockSupport.java:194) > at > java.util.concurrent.CompletableFuture$Signaller.block(java.base@11.0.6/CompletableFuture.java:1796) > at > java.util.concurrent.ForkJoinPool.managedBlock(java.base@11.0.6/ForkJoinPool.java:3128) > at > java.util.concurrent.CompletableFuture.waitingGet(java.base@11.0.6/CompletableFuture.java:1823) > at > java.util.concurrent.CompletableFuture.join(java.base@11.0.6/CompletableFuture.java:2043) > at org.apache.ignite.internal.table.TableImpl.pkId(TableImpl.java:126) > at > org.apache.ignite.internal.table.TableImpl.awaitIndexes(TableImpl.java:347) > at > org.apache.ignite.internal.table.TableImpl.lambda$indexStorageAdapters$0(TableImpl.java:237) > at > org.apache.ignite.internal.table.TableImpl$$Lambda$1842/0x000800a2fc40.get(Unknown > Source) > at > org.apache.ignite.internal.table.distributed.raft.PartitionListener.addToIndexes(PartitionListener.java:435) > at > org.apache.ignite.internal.table.distributed.raft.PartitionListener.lambda$handleUpdateAllCommand$5(PartitionListener.java:234) > at > org.apache.ignite.internal.table.distributed.raft.PartitionListener$$Lambda$2551/0x000800ceb440.execute(Unknown > Source) > at > org.apache.ignite.internal.storage.rocksdb.RocksDbMvPartitionStorage.runConsistently(RocksDbMvPartitionStorage.java:249) > at > org.apache.ignite.internal.table.distributed.raft.snapshot.outgoing.SnapshotAwarePartitionDataStorage.runConsistently(SnapshotAwarePartitionDataStorage.java:59) > at > org.apache.ignite.internal.table.distributed.raft.PartitionListener.handleUpdateAllCommand(PartitionListener.java:219) > at > org.apache.ignite.internal.table.distributed.raft.PartitionListener.lambda$onWrite$1(PartitionListener.java:153) > at > org.apache.ignite.internal.table.distributed.raft.PartitionListener$$Lambda$1944/0x000800a7a440.accept(Unknown > Source) > at java.util.Iterator.forEachRemaining(java.base@11.0.6/Iterator.java:133) > at > org.apache.ignite.internal.table.distributed.raft.PartitionListener.onWrite(PartitionListener.java:123) > at > org.apache.ignite.internal.raft.server.impl.JraftServerImpl$DelegatingStateMachine.onApply(JraftServerImpl.java:563) > at > org.apache.ignite.raft.jraft.core.FSMCallerImpl.doApplyTasks(FSMCallerImpl.java:565) > at > org.apache.ignite.raft.jraft.core.FSMCallerImpl.doCommitted(FSMCallerImpl.java:530) > at > org.apache.ignite.raft.jraft.core.FSMCallerImpl.runApplyTask(FSMCallerImpl.java:449) > at > org.apache.ignite.raft.jraft.core.FSMCallerImpl$ApplyTaskHandler.onEvent(FSMCallerImpl.java:137) > at > org.apache.ignite.raft.jraft.core.FSMCallerImpl$ApplyTaskHandler.onEvent(FSMCallerImpl.java:131) > at > org.apache.ignite.raft.jraft.disruptor.StripedDisruptor$StripeEntryHandler.onEvent(StripedDisruptor.java:217) > at > org.apache.ignite.raft.jraft.disruptor.StripedDisruptor$StripeEntryHandler.onEvent(StripedDisruptor.java:181) > at > com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:137) > at java.lang.Thread.run(java.base@11.0.6/Thread.java:834) > Probably the node stop was initiated before the indices were created for the > table, then index manager was stopped, so the indices never get created. But > only index creation completes the future that is being avaited by the shown > thread. > This might have something to do with IGNITE-18203. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17235) Fix flaky ItBplusTreePageMemoryImplTest#testPutSizeLivelock
[ https://issues.apache.org/jira/browse/IGNITE-17235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-17235: - Reviewer: Aleksandr Polovtcev > Fix flaky ItBplusTreePageMemoryImplTest#testPutSizeLivelock > --- > > Key: IGNITE-17235 > URL: https://issues.apache.org/jira/browse/IGNITE-17235 > Project: Ignite > Issue Type: Bug >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > It is necessary to investigate and fix the falling flaky > [ItBplusTreePageMemoryImplTest#testPutSizeLivelock|https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6647751?logFilter=debug] > test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-5713) The ignite-spring module should not rely on the ignite-indexing module.
[ https://issues.apache.org/jira/browse/IGNITE-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-5713: -- Release Note: Removed redundant ignite-indexing module dependencies. Warning: if you use SQL in Ignite and get Ignite dependency via maven, check that you have explicit dependency to the one of the SQL engines (ignite-indexing or ignite-calcite) > The ignite-spring module should not rely on the ignite-indexing module. > --- > > Key: IGNITE-5713 > URL: https://issues.apache.org/jira/browse/IGNITE-5713 > Project: Ignite > Issue Type: Improvement > Components: spring >Affects Versions: 2.0 >Reporter: YuJue Li >Assignee: Aleksey Plekhanov >Priority: Minor > Fix For: 2.15 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In version 2.0, the ignite-spring module has increased reliance on the > ignite-indexing module, which is not appropriate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18427) .NET: Platform cache is not updated when ReadFromBackup is true
[ https://issues.apache.org/jira/browse/IGNITE-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-18427: Release Note: .NET: Fixed platform cache invalidation on client nodes with near cache. > .NET: Platform cache is not updated when ReadFromBackup is true > --- > > Key: IGNITE-18427 > URL: https://issues.apache.org/jira/browse/IGNITE-18427 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.14 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ise > Fix For: 2.15 > > Attachments: IgniteReproducer.csproj, Test.cs > > Time Spent: 10m > Remaining Estimate: 0h > > See attached reproducer. Client 2 has stale value when *ReadFromBackup = > true*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18427) .NET: Platform cache is not updated when ReadFromBackup is true
[ https://issues.apache.org/jira/browse/IGNITE-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652824#comment-17652824 ] Pavel Tupitsyn commented on IGNITE-18427: - Merged to master: db7758ce66bef167e14030ceaee2ef34ffb1e696 > .NET: Platform cache is not updated when ReadFromBackup is true > --- > > Key: IGNITE-18427 > URL: https://issues.apache.org/jira/browse/IGNITE-18427 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.14 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ise > Fix For: 2.15 > > Attachments: IgniteReproducer.csproj, Test.cs > > Time Spent: 10m > Remaining Estimate: 0h > > See attached reproducer. Client 2 has stale value when *ReadFromBackup = > true*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-5713) The ignite-spring module should not rely on the ignite-indexing module.
[ https://issues.apache.org/jira/browse/IGNITE-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652823#comment-17652823 ] Aleksey Plekhanov commented on IGNITE-5713: --- Fix for ignite-extensions merged to master branch. > The ignite-spring module should not rely on the ignite-indexing module. > --- > > Key: IGNITE-5713 > URL: https://issues.apache.org/jira/browse/IGNITE-5713 > Project: Ignite > Issue Type: Improvement > Components: spring >Affects Versions: 2.0 >Reporter: YuJue Li >Assignee: Aleksey Plekhanov >Priority: Minor > Fix For: 2.15 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In version 2.0, the ignite-spring module has increased reliance on the > ignite-indexing module, which is not appropriate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18427) .NET: Platform cache is not updated when ReadFromBackup is true
[ https://issues.apache.org/jira/browse/IGNITE-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652820#comment-17652820 ] Alexandr Shapkin commented on IGNITE-18427: --- [~ptupitsyn], looks good to me, thanks! > .NET: Platform cache is not updated when ReadFromBackup is true > --- > > Key: IGNITE-18427 > URL: https://issues.apache.org/jira/browse/IGNITE-18427 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.14 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ise > Fix For: 2.15 > > Attachments: IgniteReproducer.csproj, Test.cs > > > See attached reproducer. Client 2 has stale value when *ReadFromBackup = > true*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17235) Fix flaky ItBplusTreePageMemoryImplTest#testPutSizeLivelock
[ https://issues.apache.org/jira/browse/IGNITE-17235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko reassigned IGNITE-17235: Assignee: Kirill Tkalenko > Fix flaky ItBplusTreePageMemoryImplTest#testPutSizeLivelock > --- > > Key: IGNITE-17235 > URL: https://issues.apache.org/jira/browse/IGNITE-17235 > Project: Ignite > Issue Type: Bug >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > It is necessary to investigate and fix the falling flaky > [ItBplusTreePageMemoryImplTest#testPutSizeLivelock|https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6647751?logFilter=debug] > test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-18466) InternalTable#scan could push more data than requested
[ https://issues.apache.org/jira/browse/IGNITE-18466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich resolved IGNITE-18466. Resolution: Invalid > InternalTable#scan could push more data than requested > -- > > Key: IGNITE-18466 > URL: https://issues.apache.org/jira/browse/IGNITE-18466 > Project: Ignite > Issue Type: Bug >Reporter: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > > org.apache.ignite.internal.table.InternalTable#scan publisher could return > more data then requested. Required investigate reason and fix it. > As reproducer could be used commented code in TableScanNode#scan method. > After fix the code should be uncommented. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-18458) Sql DML on non-existent table raise NPE
[
https://issues.apache.org/jira/browse/IGNITE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652453#comment-17652453
]
Ilhom Ulmasov edited comment on IGNITE-18458 at 12/29/22 10:10 AM:
---
[~alexpl] could you, please, take a look on the PR?
was (Author: JIRAUSER298475):
[~alex_pl] could you, please, take a look on the PR?
> Sql DML on non-existent table raise NPE
> ---
>
> Key: IGNITE-18458
> URL: https://issues.apache.org/jira/browse/IGNITE-18458
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Ilhom Ulmasov
>Assignee: Ilhom Ulmasov
>Priority: Minor
> Labels: calcite, calcite3-required, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DML operation (INSERT, UPDATE, DELETE, MERGE) raise NullPointerException on
> Calcite engine, if operation is made on non-existent table.
> Steps to reproduce.
> * Connect to DB by using JDBC driver
> * Execute any DML operation on non-existent table. For example
> {code:java}
> INSERT INTO PERSONBLABLABLA(ID, NAME, AGE) VALUES(1, 'JOHN', 3){code}
> * Exception message *Failed to validate query.
> java.lang.NullPointerException* will be returned
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18458) Sql DML on non-existent table raise NPE
[
https://issues.apache.org/jira/browse/IGNITE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652792#comment-17652792
]
Ignite TC Bot commented on IGNITE-18458:
{panel:title=Branch: [pull/10464/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10464/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6976193]]
* {color:#013220}IgniteCalciteTestSuite:
JdbcQueryTest.testDmlOnNonExistentTable - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6976274buildTypeId=IgniteTests24Java8_RunAll]
> Sql DML on non-existent table raise NPE
> ---
>
> Key: IGNITE-18458
> URL: https://issues.apache.org/jira/browse/IGNITE-18458
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Ilhom Ulmasov
>Assignee: Ilhom Ulmasov
>Priority: Minor
> Labels: calcite, calcite3-required, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DML operation (INSERT, UPDATE, DELETE, MERGE) raise NullPointerException on
> Calcite engine, if operation is made on non-existent table.
> Steps to reproduce.
> * Connect to DB by using JDBC driver
> * Execute any DML operation on non-existent table. For example
> {code:java}
> INSERT INTO PERSONBLABLABLA(ID, NAME, AGE) VALUES(1, 'JOHN', 3){code}
> * Exception message *Failed to validate query.
> java.lang.NullPointerException* will be returned
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18163) Old-style join on different column types fails with ClassCastException
[
https://issues.apache.org/jira/browse/IGNITE-18163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky reassigned IGNITE-18163:
---
Assignee: (was: Evgeny Stanilovsky)
> Old-style join on different column types fails with ClassCastException
> --
>
> Key: IGNITE-18163
> URL: https://issues.apache.org/jira/browse/IGNITE-18163
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> Query:
> {code}
> select _T0.KEY, _T1.VAL from PUBLIC.TBL1 as _T0, PUBLIC.TBL_INT32 as _T1
> where _T0.KEY IS NOT DISTINCT FROM _T1.KEY
> {code}
> Result:
> {code}
> org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:ef4217b1-04ef-4f08-b1c3-76effc3fc262 class java.lang.Long cannot be
> cast to class java.lang.Integer (java.lang.Long and java.lang.Integer are in
> module java.base of loader 'bootstrap')
> at org.apache.ignite.lang.IgniteException.wrap(IgniteException.java:289)
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:77)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:193)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:193)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.MergeJoinNode$1.onError(MergeJoinNode.java:124)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:205)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$2(ExchangeServiceImpl.java:81)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:164)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$3(MessageServiceImpl.java:133)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:80)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.ClassCastException: class java.lang.Long cannot be cast
> to class java.lang.Integer (java.lang.Long and java.lang.Integer are in
> module java.base of loader 'bootstrap')
> at java.base/java.lang.Integer.compareTo(Integer.java:59)
> at
> org.apache.calcite.rel.RelFieldCollation.compare(RelFieldCollation.java:43)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl.compare(ExpressionFactoryImpl.java:235)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl$2.compare(ExpressionFactoryImpl.java:217)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.MergeJoinNode$InnerJoin.join(MergeJoinNode.java:318)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.MergeJoinNode.pushLeft(MergeJoinNode.java:162)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.MergeJoinNode$1.push(MergeJoinNode.java:112)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushOrdered(Inbox.java:259)
> at
>
[jira] [Commented] (IGNITE-18163) Old-style join on different column types fails with ClassCastException
[
https://issues.apache.org/jira/browse/IGNITE-18163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652788#comment-17652788
]
Evgeny Stanilovsky commented on IGNITE-18163:
-
additionaly :
{noformat}
create table t1 (c0 integer, c1 varchar(10));
insert into t1 values (1,NULL),(2,3.0),(NULL,NULL);
create table t3 (c1 bigint);
insert into t3 values (1),(2),(3),(NULL);
select _T0.c1, _T1.c1 from t1 as _T0, t3 as _T1 where _T0.c1 = _T1.c1
{noformat}
need to return:
3.03
seems in scope of this issue we need to check all possible types comparisons
with all possible join algo
> Old-style join on different column types fails with ClassCastException
> --
>
> Key: IGNITE-18163
> URL: https://issues.apache.org/jira/browse/IGNITE-18163
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> Query:
> {code}
> select _T0.KEY, _T1.VAL from PUBLIC.TBL1 as _T0, PUBLIC.TBL_INT32 as _T1
> where _T0.KEY IS NOT DISTINCT FROM _T1.KEY
> {code}
> Result:
> {code}
> org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:ef4217b1-04ef-4f08-b1c3-76effc3fc262 class java.lang.Long cannot be
> cast to class java.lang.Integer (java.lang.Long and java.lang.Integer are in
> module java.base of loader 'bootstrap')
> at org.apache.ignite.lang.IgniteException.wrap(IgniteException.java:289)
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:77)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:193)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:193)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.MergeJoinNode$1.onError(MergeJoinNode.java:124)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:155)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:205)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$2(ExchangeServiceImpl.java:81)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:164)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$3(MessageServiceImpl.java:133)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:80)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.ClassCastException: class java.lang.Long cannot be cast
> to class java.lang.Integer (java.lang.Long and java.lang.Integer are in
> module java.base of loader 'bootstrap')
> at java.base/java.lang.Integer.compareTo(Integer.java:59)
> at
> org.apache.calcite.rel.RelFieldCollation.compare(RelFieldCollation.java:43)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl.compare(ExpressionFactoryImpl.java:235)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl$2.compare(ExpressionFactoryImpl.java:217)
> at
>
[jira] [Updated] (IGNITE-18487) [TC Bot] Need to notify about TC Bot starting and stopping
[ https://issues.apache.org/jira/browse/IGNITE-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-18487: --- Description: To slightly increase the availability of the bot, we need the bot send messages to the slack chat in order to respond to its stop in time and authorize the bot in time after the start. (was: To slightly increase the availability of the bot, we need the bot send messages to the chat in order to respond to its stop in time and authorize the bot in time after the start.) > [TC Bot] Need to notify about TC Bot starting and stopping > -- > > Key: IGNITE-18487 > URL: https://issues.apache.org/jira/browse/IGNITE-18487 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > > To slightly increase the availability of the bot, we need the bot send > messages to the slack chat in order to respond to its stop in time and > authorize the bot in time after the start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18487) [TC Bot] Need to notify about TC Bot starting and stopping
[ https://issues.apache.org/jira/browse/IGNITE-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-18487: --- Summary: [TC Bot] Need to notify about TC Bot starting and stopping (was: [TC Bot] Need to add notify about TC Bot starting and stopping) > [TC Bot] Need to notify about TC Bot starting and stopping > -- > > Key: IGNITE-18487 > URL: https://issues.apache.org/jira/browse/IGNITE-18487 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > > To slightly increase the availability of the bot, we need the bot send > messages to the chat in order to respond to its stop in time and authorize > the bot in time after the start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18487) [TC Bot] Need to add notify about TC Bot starting and stopping
Sergey Uttsel created IGNITE-18487: -- Summary: [TC Bot] Need to add notify about TC Bot starting and stopping Key: IGNITE-18487 URL: https://issues.apache.org/jira/browse/IGNITE-18487 Project: Ignite Issue Type: Improvement Reporter: Sergey Uttsel Assignee: Sergey Uttsel To slightly increase the availability of the bot, we need the bot send messages to the chat in order to respond to its stop in time and authorize the bot in time after the start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18486) IgniteToKafkaCdcStreamer implicitely creates topic with wrong partitions number
[
https://issues.apache.org/jira/browse/IGNITE-18486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-18486:
-
Labels: IEP-59 ise (was: )
> IgniteToKafkaCdcStreamer implicitely creates topic with wrong partitions
> number
> ---
>
> Key: IGNITE-18486
> URL: https://issues.apache.org/jira/browse/IGNITE-18486
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Sergey Korotkov
>Priority: Minor
> Labels: IEP-59, ise
>
> If Kafka topic specified in the {{IgniteToKafkaCdcStreamer}}'s property is
> absent it's created implicitely with the default number of partitions (which
> is 1).
> {quote}
> {{INFO [KafkaApi-1] Auto creation of topic ignite with 1 partitions and
> replication factor 1 is successful (kafka.server.KafkaApis)}}{quote}
> So {{IgniteToKafkaCdcStreamer}} ignores the {{kafkaPartitions}} property in
> this case.
> Looks like that {{IgniteToKafkaCdcStreamer}} should either refuse to work if
> topic is absent or create it respecting the {{kafkaPartitions}} property.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18484) Mismatched transaction id
[
https://issues.apache.org/jira/browse/IGNITE-18484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-18484:
--
Labels: ignite-3 (was: )
> Mismatched transaction id
> -
>
> Key: IGNITE-18484
> URL: https://issues.apache.org/jira/browse/IGNITE-18484
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 3.0.0-beta1
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> During the TPC-H test runs I got a problem:
> 1) Create TPC-H database
> 2) Execute "select count(*) from LINEITEM;" throw JDBC connection
> 3) Get exception:
>
> {noformat}
> [Code: 0, SQL State: 5] Exception while executing query [query=select
> count(*) from LINEITEM]. Error message:IGN-CMN-65535
> TraceId:294a2e0a-29e8-448c-abdb-7944b335deb3 IGN-TX-5
> TraceId:b582a4be-2ef1-455f-8e70-80a21e8bcc2e Failed to acquire a lock due to
> a conflict [txId=000ea0e8-bbc4--1cb0-c18823b1fa69,
> conflictingWaiter=WaiterImpl [txId=000e9f97-4be0--1cb0-c18823b1fa69,
> intendedLockMode=null, lockMode=IX, ex=null, isDone=true]]{noformat}
> and in the server logs:
>
>
> {noformat}
> Dec 29, 2022 6:32:29 AM org.apache.ignite.internal.logger.IgniteLogger
> logInternal
> WARNING: Failed to process replica request
> [request=ReadWriteScanRetrieveBatchReplicaRequestImpl [batchSize=512,
> columnsToInclude=null, exactKey=null, flags=0,
> groupId=a804d8a4-ae2d-4fc2-bd6f-e40318297fa7_part_0, indexToUse=null,
> lowerBound=null, scanId=603, term=1, timestamp=HybridTimestamp
> [physical=1672288349125, logical=0],
> transactionId=000ea0e8-bbc4--1cb0-c18823b1fa69, upperBound=null]]
> java.util.concurrent.CompletionException:
> org.apache.ignite.internal.tx.LockException: IGN-TX-5
> TraceId:b582a4be-2ef1-455f-8e70-80a21e8bcc2e Failed to acquire a lock due to
> a conflict [txId=000ea0e8-bbc4--1cb0-c18823b1fa69,
> conflictingWaiter=WaiterImpl [txId=000e9f97-4be0--1cb0-c18823b1fa69,
> intendedLockMode=null, lockMode=IX, ex=null, isDone=true]]
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:670)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.internal.tx.impl.HeapLockManager.acquire(HeapLockManager.java:103)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processScanRetrieveBatchAction(PartitionReplicaListener.java:604)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$invoke$0(PartitionReplicaListener.java:264)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.lambda$sendWithRetry$38(RaftGroupServiceImpl.java:539)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at
> java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
> Caused by: org.apache.ignite.internal.tx.LockException: IGN-TX-5
> TraceId:b582a4be-2ef1-455f-8e70-80a21e8bcc2e Failed to acquire a lock due to
> a conflict [txId=000ea0e8-bbc4--1cb0-c18823b1fa69,
> conflictingWaiter=WaiterImpl [txId=000e9f97-4be0--1cb0-c18823b1fa69,
> intendedLockMode=null, lockMode=IX, ex=null, isDone=true]]
> at
> org.apache.ignite.internal.tx.impl.HeapLockManager$LockState.lockException(HeapLockManager.java:303)
> at
> org.apache.ignite.internal.tx.impl.HeapLockManager$LockState.isWaiterReadyToNotify(HeapLockManager.java:281)
> at
> org.apache.ignite.internal.tx.impl.HeapLockManager$LockState.tryAcquire(HeapLockManager.java:230)
> at
>
[jira] [Commented] (IGNITE-18473) Prevent CdcKafkaReplicationAppsTest from stopping a build
[
https://issues.apache.org/jira/browse/IGNITE-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652766#comment-17652766
]
Ignite TC Bot commented on IGNITE-18473:
{panel:title=Branch: [pull/10466/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10466/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6977918buildTypeId=IgniteTests24Java8_RunAll]
> Prevent CdcKafkaReplicationAppsTest from stopping a build
> -
>
> Key: IGNITE-18473
> URL: https://issues.apache.org/jira/browse/IGNITE-18473
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: IEP-59, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CdcKafkaReplicationAppsTest stops JVM with exit code 255 which causes full
> build stop [1, 2].
> Build log contains such lines:
> {code}
> [21:08:45] : [Step 3/3] [2022-12-27T21:08:45,376][INFO
> ][cdc-shutdown-hook][] Stopping Change Data Capture service instance
> ...
> [21:08:46]E: [Step 3/3] Process exited with code 255 (Step: Run Extension's
> tests (Maven))
> {code}
> And such error is in log:
> {code}
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1257)
> at java.lang.Thread.join(Thread.java:1331)
> at
> org.apache.ignite.startup.cmdline.CdcCommandLineStartup.main(CdcCommandLineStartup.java:95)
> at
> org.apache.ignite.cdc.kafka.CdcKafkaReplicationAppsTest.lambda$igniteToKafka$b1982e5$1(CdcKafkaReplicationAppsTest.java:126)
> at org.apache.ignite.internal.util.lang.RunnableX.run(RunnableX.java:37)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$3(GridTestUtils.java:1176)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$4(GridTestUtils.java:1232)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1573)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:88)
> Failed to run CDC: null
> {code}
> Links:
> #
> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6978239?hideProblemsFromDependencies=false=false=true
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6970356?hideProblemsFromDependencies=false=false=true
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18486) IgniteToKafkaCdcStreamer implicitely creates topic with wrong partitions number
[
https://issues.apache.org/jira/browse/IGNITE-18486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-18486:
-
Description:
If Kafka topic specified in the {{IgniteToKafkaCdcStreamer}}'s property is
absent it's created implicitely with the default number of partitions (which is
1).
{quote}
{{INFO [KafkaApi-1] Auto creation of topic ignite with 1 partitions and
replication factor 1 is successful (kafka.server.KafkaApis)}}{quote}
So {{IgniteToKafkaCdcStreamer}} ignores the {{kafkaPartitions}} property in
this case.
Looks like that {{IgniteToKafkaCdcStreamer}} should either refuse to work if
topic is absent or create it respecting the {{kafkaPartitions}} property.
was:
If Kafka topic specified in the {{IgniteToKafkaCdcStreamer}}'s property is
absent it's created implicitely with the default number of partitions (which is
1).
So {{IgniteToKafkaCdcStreamer}} ignores the {{kafkaPartitions}} property in
this case.
Looks like that {{IgniteToKafkaCdcStreamer}} should either refuse to work if
topic is absent or create it respecting the {{kafkaPartitions}} property.
> IgniteToKafkaCdcStreamer implicitely creates topic with wrong partitions
> number
> ---
>
> Key: IGNITE-18486
> URL: https://issues.apache.org/jira/browse/IGNITE-18486
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Sergey Korotkov
>Priority: Minor
>
> If Kafka topic specified in the {{IgniteToKafkaCdcStreamer}}'s property is
> absent it's created implicitely with the default number of partitions (which
> is 1).
> {quote}
> {{INFO [KafkaApi-1] Auto creation of topic ignite with 1 partitions and
> replication factor 1 is successful (kafka.server.KafkaApis)}}{quote}
> So {{IgniteToKafkaCdcStreamer}} ignores the {{kafkaPartitions}} property in
> this case.
> Looks like that {{IgniteToKafkaCdcStreamer}} should either refuse to work if
> topic is absent or create it respecting the {{kafkaPartitions}} property.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18486) IgniteToKafkaCdcStreamer implicitely creates topic with wrong partitions number
[
https://issues.apache.org/jira/browse/IGNITE-18486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-18486:
-
Component/s: extensions
> IgniteToKafkaCdcStreamer implicitely creates topic with wrong partitions
> number
> ---
>
> Key: IGNITE-18486
> URL: https://issues.apache.org/jira/browse/IGNITE-18486
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Sergey Korotkov
>Priority: Minor
>
> If Kafka topic specified in the {{IgniteToKafkaCdcStreamer}}'s property is
> absent it's created implicitely with the default number of partitions (which
> is 1).
> So {{IgniteToKafkaCdcStreamer}} ignores the {{kafkaPartitions}} property in
> this case.
> Looks like that {{IgniteToKafkaCdcStreamer}} should either refuse to work if
> topic is absent or create it respecting the {{kafkaPartitions}} property.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18486) IgniteToKafkaCdcStreamer implicitely creates topic with wrong partitions number
Sergey Korotkov created IGNITE-18486:
Summary: IgniteToKafkaCdcStreamer implicitely creates topic with
wrong partitions number
Key: IGNITE-18486
URL: https://issues.apache.org/jira/browse/IGNITE-18486
Project: Ignite
Issue Type: Bug
Reporter: Sergey Korotkov
If Kafka topic specified in the {{IgniteToKafkaCdcStreamer}}'s property is
absent it's created implicitely with the default number of partitions (which is
1).
So {{IgniteToKafkaCdcStreamer}} ignores the {{kafkaPartitions}} property in
this case.
Looks like that {{IgniteToKafkaCdcStreamer}} should either refuse to work if
topic is absent or create it respecting the {{kafkaPartitions}} property.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
