[jira] [Commented] (IGNITE-17316) Thin client pluggable affnity function to use partition awareness
[
https://issues.apache.org/jira/browse/IGNITE-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572594#comment-17572594
]
Ignite TC Bot commented on IGNITE-17316:
{panel:title=Branch: [pull/10140/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10140/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6699489]]
* {color:#013220}ClientTestSuite:
ThinClientPartitionAwarenessStableTopologyTest.testPartitionedCustomAffinityCacheWithMapper
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6699499buildTypeId=IgniteTests24Java8_RunAll]
> Thin client pluggable affnity function to use partition awareness
> -
>
> Key: IGNITE-17316
> URL: https://issues.apache.org/jira/browse/IGNITE-17316
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.13
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> We should provie a pluggable affinity for the thin client, thus using the
> partition awareness features become possible on only for
> {{RendezvousAffinityFunction}}.
> Dev-list discussion:
> https://lists.apache.org/thread/7n7zbcgw59voxyr08ct3zx2ss5g8q9wh
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17433) SQL API: When cursor is closed, internal exception is thrown from fetchNextPage
[ https://issues.apache.org/jira/browse/IGNITE-17433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572584#comment-17572584 ] Igor Sapego commented on IGNITE-17433: -- [~ptupitsyn] looks good to me. > SQL API: When cursor is closed, internal exception is thrown from > fetchNextPage > --- > > Key: IGNITE-17433 > URL: https://issues.apache.org/jira/browse/IGNITE-17433 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > * Introduce error code for closed cursor scenario > * Fix client side to throw the same exception too > * Add shared tests to ItSqlAsynchronousApiTest, ItSqlSynchronousApiTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17429) Sql. Extend sql grammar to support CREATE/DROP INDEX statements
[
https://issues.apache.org/jira/browse/IGNITE-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reassigned IGNITE-17429:
-
Assignee: Konstantin Orlov
> Sql. Extend sql grammar to support CREATE/DROP INDEX statements
> ---
>
> Key: IGNITE-17429
> URL: https://issues.apache.org/jira/browse/IGNITE-17429
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
>
> We need to give an ability to manage index via DDL statements.
> As a first step lets support CREATE and DROP statements only. Within this
> ticket we need to extend the sql grammar file as well as provide all
> necessary structures to keep parsed AST.
> The proposed grammar:
> {code:java}
> CREATE INDEX [IF NOT EXISTS] name ON table_name [USING HASH | SORTED ]
> (column_name [ASC | DESC] [NULLS {FIRST | LAST}] [, ...]);
>
> {code}
> {code:java}
> DROP INDEX [IF EXISTS] name;{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17435) Fix Datastreamer documentation.
Vladimir Steshin created IGNITE-17435: - Summary: Fix Datastreamer documentation. Key: IGNITE-17435 URL: https://issues.apache.org/jira/browse/IGNITE-17435 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin The doc should mention something like: Setting the allowOverwrite property to false is best used for initial data load on a cluster with stable topology. When cluster works under load, some actions may cause issues with data consistency. To avoid them: Avoid having the same keys repeating in the data being streamed; Avoid concurrent updates of the cache that is being streamed into; Avoid rebalance on that cache. Avoid snapshotting. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17435) Fix Datastreamer documentation.
[ https://issues.apache.org/jira/browse/IGNITE-17435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-17435: -- Description: The doc should mention something like: Setting the allowOverwrite property to false is best used for initial data load on a cluster with stable topology. When cluster works under load, some actions may cause issues with data consistency. To avoid them: * Avoid having the same keys repeating in the data being streamed; * Avoid concurrent updates of the cache that is being streamed into; * Avoid rebalance on that cache. * Avoid snapshotting. was: The doc should mention something like: _Setting the allowOverwrite property to false is best used for initial data load on a cluster with stable topology. When cluster works under load, some actions may cause issues with data consistency. To avoid them: Avoid having the same keys repeating in the data being streamed; Avoid concurrent updates of the cache that is being streamed into; Avoid rebalance on that cache. Avoid snapshotting._ > Fix Datastreamer documentation. > --- > > Key: IGNITE-17435 > URL: https://issues.apache.org/jira/browse/IGNITE-17435 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > The doc should mention something like: > Setting the allowOverwrite property to false is best used for initial data > load on a cluster with stable topology. When cluster works under load, some > actions may cause issues with data consistency. To avoid them: > * Avoid having the same keys repeating in the data being streamed; > * Avoid concurrent updates of the cache that is being streamed into; > * Avoid rebalance on that cache. > * Avoid snapshotting. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17435) Fix Datastreamer documentation.
[ https://issues.apache.org/jira/browse/IGNITE-17435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-17435: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Fix Datastreamer documentation. > --- > > Key: IGNITE-17435 > URL: https://issues.apache.org/jira/browse/IGNITE-17435 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > The doc should mention something like: > Setting the allowOverwrite property to false is best used for initial data > load on a cluster with stable topology. When cluster works under load, some > actions may cause issues with data consistency. To avoid them: > Avoid having the same keys repeating in the data being streamed; > Avoid concurrent updates of the cache that is being streamed into; > Avoid rebalance on that cache. > Avoid snapshotting. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17435) Fix Datastreamer documentation.
[ https://issues.apache.org/jira/browse/IGNITE-17435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-17435: -- Description: The doc should mention something like: _Setting the allowOverwrite property to false is best used for initial data load on a cluster with stable topology. When cluster works under load, some actions may cause issues with data consistency. To avoid them: Avoid having the same keys repeating in the data being streamed; Avoid concurrent updates of the cache that is being streamed into; Avoid rebalance on that cache. Avoid snapshotting._ was: The doc should mention something like: Setting the allowOverwrite property to false is best used for initial data load on a cluster with stable topology. When cluster works under load, some actions may cause issues with data consistency. To avoid them: Avoid having the same keys repeating in the data being streamed; Avoid concurrent updates of the cache that is being streamed into; Avoid rebalance on that cache. Avoid snapshotting. > Fix Datastreamer documentation. > --- > > Key: IGNITE-17435 > URL: https://issues.apache.org/jira/browse/IGNITE-17435 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > The doc should mention something like: > _Setting the allowOverwrite property to false is best used for initial data > load on a cluster with stable topology. When cluster works under load, some > actions may cause issues with data consistency. To avoid them: > Avoid having the same keys repeating in the data being streamed; > Avoid concurrent updates of the cache that is being streamed into; > Avoid rebalance on that cache. > Avoid snapshotting._ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572473#comment-17572473 ] Anton Kurbanov commented on IGNITE-12852: - [~dpavlov][~nizhikov] Could you please check the patch once again as the branch has been rebased agains fresher master and TC re-run for this ticket? > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17407) The snapshot rate limit does not work correctly when set to values greater than 100 MB per second.
[
https://issues.apache.org/jira/browse/IGNITE-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572468#comment-17572468
]
Amelchev Nikita commented on IGNITE-17407:
--
[~xtern], LGTM.
> The snapshot rate limit does not work correctly when set to values greater
> than 100 MB per second.
>
>
> Key: IGNITE-17407
> URL: https://issues.apache.org/jira/browse/IGNITE-17407
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The snapshot rate limit does not work correctly when set to values greater
> than 100 MB per second.
> Currently, the snapshot transfer rate is limited by the BasicRateLimiter.
> Testing shows that limiter is unable to give more than ~119 millions permits
> per second.
> {code:java}
> long dataSize = U.GB;
> BasicRateLimiter limiter = new BasicRateLimiter(dataSize / 2);
> int blockSize =
> IgniteSnapshotManager.SNAPSHOT_LIMITED_TRANSFER_BLOCK_SIZE_BYTES;
> long start = System.currentTimeMillis();
> for (long i = 0; i < dataSize; i+=blockSize)
> limiter.acquire(blockSize);
> long totalSec =
> TimeUnit.MILLISECONDS.toSeconds(System.currentTimeMillis() - start);
> System.out.println("Speed= " + (dataSize / totalSec));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17423) Investigate performance of insert only YCSB benchmark
[ https://issues.apache.org/jira/browse/IGNITE-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov reassigned IGNITE-17423: --- Assignee: Kirill Gusakov > Investigate performance of insert only YCSB benchmark > - > > Key: IGNITE-17423 > URL: https://issues.apache.org/jira/browse/IGNITE-17423 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > At the moment performance results of insert-only YCSB bencmark from > https://issues.apache.org/jira/browse/IGNITE-17220 and from my local run of > synthetic put/insert handmade benchmarks looks so different - I have near the > 2000k inserts per second vs the 200 in the YCSB benchmark (on the same my > machine). > > Needed further investigations if it can be described by: > * jdbc client penalties (not covered by synthetic put only benchmarks) > * remote machine latency > * -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17434) Extend implicit sql transactions functionality for RO|RW transactions support.
Evgeny Stanilovsky created IGNITE-17434: --- Summary: Extend implicit sql transactions functionality for RO|RW transactions support. Key: IGNITE-17434 URL: https://issues.apache.org/jira/browse/IGNITE-17434 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 3.0.0-alpha5 Reporter: Evgeny Stanilovsky After [1] was implemented, there are some improvements seems still required: # If no explicit tx is specified it`s possible to obtain situation when keys from one bulk enlisted under different tx [2] # Implicit tx (not tx at all but tx meta - timestamp, first enlisted partition and so on ..) need to be replicated into all calcite execution fragments. Thus in [3] seems we need to start implicit tx if no explicit defined and correctly process it in [4] [1] https://issues.apache.org/jira/browse/IGNITE-17328 [2] ModifyNode#flushTuples [3] ExecutionServiceImpl#executeQuery [4] DistributedQueryManager#execute -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-11404) Document CREATE TABLE "parallelism" option
[
https://issues.apache.org/jira/browse/IGNITE-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572369#comment-17572369
]
Pavel Tupitsyn commented on IGNITE-11404:
-
Merged to master: 43a662be8d11918a9c22161b617f28f6d79edc9c
> Document CREATE TABLE "parallelism" option
> --
>
> Key: IGNITE-11404
> URL: https://issues.apache.org/jira/browse/IGNITE-11404
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: YuJue Li
>Priority: Major
> Fix For: 2.14
>
> Attachments:
> 0001-IGNITE-11404-Document-CREATE-TABLE-parallelism-optio.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We added new {{PARALLELISM}} option:
> {code}
> CREATE TABLE ... WITH "parallelism = 4"
> {code}
> This option affect query parallelism which is otherwise set from
> {{CacheConfiguration.queryParallelism}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13612) Ignite Docs: Duplicate document
[ https://issues.apache.org/jira/browse/IGNITE-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572347#comment-17572347 ] Pavel Tupitsyn commented on IGNITE-13612: - Merged to master: f9d76fead1e24970a0186a987a5c5831176ad6d0 > Ignite Docs: Duplicate document > --- > > Key: IGNITE-13612 > URL: https://issues.apache.org/jira/browse/IGNITE-13612 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Minor > Fix For: 2.14 > > Attachments: 0001-IGNITE-13612-Ignite-Docs-Duplicate-document.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > The following two documents are duplicate. Keep one. > [https://ignite.apache.org/docs/latest/data-structures/atomic-sequence] > [https://ignite.apache.org/docs/latest/data-structures/id-generator] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17433) SQL API: When cursor is closed, internal exception is thrown from fetchNextPage
Pavel Tupitsyn created IGNITE-17433: --- Summary: SQL API: When cursor is closed, internal exception is thrown from fetchNextPage Key: IGNITE-17433 URL: https://issues.apache.org/jira/browse/IGNITE-17433 Project: Ignite Issue Type: Bug Components: sql Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn * Introduce error code for closed cursor scenario * Fix client side to throw the same exception too * Add shared tests to ItSqlAsynchronousApiTest, ItSqlSynchronousApiTest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17372) Implement DeltaFilePageStore
[ https://issues.apache.org/jira/browse/IGNITE-17372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572327#comment-17572327 ] Ivan Bessonov commented on IGNITE-17372: Looks good to me. Thank you for the contribution! > Implement DeltaFilePageStore > > > Key: IGNITE-17372 > URL: https://issues.apache.org/jira/browse/IGNITE-17372 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 7h > Remaining Estimate: 0h > > For the new checkpoint, we need to implement *DeltaFilePageStore*. > Will consist of: > * File header, similar to *FilePageStore*, but in addition it will store a > sorted list of pageIdx in which it will be stored; > * Pages themselves, sorted by pageIdx. > Some implementation notes > * Format of the file name for the *DeltaFilePageStore* is > *part-%d-delta-%d.bin* for example *part-1-delta-3.bin* where the first digit > is the partition identifier, and the second is the serial number of the delta > file for this partition; > * Before creating *part-1-delta-3.bin*, a temporary file > *part-1-delta-3.bin.tmp* will be created at the checkpoint first, then > filled, then renamed to *part-1-delta-3.bin*; > * In each delta file we will store the > *org.apache.ignite.internal.storage.pagememory.io.PartitionMetaIo*, which > will be the first page in this file, and it will be special. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17372) Implement DeltaFilePageStore
[ https://issues.apache.org/jira/browse/IGNITE-17372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-17372: --- Release Note: (was: Looks good to me. Thank you for the contribution!) > Implement DeltaFilePageStore > > > Key: IGNITE-17372 > URL: https://issues.apache.org/jira/browse/IGNITE-17372 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 7h > Remaining Estimate: 0h > > For the new checkpoint, we need to implement *DeltaFilePageStore*. > Will consist of: > * File header, similar to *FilePageStore*, but in addition it will store a > sorted list of pageIdx in which it will be stored; > * Pages themselves, sorted by pageIdx. > Some implementation notes > * Format of the file name for the *DeltaFilePageStore* is > *part-%d-delta-%d.bin* for example *part-1-delta-3.bin* where the first digit > is the partition identifier, and the second is the serial number of the delta > file for this partition; > * Before creating *part-1-delta-3.bin*, a temporary file > *part-1-delta-3.bin.tmp* will be created at the checkpoint first, then > filled, then renamed to *part-1-delta-3.bin*; > * In each delta file we will store the > *org.apache.ignite.internal.storage.pagememory.io.PartitionMetaIo*, which > will be the first page in this file, and it will be special. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16657) [Native Persistence 3.0] Implement partitions chunks merger
[ https://issues.apache.org/jira/browse/IGNITE-16657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16657: - Fix Version/s: 3.0.0-alpha6 > [Native Persistence 3.0] Implement partitions chunks merger > --- > > Key: IGNITE-16657 > URL: https://issues.apache.org/jira/browse/IGNITE-16657 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > Please refer to https://issues.apache.org/jira/browse/IGNITE-15818 for the > description. This issue should include the merge process itself. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-16657) [Native Persistence 3.0] Implement partitions chunks merger
[ https://issues.apache.org/jira/browse/IGNITE-16657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko reassigned IGNITE-16657: Assignee: Kirill Tkalenko > [Native Persistence 3.0] Implement partitions chunks merger > --- > > Key: IGNITE-16657 > URL: https://issues.apache.org/jira/browse/IGNITE-16657 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > > Please refer to https://issues.apache.org/jira/browse/IGNITE-15818 for the > description. This issue should include the merge process itself. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-11404) Document CREATE TABLE "parallelism" option
[
https://issues.apache.org/jira/browse/IGNITE-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572304#comment-17572304
]
Pavel Tupitsyn edited comment on IGNITE-11404 at 7/28/22 8:20 AM:
--
[~liyuj] please see my comment on GitHub.
was (Author: ptupitsyn):
Please see my comment on GitHub
> Document CREATE TABLE "parallelism" option
> --
>
> Key: IGNITE-11404
> URL: https://issues.apache.org/jira/browse/IGNITE-11404
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: YuJue Li
>Priority: Major
> Fix For: 2.14
>
> Attachments:
> 0001-IGNITE-11404-Document-CREATE-TABLE-parallelism-optio.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We added new {{PARALLELISM}} option:
> {code}
> CREATE TABLE ... WITH "parallelism = 4"
> {code}
> This option affect query parallelism which is otherwise set from
> {{CacheConfiguration.queryParallelism}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-11404) Document CREATE TABLE "parallelism" option
[
https://issues.apache.org/jira/browse/IGNITE-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572304#comment-17572304
]
Pavel Tupitsyn commented on IGNITE-11404:
-
Please see my comment on GitHub
> Document CREATE TABLE "parallelism" option
> --
>
> Key: IGNITE-11404
> URL: https://issues.apache.org/jira/browse/IGNITE-11404
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: YuJue Li
>Priority: Major
> Fix For: 2.14
>
> Attachments:
> 0001-IGNITE-11404-Document-CREATE-TABLE-parallelism-optio.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We added new {{PARALLELISM}} option:
> {code}
> CREATE TABLE ... WITH "parallelism = 4"
> {code}
> This option affect query parallelism which is otherwise set from
> {{CacheConfiguration.queryParallelism}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13612) Ignite Docs: Duplicate document
[ https://issues.apache.org/jira/browse/IGNITE-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572302#comment-17572302 ] Pavel Tupitsyn commented on IGNITE-13612: - Please remove the page as well, not just the link. > Ignite Docs: Duplicate document > --- > > Key: IGNITE-13612 > URL: https://issues.apache.org/jira/browse/IGNITE-13612 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Minor > Fix For: 2.14 > > Attachments: 0001-IGNITE-13612-Ignite-Docs-Duplicate-document.patch > > Time Spent: 10m > Remaining Estimate: 0h > > The following two documents are duplicate. Keep one. > [https://ignite.apache.org/docs/latest/data-structures/atomic-sequence] > [https://ignite.apache.org/docs/latest/data-structures/id-generator] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17427) Update netty version up to 4.1.79.Final
[ https://issues.apache.org/jira/browse/IGNITE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572294#comment-17572294 ] Maxim Muzafarov commented on IGNITE-17427: -- Merged to the master branch. [~agidaspov] thank you for the contribution. > Update netty version up to 4.1.79.Final > --- > > Key: IGNITE-17427 > URL: https://issues.apache.org/jira/browse/IGNITE-17427 > Project: Ignite > Issue Type: Task >Reporter: Alexey Gidaspov >Assignee: Alexey Gidaspov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Need to update netty version up to 4.1.79.Final because of > [CVE-2022-24823|https://nvd.nist.gov/vuln/detail/CVE-2022-24823] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17427) Update netty version up to 4.1.79.Final
[ https://issues.apache.org/jira/browse/IGNITE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov resolved IGNITE-17427. -- Resolution: Fixed > Update netty version up to 4.1.79.Final > --- > > Key: IGNITE-17427 > URL: https://issues.apache.org/jira/browse/IGNITE-17427 > Project: Ignite > Issue Type: Task >Reporter: Alexey Gidaspov >Assignee: Alexey Gidaspov >Priority: Minor > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to update netty version up to 4.1.79.Final because of > [CVE-2022-24823|https://nvd.nist.gov/vuln/detail/CVE-2022-24823] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17427) Update netty version up to 4.1.79.Final
[ https://issues.apache.org/jira/browse/IGNITE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17427: - Fix Version/s: 2.14 > Update netty version up to 4.1.79.Final > --- > > Key: IGNITE-17427 > URL: https://issues.apache.org/jira/browse/IGNITE-17427 > Project: Ignite > Issue Type: Task >Reporter: Alexey Gidaspov >Assignee: Alexey Gidaspov >Priority: Minor > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to update netty version up to 4.1.79.Final because of > [CVE-2022-24823|https://nvd.nist.gov/vuln/detail/CVE-2022-24823] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17427) Update netty version up to 4.1.79.Final
[
https://issues.apache.org/jira/browse/IGNITE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572283#comment-17572283
]
Ignite TC Bot commented on IGNITE-17427:
{panel:title=Branch: [pull/10172/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10172/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=6535093buildTypeId=IgniteTests24Java8_RunAll]
> Update netty version up to 4.1.79.Final
> ---
>
> Key: IGNITE-17427
> URL: https://issues.apache.org/jira/browse/IGNITE-17427
> Project: Ignite
> Issue Type: Task
>Reporter: Alexey Gidaspov
>Assignee: Alexey Gidaspov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to update netty version up to 4.1.79.Final because of
> [CVE-2022-24823|https://nvd.nist.gov/vuln/detail/CVE-2022-24823]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17255) Implement ReplicaService
[ https://issues.apache.org/jira/browse/IGNITE-17255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel reassigned IGNITE-17255: -- Assignee: Sergey Uttsel > Implement ReplicaService > > > Key: IGNITE-17255 > URL: https://issues.apache.org/jira/browse/IGNITE-17255 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3, transaction3_rw > > For general context please check IGNITE-17252 > Within given ticket it's required to > * Implement ReplicaService itself. > * Substitute RaftGroupService with ReplicaService from within > InternalTableImpl and others > Please pay attention that according to tx protocol it's valid to fail the > transaction in case of primary replica change - we'll introduce support of > graceful primary replica switch later on. For now, within the scope of RW > transactions it's enough to detect where primary replica is and enlist it to > transaction with corresponding partition in order to reuse for further > in-partition communication. > We should make it very clear, that any replicaService.invoke(nodeId) might > fail with primaryReplicaMiss or replicaUnavailable, it's up to the outer > logic to remap such failed requests. > However it's still required to detect proper primary replica initially and > check whether it's still primary during further queries. Proper lease-based > primary replica stability engine will be introduced within > [IGNITE-17256|https://issues.apache.org/jira/browse/IGNITE-17256] , as a > staring point it's possible to reuse sendWithRetry logic with true readIndex > leader checks, meaning that primary replica is the replica collocated with > the current leader (not the node that is thinking that it's a leader, but a > node that was proved to be a leader based on readIndex logic). > In addition to all points mentioned above we should be aware that lot's of > tests will become flaky because sendWithRetry logic will only be available > with initial primaryReplica detection method and not within common invokes. > Generally speaking I believe that it's a good chance to rework them and thus > make them stable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17331) Investigate of smart transaction exception handling for SQL
[ https://issues.apache.org/jira/browse/IGNITE-17331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-17331: --- Summary: Investigate of smart transaction exception handling for SQL (was: Smart transaction exception handling for SQL) > Investigate of smart transaction exception handling for SQL > --- > > Key: IGNITE-17331 > URL: https://issues.apache.org/jira/browse/IGNITE-17331 > Project: Ignite > Issue Type: Improvement >Reporter: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > > As of now we have just abort transaction and SQL execution in case of any > error. Let's investigate for which cases possible retry execute whole query > or just a fragments behind the scene and don't notify user about a issue. > As result of the task should be banch of tickets with description possible > cases and ways to implement the retries logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
