[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330048#comment-17330048 ] Kirill Tkalenko commented on IGNITE-14469: -- [~erixon] Please see comments in PR. > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14635) Calcite engine. EXCEPT operator using anti-join
Aleksey Plekhanov created IGNITE-14635:
--
Summary: Calcite engine. EXCEPT operator using anti-join
Key: IGNITE-14635
URL: https://issues.apache.org/jira/browse/IGNITE-14635
Project: Ignite
Issue Type: Improvement
Reporter: Aleksey Plekhanov
Currently, EXCEPT operator implemented as hash aggregation of underlying
inputs, but in some cases ([all=false], inputs are colocated and have required
collations) perhaps anti-join will be more effective (but benchmarking is
needed) and produce streamed output.
For example, query like {{SELECT f1 FROM t1 EXCEPT SELECT f1 FROM t2}} could be
rewritten to {{SELECT DISTINCT f1 FROM t1 ANTI JOIN t2 USING (f1)}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14634) NPE in ShmemClient
[
https://issues.apache.org/jira/browse/IGNITE-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kazakov updated IGNITE-14634:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> NPE in ShmemClient
> --
>
> Key: IGNITE-14634
> URL: https://issues.apache.org/jira/browse/IGNITE-14634
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.10
>Reporter: Ilya Kazakov
>Priority: Major
>
> This code works correctly on 2.7, but do not work on 2.8, 2.9 and 2.10
> {code:java}
> public class T1 {
> static int sharedMemPort = 37235;
> public static void main(String[] args) {
> Ignition.start(getConf("I1"));
> Ignition.start(getConf("I2"));
> }
> public static IgniteConfiguration getConf(String instanceName) {
> return new
> IgniteConfiguration().setIgniteInstanceName(instanceName).setCommunicationSpi(new
> TcpCommunicationSpi().setSharedMemoryPort(sharedMemPort));
> }
> }{code}
> On 2.10
> {code:java}
> [2021-04-23
> 13:06:20,562][ERROR][exchange-worker-#129%I2%][TcpCommunicationSpi] Failed to
> send message to remote node [node=TcpDiscoveryNode
> [id=7469805f-1097-4e49-a0d9-3474a6a792bb,
> consistentId=0:0:0:0:0:0:0:1%lo,127.0.0.1,172.17.0.1,192.168.1.105,192.168.49.1:47500,
> addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 192.168.1.105,
> 192.168.49.1], sockAddrs=HashSet [/172.17.0.1:47500, /192.168.49.1:47500,
> /0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500, /192.168.1.105:47500],
> discPort=47500, order=1, intOrder=1, lastExchangeTime=1619154380497,
> loc=false, ver=2.11.0#20210422-sha1:bec58b00, isClient=false],
> msg=GridIoMessage [plc=2, topic=TOPIC_CACHE, topicOrd=8, ordered=false,
> timeout=0, skipOnTimeout=false, msg=GridDhtPartitionsSingleMessage
> [parts=HashMap {-2100569601=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=-1, minorTopVer=0], updateSeq=1,
> size=0]}, partCntrs=HashMap {-2100569601=CachePartitionPartialCountersMap
> {}}, partsSizes=null, partHistCntrs=null, err=null, client=false,
> exchangeStartTime=1619154380524, finishMsg=null,
> super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0],
> discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=f3b31869-bea3-406c-a8a3-6fe5a502d8c4,
> consistentId=0:0:0:0:0:0:0:1%lo,127.0.0.1,172.17.0.1,192.168.1.105,192.168.49.1:47501,
> addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 192.168.1.105,
> 192.168.49.1], sockAddrs=HashSet [/192.168.49.1:47501,
> /0:0:0:0:0:0:0:1%lo:47501, /127.0.0.1:47501, /192.168.1.105:47501,
> /172.17.0.1:47501], discPort=47501, order=2, intOrder=2,
> lastExchangeTime=1619154380527, loc=true, ver=2.11.0#20210422-sha1:bec58b00,
> isClient=false], topVer=2, msgTemplate=null,
> span=org.apache.ignite.internal.processors.tracing.NoopSpan@4773b242,
> nodeId8=f3b31869, msg=null, type=NODE_JOINED, tstamp=1619154380517],
> nodeId=f3b31869, evt=NODE_JOINED], lastVer=GridCacheVersion [topVer=0,
> order=1619154379141, nodeOrder=0], super=GridCacheMessage [msgId=1,
> depInfo=null, lastAffChangedTopVer=AffinityTopologyVersion [topVer=-1,
> minorTopVer=0], err=null, skipPrepare=false][2021-04-23
> 13:06:20,562][ERROR][exchange-worker-#129%I2%][TcpCommunicationSpi] Failed to
> send message to remote node [node=TcpDiscoveryNode
> [id=7469805f-1097-4e49-a0d9-3474a6a792bb,
> consistentId=0:0:0:0:0:0:0:1%lo,127.0.0.1,172.17.0.1,192.168.1.105,192.168.49.1:47500,
> addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 192.168.1.105,
> 192.168.49.1], sockAddrs=HashSet [/172.17.0.1:47500, /192.168.49.1:47500,
> /0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500, /192.168.1.105:47500],
> discPort=47500, order=1, intOrder=1, lastExchangeTime=1619154380497,
> loc=false, ver=2.11.0#20210422-sha1:bec58b00, isClient=false],
> msg=GridIoMessage [plc=2, topic=TOPIC_CACHE, topicOrd=8, ordered=false,
> timeout=0, skipOnTimeout=false, msg=GridDhtPartitionsSingleMessage
> [parts=HashMap {-2100569601=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=-1, minorTopVer=0], updateSeq=1,
> size=0]}, partCntrs=HashMap {-2100569601=CachePartitionPartialCountersMap
> {}}, partsSizes=null, partHistCntrs=null, err=null, client=false,
> exchangeStartTime=1619154380524, finishMsg=null,
> super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0],
> discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=f3b
[jira] [Created] (IGNITE-14634) NPE in ShmemClient
Ilya Kazakov created IGNITE-14634:
-
Summary: NPE in ShmemClient
Key: IGNITE-14634
URL: https://issues.apache.org/jira/browse/IGNITE-14634
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.10
Reporter: Ilya Kazakov
This code works correctly on 2.7, but do not work on 2.8, 2.9 and 2.10
{code:java}
public class T1 {
static int sharedMemPort = 37235;
public static void main(String[] args) {
Ignition.start(getConf("I1"));
Ignition.start(getConf("I2"));
}
public static IgniteConfiguration getConf(String instanceName) {
return new
IgniteConfiguration().setIgniteInstanceName(instanceName).setCommunicationSpi(new
TcpCommunicationSpi().setSharedMemoryPort(sharedMemPort));
}
}{code}
On 2.10
{code:java}
[2021-04-23 13:06:20,562][ERROR][exchange-worker-#129%I2%][TcpCommunicationSpi]
Failed to send message to remote node [node=TcpDiscoveryNode
[id=7469805f-1097-4e49-a0d9-3474a6a792bb,
consistentId=0:0:0:0:0:0:0:1%lo,127.0.0.1,172.17.0.1,192.168.1.105,192.168.49.1:47500,
addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 192.168.1.105,
192.168.49.1], sockAddrs=HashSet [/172.17.0.1:47500, /192.168.49.1:47500,
/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500, /192.168.1.105:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1619154380497, loc=false,
ver=2.11.0#20210422-sha1:bec58b00, isClient=false], msg=GridIoMessage [plc=2,
topic=TOPIC_CACHE, topicOrd=8, ordered=false, timeout=0, skipOnTimeout=false,
msg=GridDhtPartitionsSingleMessage [parts=HashMap
{-2100569601=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=-1, minorTopVer=0], updateSeq=1, size=0]}, partCntrs=HashMap
{-2100569601=CachePartitionPartialCountersMap {}}, partsSizes=null,
partHistCntrs=null, err=null, client=false, exchangeStartTime=1619154380524,
finishMsg=null, super=GridDhtPartitionsAbstractMessage
[exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=f3b31869-bea3-406c-a8a3-6fe5a502d8c4,
consistentId=0:0:0:0:0:0:0:1%lo,127.0.0.1,172.17.0.1,192.168.1.105,192.168.49.1:47501,
addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 192.168.1.105,
192.168.49.1], sockAddrs=HashSet [/192.168.49.1:47501,
/0:0:0:0:0:0:0:1%lo:47501, /127.0.0.1:47501, /192.168.1.105:47501,
/172.17.0.1:47501], discPort=47501, order=2, intOrder=2,
lastExchangeTime=1619154380527, loc=true, ver=2.11.0#20210422-sha1:bec58b00,
isClient=false], topVer=2, msgTemplate=null,
span=org.apache.ignite.internal.processors.tracing.NoopSpan@4773b242,
nodeId8=f3b31869, msg=null, type=NODE_JOINED, tstamp=1619154380517],
nodeId=f3b31869, evt=NODE_JOINED], lastVer=GridCacheVersion [topVer=0,
order=1619154379141, nodeOrder=0], super=GridCacheMessage [msgId=1,
depInfo=null, lastAffChangedTopVer=AffinityTopologyVersion [topVer=-1,
minorTopVer=0], err=null, skipPrepare=false][2021-04-23
13:06:20,562][ERROR][exchange-worker-#129%I2%][TcpCommunicationSpi] Failed to
send message to remote node [node=TcpDiscoveryNode
[id=7469805f-1097-4e49-a0d9-3474a6a792bb,
consistentId=0:0:0:0:0:0:0:1%lo,127.0.0.1,172.17.0.1,192.168.1.105,192.168.49.1:47500,
addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 192.168.1.105,
192.168.49.1], sockAddrs=HashSet [/172.17.0.1:47500, /192.168.49.1:47500,
/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500, /192.168.1.105:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1619154380497, loc=false,
ver=2.11.0#20210422-sha1:bec58b00, isClient=false], msg=GridIoMessage [plc=2,
topic=TOPIC_CACHE, topicOrd=8, ordered=false, timeout=0, skipOnTimeout=false,
msg=GridDhtPartitionsSingleMessage [parts=HashMap
{-2100569601=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=-1, minorTopVer=0], updateSeq=1, size=0]}, partCntrs=HashMap
{-2100569601=CachePartitionPartialCountersMap {}}, partsSizes=null,
partHistCntrs=null, err=null, client=false, exchangeStartTime=1619154380524,
finishMsg=null, super=GridDhtPartitionsAbstractMessage
[exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=f3b31869-bea3-406c-a8a3-6fe5a502d8c4,
consistentId=0:0:0:0:0:0:0:1%lo,127.0.0.1,172.17.0.1,192.168.1.105,192.168.49.1:47501,
addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 192.168.1.105,
192.168.49.1], sockAddrs=HashSet [/192.168.49.1:47501,
/0:0:0:0:0:0:0:1%lo:47501, /127.0.0.1:47501, /192.168.1.105:47501,
/172.17.0.1:47501], discPort=47501, order=2, intOrder=2,
lastExchangeTime=1619154380527, loc=true, ver=2.11.0#20210422-sha1:bec58b00,
isClient=false], topVer=2, msgTemplate=null,
span=org.apache.ignite.internal.processors.tracing.NoopSpan@4773b242,
nodeId8=f3b31869, msg=null, type
[jira] [Commented] (IGNITE-14633) Calcite engine. Sort out the types/[hugeint|map|null|struct|unsigned] directories
[ https://issues.apache.org/jira/browse/IGNITE-14633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329448#comment-17329448 ] Konstantin Orlov commented on IGNITE-14633: --- [~tledkov-gridgain], [~zstan], folks, do a review please > Calcite engine. Sort out the types/[hugeint|map|null|struct|unsigned] > directories > - > > Key: IGNITE-14633 > URL: https://issues.apache.org/jira/browse/IGNITE-14633 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Subj. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14633) Calcite engine. Sort out the types/[hugeint|map|null|struct|unsigned] directories
Konstantin Orlov created IGNITE-14633: - Summary: Calcite engine. Sort out the types/[hugeint|map|null|struct|unsigned] directories Key: IGNITE-14633 URL: https://issues.apache.org/jira/browse/IGNITE-14633 Project: Ignite Issue Type: Task Components: sql Reporter: Konstantin Orlov Assignee: Konstantin Orlov Subj. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14632) Calcite engine. Support for unsigned types
Konstantin Orlov created IGNITE-14632:
-
Summary: Calcite engine. Support for unsigned types
Key: IGNITE-14632
URL: https://issues.apache.org/jira/browse/IGNITE-14632
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Konstantin Orlov
Subj.
Affected tests:
{{src/test/sql/types/unsigned/test_unsigned_arithmetic.test_ignored}}
{{src/test/sql/types/unsigned/test_unsigned_auto_cast.test_ignored}}
{{src/test/sql/types/unsigned/test_unsigned_conversion.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14595) ExpiryPolicy support to python thin client
[ https://issues.apache.org/jira/browse/IGNITE-14595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329360#comment-17329360 ] Igor Sapego commented on IGNITE-14595: -- [~ivandasch] I'm OK with the patch > ExpiryPolicy support to python thin client > -- > > Key: IGNITE-14595 > URL: https://issues.apache.org/jira/browse/IGNITE-14595 > Project: Ignite > Issue Type: New Feature > Components: python, thin client >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Labels: python, thin > Fix For: python-0.5.0 > > Time Spent: 40m > Remaining Estimate: 0h > > It's of a crucial importance to add support for expiration policy in python > client. > This is on of the most used feature of any cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14620) GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky
[ https://issues.apache.org/jira/browse/IGNITE-14620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329357#comment-17329357 ] Pavel Tupitsyn commented on IGNITE-14620: - Merged to master: 255a30c0a9e95a0d444ce6a72d634e0963bc5097 > GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky > --- > > Key: IGNITE-14620 > URL: https://issues.apache.org/jira/browse/IGNITE-14620 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.11 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > GridCacheAsyncOperationsLimitSelfTest#testAsyncOps became flaky because of > changes from IGNITE-12033 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14628) [ignite website] Add to downloads page links to pyignite release
[ https://issues.apache.org/jira/browse/IGNITE-14628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-14628: - Description: Since pyignite-0.4.0 is released, it will be great to change a little bit the download page. In new section (Apache IGNITE python thin client) 1. Add download links to [source package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] and [gpg signature| https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) 3. Add link to docs on [readthedocs.io|https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0/] 4. Add link to [release notes|https://ignite.apache.org/releases/pyignite/0.4.0/release_notes.html] Links to source packages should be changed after selecting mirror. was: Since pyignite-0.4.0 is released, it will be great to change a little bit the download page. In new section (Apache IGNITE python thin client) 1. Add download links to [source package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] and [gpg signature| https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) 3. Add link to docs on [readthedocs.io|https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0/] Links to source packages should be changed after selecting mirror. > [ignite website] Add to downloads page links to pyignite release > > > Key: IGNITE-14628 > URL: https://issues.apache.org/jira/browse/IGNITE-14628 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Ivan Daschinsky >Assignee: Mauricio Stekl >Priority: Major > > Since pyignite-0.4.0 is released, it will be great to change a little bit the > download page. > In new section (Apache IGNITE python thin client) > 1. Add download links to [source > package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], > [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] > and [gpg signature| > https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] > 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) > 3. Add link to docs on > [readthedocs.io|https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0/] > 4. Add link to [release > notes|https://ignite.apache.org/releases/pyignite/0.4.0/release_notes.html] > > Links to source packages should be changed after selecting mirror. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14631) Move SSL certificates generation to python code
Nikolay Izhikov created IGNITE-14631: Summary: Move SSL certificates generation to python code Key: IGNITE-14631 URL: https://issues.apache.org/jira/browse/IGNITE-14631 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov For now, it's impossible to change the way of generation of SSL certificates for Ignite forks. Also, certificates are generating on every ducktape run which is useless. Generations should be invoked only if SSL enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14628) [ignite website] Add to downloads page links to pyignite release
[ https://issues.apache.org/jira/browse/IGNITE-14628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-14628: - Description: Since pyignite-0.4.0 is released, it will be great to change a little bit the download page. In new section (Apache IGNITE python thin client) 1. Add download links to [source package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] and [gpg signature| https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) 3. Add link to docs on [readthedocs.io|https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0/] Links to source packages should be changed after selecting mirror. was: Since pyignite-0.4.0 is released, it will be great to change a little bit the download page. In new section (Apache IGNITE python thin client) 1. Add download links to [source package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] and [gpg signature| https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) Links to source packages should be changed after selecting mirror. > [ignite website] Add to downloads page links to pyignite release > > > Key: IGNITE-14628 > URL: https://issues.apache.org/jira/browse/IGNITE-14628 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Ivan Daschinsky >Assignee: Mauricio Stekl >Priority: Major > > Since pyignite-0.4.0 is released, it will be great to change a little bit the > download page. > In new section (Apache IGNITE python thin client) > 1. Add download links to [source > package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], > [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] > and [gpg signature| > https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] > 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) > 3. Add link to docs on > [readthedocs.io|https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0/] > > Links to source packages should be changed after selecting mirror. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14630) Fix excess versions declaration in POMs
Peter Ivanov created IGNITE-14630: - Summary: Fix excess versions declaration in POMs Key: IGNITE-14630 URL: https://issues.apache.org/jira/browse/IGNITE-14630 Project: Ignite Issue Type: Bug Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 3.0.0-alpha2 https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_SanityChecks_Maven/5978039 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14239) Raft based implementation of atomic protocol
[ https://issues.apache.org/jira/browse/IGNITE-14239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-14239: Assignee: Vyacheslav Koptilin > Raft based implementation of atomic protocol > > > Key: IGNITE-14239 > URL: https://issues.apache.org/jira/browse/IGNITE-14239 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: iep-72, ignite-3 > > Implement a new atomic protocol based on raft client api [1] > [1] IGNITE-14149 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14239) Raft based implementation of atomic protocol
[ https://issues.apache.org/jira/browse/IGNITE-14239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-14239: Assignee: Vladislav Pyatkov (was: Vyacheslav Koptilin) > Raft based implementation of atomic protocol > > > Key: IGNITE-14239 > URL: https://issues.apache.org/jira/browse/IGNITE-14239 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Vladislav Pyatkov >Priority: Major > Labels: iep-72, ignite-3 > > Implement a new atomic protocol based on raft client api [1] > [1] IGNITE-14149 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14238) Creating and destroying tables
[ https://issues.apache.org/jira/browse/IGNITE-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-14238: Assignee: Vladislav Pyatkov (was: Vyacheslav Koptilin) > Creating and destroying tables > -- > > Key: IGNITE-14238 > URL: https://issues.apache.org/jira/browse/IGNITE-14238 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Vladislav Pyatkov >Priority: Major > Labels: iep-72, ignite-3 > > Need to implement a new cluster-wide procedure that will be responsible for > creating and destroying caches. > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14238) Creating and destroying tables
[ https://issues.apache.org/jira/browse/IGNITE-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-14238: Assignee: Vyacheslav Koptilin (was: Vladislav Pyatkov) > Creating and destroying tables > -- > > Key: IGNITE-14238 > URL: https://issues.apache.org/jira/browse/IGNITE-14238 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: iep-72, ignite-3 > > Need to implement a new cluster-wide procedure that will be responsible for > creating and destroying caches. > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14238) Creating and destroying tables
[ https://issues.apache.org/jira/browse/IGNITE-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14238: - Summary: Creating and destroying tables (was: Creating and destroying caches) > Creating and destroying tables > -- > > Key: IGNITE-14238 > URL: https://issues.apache.org/jira/browse/IGNITE-14238 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Vladislav Pyatkov >Priority: Major > Labels: iep-72, ignite-3 > > Need to implement a new cluster-wide procedure that will be responsible for > creating and destroying caches. > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14238) Creating and destroying caches
[ https://issues.apache.org/jira/browse/IGNITE-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-14238: Assignee: Vladislav Pyatkov (was: Vyacheslav Koptilin) > Creating and destroying caches > -- > > Key: IGNITE-14238 > URL: https://issues.apache.org/jira/browse/IGNITE-14238 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Vladislav Pyatkov >Priority: Major > Labels: iep-72, ignite-3 > > Need to implement a new cluster-wide procedure that will be responsible for > creating and destroying caches. > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14238) Creating and destroying caches
[ https://issues.apache.org/jira/browse/IGNITE-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-14238: Assignee: Vyacheslav Koptilin > Creating and destroying caches > -- > > Key: IGNITE-14238 > URL: https://issues.apache.org/jira/browse/IGNITE-14238 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: iep-72, ignite-3 > > Need to implement a new cluster-wide procedure that will be responsible for > creating and destroying caches. > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14628) [ignite website] Add to downloads page links to pyignite release
[ https://issues.apache.org/jira/browse/IGNITE-14628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-14628: - Description: Since pyignite-0.4.0 is released, it will be great to change a little bit the download page. In new section (Apache IGNITE python thin client) 1. Add download links to [source package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] and [gpg signature| https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) Links to source packages should be changed after selecting mirror. was: Since pyignite-0.4.0 is released, it will be great to change a little bit the download page. In new section (Apache IGNITE python thin client) 1. Add download links to [source package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] and [gpg signature| https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0] Links to source packages should be changed after selecting mirror. > [ignite website] Add to downloads page links to pyignite release > > > Key: IGNITE-14628 > URL: https://issues.apache.org/jira/browse/IGNITE-14628 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Ivan Daschinsky >Assignee: Mauricio Stekl >Priority: Major > > Since pyignite-0.4.0 is released, it will be great to change a little bit the > download page. > In new section (Apache IGNITE python thin client) > 1. Add download links to [source > package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], > [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] > and [gpg signature| > https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] > 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0]) > > Links to source packages should be changed after selecting mirror. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14629) Update ducktests documentation about forks run (form releases or sources)
[
https://issues.apache.org/jira/browse/IGNITE-14629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-14629:
--
Description:
The following sections should be updated
{noformat}
# Custom Ignites (forks) testing
## Run all tests
TBD
## Run tests from the external source/repository
TBD
{noformat}
> Update ducktests documentation about forks run (form releases or sources)
> -
>
> Key: IGNITE-14629
> URL: https://issues.apache.org/jira/browse/IGNITE-14629
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
>
> The following sections should be updated
> {noformat}
> # Custom Ignites (forks) testing
> ## Run all tests
> TBD
> ## Run tests from the external source/repository
> TBD
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14629) Update ducktests documentation about forks run (form releases or sources)
Anton Vinogradov created IGNITE-14629: - Summary: Update ducktests documentation about forks run (form releases or sources) Key: IGNITE-14629 URL: https://issues.apache.org/jira/browse/IGNITE-14629 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14628) [ignite website] Add to downloads page links to pyignite release
[ https://issues.apache.org/jira/browse/IGNITE-14628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-14628: - Summary: [ignite website] Add to downloads page links to pyignite release (was: Add to downloads page on ignite website links to pyignite release) > [ignite website] Add to downloads page links to pyignite release > > > Key: IGNITE-14628 > URL: https://issues.apache.org/jira/browse/IGNITE-14628 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Ivan Daschinsky >Assignee: Mauricio Stekl >Priority: Major > > Since pyignite-0.4.0 is released, it will be great to change a little bit the > download page. > In new section (Apache IGNITE python thin client) > 1. Add download links to [source > package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], > [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] > and [gpg signature| > https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] > 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0] > > Links to source packages should be changed after selecting mirror. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14628) Add to downloads page on ignite website links to pyignite release
Ivan Daschinsky created IGNITE-14628: Summary: Add to downloads page on ignite website links to pyignite release Key: IGNITE-14628 URL: https://issues.apache.org/jira/browse/IGNITE-14628 Project: Ignite Issue Type: Task Components: website Reporter: Ivan Daschinsky Assignee: Mauricio Stekl Since pyignite-0.4.0 is released, it will be great to change a little bit the download page. In new section (Apache IGNITE python thin client) 1. Add download links to [source package|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip], [hashsum|https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.sha512] and [gpg signature| https://archive.apache.org/dist/ignite/pyignite/0.4.0/pyignite-0.4.0.zip.asc] 2. Add link (install via [pip|https://pypi.org/project/pyignite/0.4.0] Links to source packages should be changed after selecting mirror. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-6324) Transactional cache data partially available after crash and further recovery.
[
https://issues.apache.org/jira/browse/IGNITE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329177#comment-17329177
]
Ignite TC Bot commented on IGNITE-6324:
---
{panel:title=Branch: [pull/8987/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8987/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: Basic Tests*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5977660&buildTypeId=IgniteTests24Java8_RunBasicTests]
> Transactional cache data partially available after crash and further recovery.
> --
>
> Key: IGNITE-6324
> URL: https://issues.apache.org/jira/browse/IGNITE-6324
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.10
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Attachments: InterruptCommitedThreadTest.java
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> If InterruptedException raise in client code during pds store operations we
> can obtain inconsistent cache after restart.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14545) Calcite engine. Unicode literal not supported
[
https://issues.apache.org/jira/browse/IGNITE-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329176#comment-17329176
]
Aleksey Plekhanov commented on IGNITE-14545:
{quote}it's not true. We need to override only those functions sensible to the
size of the character, like length, substring, strpos
{quote}
All mentioned above functions are sensitive to the size of the character.
Currently, with H2 (which uses {{v.getString().length()}}) we have the same
issue, so I think it's ok to have default Calcite implemented string function
and provide some new functions in the future to deal with 32-bit characters (by
separate low-priority ticket).
> Calcite engine. Unicode literal not supported
> -
>
> Key: IGNITE-14545
> URL: https://issues.apache.org/jira/browse/IGNITE-14545
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unicode literal not supported.
> e.g. {{SELECT }}
> Tests:
> {{aggregate/aggregates/test_aggr_string.test}}
> {{types/string/test_unicode.test_ignored}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14626) [Ignite Website] Update for events schedule & usecases
[ https://issues.apache.org/jira/browse/IGNITE-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14626. - Resolution: Done Added Use Cases and updated list of events. > [Ignite Website] Update for events schedule & usecases > -- > > Key: IGNITE-14626 > URL: https://issues.apache.org/jira/browse/IGNITE-14626 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl], please update the site: > > 1) [https://ignite.apache.org/use-cases/provenusecases.html] > Please add hereBanco do Brasil [https://youtu.be/g1FcrOPXWyg] (after ING Bank) > description: Banco do Brasil is developing in-house the omnichannel Horus > platform. They implemented a complex event processing (CEP) ecosystem that is > based on Apache Ignite, JBoss Drools, and other components. The team also > built microservices and interface applications, both event-driven. > Please delete Vrbo > 2)Please update the events schedule: [https://ignite.apache.org/events.html] > How to Use Spark With Apache Ignite for Big Data Processing > Webinar, Andrey Alexandrov > April 28, 2021 > In this webinar, you learn when to use Ignite, and, using real-world > examples, you learn how to configure Spark-Ignite integration. In addition, > Andrey will tell about optimization techniques and best practices. > Learn more > https://www.gridgain.com/resources/webinars/how-use-spark-apache-ignite-big-data-processing > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14627) Ignite fails before able to activate cluster
Adam Wiedel created IGNITE-14627: Summary: Ignite fails before able to activate cluster Key: IGNITE-14627 URL: https://issues.apache.org/jira/browse/IGNITE-14627 Project: Ignite Issue Type: Bug Environment: I'm running in a CentOS Docker image using Ignite 2.8. The only change in my configuration was adding the data storage configuration. http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd";> Reporter: Adam Wiedel I'm starting my nodes within Docker containers that I have created using the "ignite.sh" script that is deployed within the image. Recently, I turned on native persistence for my default data region configuration, and now the node fails to start with this exception: _Caused by: java.lang.NullPointerException_ _at org.apache.ignite.internal.processors.cache.GridCacheUtils.affinityNode(GridCacheUtils.java:1374)_ _at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$CachePredicate.dataNode(GridDiscoveryManager.java:3205)_ _at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.cacheAffinityNode(GridDiscoveryManager.java:1894)_ _at org.apache.ignite.internal.processors.cache.ValidationOnNodeJoinUtils.validate(ValidationOnNodeJoinUtils.java:346)_ _at org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1201)_ _at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheInRecoveryMode(GridCacheProcessor.java:2291)_ _at org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1700(GridCacheProcessor.java:202)_ _at org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.afterBinaryMemoryRestore(GridCacheProcessor.java:5387)_ _at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreBinaryMemory(GridCacheDatabaseSharedManager.java:1075)_ _at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:2068)_ _at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1254)_ It seems like I should be able to start the node and have time to activate the cluster before it fails. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13691) Calcite Integration. Support of EXCEPT operator
[ https://issues.apache.org/jira/browse/IGNITE-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329144#comment-17329144 ] Aleksey Plekhanov commented on IGNITE-13691: [~korlov], thanks for the review! Merged to sql-calcite. > Calcite Integration. Support of EXCEPT operator > --- > > Key: IGNITE-13691 > URL: https://issues.apache.org/jira/browse/IGNITE-13691 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Aleksey Plekhanov >Priority: Critical > Time Spent: 4h 40m > Remaining Estimate: 0h > > As of now new Calcite based SQL engine doesn't support opearator EXCEPT. We > need to implement it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14626) [Ignite Website] Update for events schedule & usecases
[ https://issues.apache.org/jira/browse/IGNITE-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14626: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule & usecases > -- > > Key: IGNITE-14626 > URL: https://issues.apache.org/jira/browse/IGNITE-14626 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl], please update the site: > > 1) [https://ignite.apache.org/use-cases/provenusecases.html] > Please add hereBanco do Brasil [https://youtu.be/g1FcrOPXWyg] (after ING Bank) > description: Banco do Brasil is developing in-house the omnichannel Horus > platform. They implemented a complex event processing (CEP) ecosystem that is > based on Apache Ignite, JBoss Drools, and other components. The team also > built microservices and interface applications, both event-driven. > Please delete Vrbo > 2)Please update the events schedule: [https://ignite.apache.org/events.html] > How to Use Spark With Apache Ignite for Big Data Processing > Webinar, Andrey Alexandrov > April 28, 2021 > In this webinar, you learn when to use Ignite, and, using real-world > examples, you learn how to configure Spark-Ignite integration. In addition, > Andrey will tell about optimization techniques and best practices. > Learn more > https://www.gridgain.com/resources/webinars/how-use-spark-apache-ignite-big-data-processing > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14625) Make DurableBackgroundTask return future
Kirill Tkalenko created IGNITE-14625: Summary: Make DurableBackgroundTask return future Key: IGNITE-14625 URL: https://issues.apache.org/jira/browse/IGNITE-14625 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 2.11 While trying to implement rebuilding indexes on *DurableBackgroundTask*, I encountered several problems: * For each task, a new thread is created, which can be critical for rebuilding indexes, since there can be many caches and this can create many threads; * Tasks can be completed close to the end of a checkpoint, and data may not reach this checkpoint. Therefore, I propose to slightly rework the *DurableBackgroundTask*. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14626) [Ignite Website] Update for events schedule & usecases
Kseniya Romanova created IGNITE-14626: - Summary: [Ignite Website] Update for events schedule & usecases Key: IGNITE-14626 URL: https://issues.apache.org/jira/browse/IGNITE-14626 Project: Ignite Issue Type: Task Components: website Reporter: Kseniya Romanova [~mstekl], please update the site: 1) [https://ignite.apache.org/use-cases/provenusecases.html] Please add hereBanco do Brasil [https://youtu.be/g1FcrOPXWyg] (after ING Bank) description: Banco do Brasil is developing in-house the omnichannel Horus platform. They implemented a complex event processing (CEP) ecosystem that is based on Apache Ignite, JBoss Drools, and other components. The team also built microservices and interface applications, both event-driven. Please delete Vrbo 2)Please update the events schedule: [https://ignite.apache.org/events.html] How to Use Spark With Apache Ignite for Big Data Processing Webinar, Andrey Alexandrov April 28, 2021 In this webinar, you learn when to use Ignite, and, using real-world examples, you learn how to configure Spark-Ignite integration. In addition, Andrey will tell about optimization techniques and best practices. Learn more https://www.gridgain.com/resources/webinars/how-use-spark-apache-ignite-big-data-processing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13691) Calcite Integration. Support of EXCEPT operator
[ https://issues.apache.org/jira/browse/IGNITE-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329121#comment-17329121 ] Konstantin Orlov commented on IGNITE-13691: --- [~alex_pl], LGTM! > Calcite Integration. Support of EXCEPT operator > --- > > Key: IGNITE-13691 > URL: https://issues.apache.org/jira/browse/IGNITE-13691 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Aleksey Plekhanov >Priority: Critical > Time Spent: 4h 40m > Remaining Estimate: 0h > > As of now new Calcite based SQL engine doesn't support opearator EXCEPT. We > need to implement it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14624) WalSegmentSyncer stops in an incorrect way
Vyacheslav Koptilin created IGNITE-14624:
Summary: WalSegmentSyncer stops in an incorrect way
Key: IGNITE-14624
URL: https://issues.apache.org/jira/browse/IGNITE-14624
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin
{{WalSegmentSyncer#shutdown}} uses {{U.join(GridWorker, IgniteLogger)}} method
which delegates to {{GridWorker#join()}}
{code:java|title=GridWorker.java}
public void join() throws InterruptedException {
...
if ((runner == null && isCancelled) || finished)
return;
synchronized (mux) {
while (!finished)
mux.wait();
}
}
{code}
On the other hand, {{GridWorker#run()}} nullifies the {{runner}} field *after*
the worker notifies all threads that work is finished:
{code:java|title=GridWorker.java}
@Override public final void run() {
// Runner thread must be recorded first as other operations
// may depend on it being present.
runner = Thread.currentThread();
try {
...
body();
}
catch (Throwable e) {
...
}
finally {
synchronized (mux) {
finished = true;
mux.notifyAll();
}
...
// Need to set runner to null, to make sure that
// further operations on this runnable won't
// affect the thread which could have been recycled
// by thread pool.
runner = null;
}
}
{code}
This can lead to {{AssertionError}} like the following:
{noformat}
java.lang.AssertionError: WalSegmentSyncer is running.
org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl$WalSegmentSyncer.restart(FileHandleManagerImpl.java:646)
org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.resumeLogging(FileHandleManagerImpl.java:235)
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.resumeLogging(FileWriteAheadLogManager.java:705)
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.resumeWalLogging(GridCacheDatabaseSharedManager.java:1707)
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.finishRecovery(GridCacheDatabaseSharedManager.java:757)
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onActivate(GridCacheDatabaseSharedManager.java:637)
org.apache.ignite.internal.processors.cache.GridCacheSharedContext.activate(GridCacheSharedContext.java:296)
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:1322)
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:964)
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3375)
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3194)
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14545) Calcite engine. Unicode literal not supported
[
https://issues.apache.org/jira/browse/IGNITE-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329126#comment-17329126
]
Konstantin Orlov commented on IGNITE-14545:
---
# it's true, so may be it would be better to toggle supporting somehow or even
add under different name
# it's not true. We need to override only those functions sensible to the size
of the character, like length, substring, strpos.
In fact, I don't mind to leave current solution. But then we need to create
separate ticket with lower priority to fix the rest issues related to the
strings containing 32-bit characters.
> Calcite engine. Unicode literal not supported
> -
>
> Key: IGNITE-14545
> URL: https://issues.apache.org/jira/browse/IGNITE-14545
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unicode literal not supported.
> e.g. {{SELECT }}
> Tests:
> {{aggregate/aggregates/test_aggr_string.test}}
> {{types/string/test_unicode.test_ignored}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14623) Calcite. Sort out test scripts at: sql/aggregate/aggregates/*
Taras Ledkov created IGNITE-14623:
-
Summary: Calcite. Sort out test scripts at:
sql/aggregate/aggregates/*
Key: IGNITE-14623
URL: https://issues.apache.org/jira/browse/IGNITE-14623
Project: Ignite
Issue Type: Task
Reporter: Taras Ledkov
Assignee: Taras Ledkov
Calcite. Sort out test scripts at: {{sql/aggregate/aggregates/*}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14573) Calcite. Fix composite objects comparator
[
https://issues.apache.org/jira/browse/IGNITE-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14573:
--
Summary: Calcite. Fix composite objects comparator (was: Calcite. Fix
compare composite objects)
> Calcite. Fix composite objects comparator
> -
>
> Key: IGNITE-14573
> URL: https://issues.apache.org/jira/browse/IGNITE-14573
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As a result, insert with further read operations will fail.
> For example:
> {code:java}
> CREATE TABLE IF NOT EXISTS test (id INTEGER, a INTEGER);
> INSERT INTO test VALUES (1, 1), (2, 2), (3, 3), (4, NULL);"
> UPDATE test SET a=CASE WHEN id=1 THEN 7 ELSE NULL END WHERE id <= 2";
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14624) WalSegmentSyncer stops in an incorrect way
[
https://issues.apache.org/jira/browse/IGNITE-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14624:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> WalSegmentSyncer stops in an incorrect way
> --
>
> Key: IGNITE-14624
> URL: https://issues.apache.org/jira/browse/IGNITE-14624
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
>
> {{WalSegmentSyncer#shutdown}} uses {{U.join(GridWorker, IgniteLogger)}}
> method which delegates to {{GridWorker#join()}}
> {code:java|title=GridWorker.java}
> public void join() throws InterruptedException {
> ...
> if ((runner == null && isCancelled) || finished)
> return;
> synchronized (mux) {
> while (!finished)
> mux.wait();
> }
> }
> {code}
> On the other hand, {{GridWorker#run()}} nullifies the {{runner}} field
> *after* the worker notifies all threads that work is finished:
> {code:java|title=GridWorker.java}
> @Override public final void run() {
> // Runner thread must be recorded first as other operations
> // may depend on it being present.
> runner = Thread.currentThread();
> try {
> ...
> body();
> }
> catch (Throwable e) {
> ...
> }
> finally {
> synchronized (mux) {
> finished = true;
> mux.notifyAll();
> }
> ...
> // Need to set runner to null, to make sure that
> // further operations on this runnable won't
> // affect the thread which could have been recycled
> // by thread pool.
> runner = null;
> }
> }
> {code}
> This can lead to {{AssertionError}} like the following:
> {noformat}
> java.lang.AssertionError: WalSegmentSyncer is running.
>
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl$WalSegmentSyncer.restart(FileHandleManagerImpl.java:646)
>
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.resumeLogging(FileHandleManagerImpl.java:235)
>
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.resumeLogging(FileWriteAheadLogManager.java:705)
>
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.resumeWalLogging(GridCacheDatabaseSharedManager.java:1707)
>
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.finishRecovery(GridCacheDatabaseSharedManager.java:757)
>
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onActivate(GridCacheDatabaseSharedManager.java:637)
>
> org.apache.ignite.internal.processors.cache.GridCacheSharedContext.activate(GridCacheSharedContext.java:296)
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:1322)
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:964)
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3375)
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3194)
>
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14573) fix compare composite objects
[
https://issues.apache.org/jira/browse/IGNITE-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14573:
--
Summary: fix compare composite objects (was: DML operations failure.)
> fix compare composite objects
> -
>
> Key: IGNITE-14573
> URL: https://issues.apache.org/jira/browse/IGNITE-14573
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As a result, insert with further read operations will fail.
> For example:
> {code:java}
> CREATE TABLE IF NOT EXISTS test (id INTEGER, a INTEGER);
> INSERT INTO test VALUES (1, 1), (2, 2), (3, 3), (4, NULL);"
> UPDATE test SET a=CASE WHEN id=1 THEN 7 ELSE NULL END WHERE id <= 2";
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14573) Calcite. Fix compare composite objects
[
https://issues.apache.org/jira/browse/IGNITE-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14573:
--
Summary: Calcite. Fix compare composite objects (was: fix compare
composite objects)
> Calcite. Fix compare composite objects
> --
>
> Key: IGNITE-14573
> URL: https://issues.apache.org/jira/browse/IGNITE-14573
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As a result, insert with further read operations will fail.
> For example:
> {code:java}
> CREATE TABLE IF NOT EXISTS test (id INTEGER, a INTEGER);
> INSERT INTO test VALUES (1, 1), (2, 2), (3, 3), (4, NULL);"
> UPDATE test SET a=CASE WHEN id=1 THEN 7 ELSE NULL END WHERE id <= 2";
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14545) Calcite engine. Unicode literal not supported
[
https://issues.apache.org/jira/browse/IGNITE-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328580#comment-17328580
]
Aleksey Plekhanov commented on IGNITE-14545:
# It will work much slower them standard functions for all cases (including
cases where there are no 32-bit chars in the string)
# In this case, we should write our own implementation for all string
functions in Calcite (including used SqlLibrary dialects). There are plenty of
such functions and their aliases (char_length, character_length, substring,
lpad, rpad, locate, strpos, left, right, etc) and there is a chance to miss
something, or chance that some new string function will be added to calcite.
> Calcite engine. Unicode literal not supported
> -
>
> Key: IGNITE-14545
> URL: https://issues.apache.org/jira/browse/IGNITE-14545
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unicode literal not supported.
> e.g. {{SELECT }}
> Tests:
> {{aggregate/aggregates/test_aggr_string.test}}
> {{types/string/test_unicode.test_ignored}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-6324) Transactional cache data partially available after crash and further recovery.
[ https://issues.apache.org/jira/browse/IGNITE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328727#comment-17328727 ] Stanilovsky Evgeny commented on IGNITE-6324: [~sergey-chugunov] thanks for review, i fix all your comments. > Transactional cache data partially available after crash and further recovery. > -- > > Key: IGNITE-6324 > URL: https://issues.apache.org/jira/browse/IGNITE-6324 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.10 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Critical > Attachments: InterruptCommitedThreadTest.java > > Time Spent: 40m > Remaining Estimate: 0h > > If InterruptedException raise in client code during pds store operations we > can obtain inconsistent cache after restart. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14569) Create data structures system view
[ https://issues.apache.org/jira/browse/IGNITE-14569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kazakov updated IGNITE-14569: -- Description: It will be good to have an api to list all created data structures: latches, atomics and so on. So it could be a system view. There is system views for caches, for nodes, for continuous queries. It needs a system view (or views) for data structures. was:It will be good to have an api to list all created data structures: latches, atomics and so on. So it could be a system view. > Create data structures system view > -- > > Key: IGNITE-14569 > URL: https://issues.apache.org/jira/browse/IGNITE-14569 > Project: Ignite > Issue Type: Improvement > Components: data structures >Affects Versions: 2.10 >Reporter: Ilya Kazakov >Priority: Minor > Labels: newbie > > It will be good to have an api to list all created data structures: latches, > atomics and so on. So it could be a system view. > There is system views for caches, for nodes, for continuous queries. It needs > a system view (or views) for data structures. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14595) ExpiryPolicy support to python thin client
[ https://issues.apache.org/jira/browse/IGNITE-14595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328154#comment-17328154 ] Ivan Daschinsky commented on IGNITE-14595: -- [~isapego] Could you please review my patch? > ExpiryPolicy support to python thin client > -- > > Key: IGNITE-14595 > URL: https://issues.apache.org/jira/browse/IGNITE-14595 > Project: Ignite > Issue Type: New Feature > Components: python, thin client >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Labels: python, thin > Fix For: python-0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > It's of a crucial importance to add support for expiration policy in python > client. > This is on of the most used feature of any cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14595) ExpiryPolicy support to python thin client
[ https://issues.apache.org/jira/browse/IGNITE-14595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-14595: - Fix Version/s: python-0.5.0 > ExpiryPolicy support to python thin client > -- > > Key: IGNITE-14595 > URL: https://issues.apache.org/jira/browse/IGNITE-14595 > Project: Ignite > Issue Type: New Feature > Components: python, thin client >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Labels: python, thin > Fix For: python-0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > It's of a crucial importance to add support for expiration policy in python > client. > This is on of the most used feature of any cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14565) Add additional update counter logging for detect causes of AssertionError: LWM after HWM
[ https://issues.apache.org/jira/browse/IGNITE-14565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14565: - Ignite Flags: (was: Release Notes Required) > Add additional update counter logging for detect causes of AssertionError: > LWM after HWM > > > Key: IGNITE-14565 > URL: https://issues.apache.org/jira/browse/IGNITE-14565 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14620) GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky
[ https://issues.apache.org/jira/browse/IGNITE-14620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327399#comment-17327399 ] Igor Sapego commented on IGNITE-14620: -- [~ptupitsyn] looks good. > GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky > --- > > Key: IGNITE-14620 > URL: https://issues.apache.org/jira/browse/IGNITE-14620 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.11 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > GridCacheAsyncOperationsLimitSelfTest#testAsyncOps became flaky because of > changes from IGNITE-12033 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14620) GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky
[
https://issues.apache.org/jira/browse/IGNITE-14620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14620:
Comment: was deleted
(was: {panel:title=Branch: [pull/9031/head] Base: [master] : Possible Blockers
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5976225]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5976168]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore1 -
Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryCommunicationFailureTest.testCommunicationFailureResolve_KillCoordinator_5
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5976212]]
* IgniteBinaryCacheQueryTestSuite:
DynamicIndexServerCoordinatorBasicSelfTest.testDropNoIndexPartitionedAtomicNear
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
DynamicIndexServerCoordinatorBasicSelfTest.testCreateIndexWithParallelismPartitionedTransactional
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5976207]]
* dll:
PlatformCacheTest.TestExpiryPolicyRemovesValuesFromPlatformCache(ServerLocal) -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5976200]]
* IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverIncompletedPartition1 - Test
has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotCheckWithIndexesTest.testClusterSnapshotCheckWithNodeFilter
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9031/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5976233&buildTypeId=IgniteTests24Java8_RunAll])
> GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky
> ---
>
> Key: IGNITE-14620
> URL: https://issues.apache.org/jira/browse/IGNITE-14620
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.11
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> GridCacheAsyncOperationsLimitSelfTest#testAsyncOps became flaky because of
> changes from IGNITE-12033
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14620) GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky
[
https://issues.apache.org/jira/browse/IGNITE-14620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327364#comment-17327364
]
Ignite TC Bot commented on IGNITE-14620:
{panel:title=Branch: [pull/9031/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9031/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5976233&buildTypeId=IgniteTests24Java8_RunAll]
> GridCacheAsyncOperationsLimitSelfTest#testAsyncOps is flaky
> ---
>
> Key: IGNITE-14620
> URL: https://issues.apache.org/jira/browse/IGNITE-14620
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.11
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> GridCacheAsyncOperationsLimitSelfTest#testAsyncOps became flaky because of
> changes from IGNITE-12033
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14545) Calcite engine. Unicode literal not supported
[
https://issues.apache.org/jira/browse/IGNITE-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327264#comment-17327264
]
Konstantin Orlov commented on IGNITE-14545:
---
There is relatively easy way to support 32-bit characters too. We could provide
{{SqlOperatorTables.chain}} with our custom table first. And for string related
function we have to deal with code points, not chars. Here is how we could
derive a proper string length with regards to 32-chars: {{str.codePointCount(0,
str.length())}}. And here is snippets for substring:
{{str.substring(str.offsetByCodePoints(0, from), str.offsetByCodePoints(0, from
+ len))}}. But I don't 100% sure about this approach.
> Calcite engine. Unicode literal not supported
> -
>
> Key: IGNITE-14545
> URL: https://issues.apache.org/jira/browse/IGNITE-14545
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unicode literal not supported.
> e.g. {{SELECT }}
> Tests:
> {{aggregate/aggregates/test_aggr_string.test}}
> {{types/string/test_unicode.test_ignored}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14618) Increase stop timeout to 60 seconds
[ https://issues.apache.org/jira/browse/IGNITE-14618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327263#comment-17327263 ] Anton Vinogradov commented on IGNITE-14618: --- [~nizhikov], thanks for the review. Merged into ignite-ducktape. > Increase stop timeout to 60 seconds > --- > > Key: IGNITE-14618 > URL: https://issues.apache.org/jira/browse/IGNITE-14618 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Graceful stops may take 10+ seconds, so we should increase the timeout to > have no false-negative results. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14622) Snapshot test simplification
[ https://issues.apache.org/jira/browse/IGNITE-14622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327262#comment-17327262 ] Anton Vinogradov commented on IGNITE-14622: --- [~nizhikov], thanks for the review. Merged into ignite-ducktape. > Snapshot test simplification > > > Key: IGNITE-14622 > URL: https://issues.apache.org/jira/browse/IGNITE-14622 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Just get rid of useless stuff %) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14622) Snapshot test simplification
Anton Vinogradov created IGNITE-14622: - Summary: Snapshot test simplification Key: IGNITE-14622 URL: https://issues.apache.org/jira/browse/IGNITE-14622 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Just get rid of useless stuff %) -- This message was sent by Atlassian Jira (v8.3.4#803005)
