[jira] [Created] (IGNITE-14636) Calcite engine. Implement STRING_AGG (aka GROUP_CONCAT, LISTAGG) aggregate function
Taras Ledkov created IGNITE-14636:
-
Summary: Calcite engine. Implement STRING_AGG (aka GROUP_CONCAT,
LISTAGG) aggregate function
Key: IGNITE-14636
URL: https://issues.apache.org/jira/browse/IGNITE-14636
Project: Ignite
Issue Type: Task
Components: sql
Reporter: Taras Ledkov
Tests:
{{src/test/sql/aggregate/aggregates/test_aggregate_types.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14543) Calcite engine. COUNT agregate on scalar values fails
[
https://issues.apache.org/jira/browse/IGNITE-14543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14543:
--
Description:
Failed queries:
{{SELECT COUNT(*)}}
{{SELECT COUNT(NULL)}}
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
{{aggregate/aggregates/test_aggregate_types_scalar.test_ignore}}
was:
Failed queries:
{{SELECT COUNT(*)}}
{{SELECT COUNT(NULL)}}
Test:
{{aggregate/aggregates/test_count.test_ignored}}
> Calcite engine. COUNT agregate on scalar values fails
> -
>
> Key: IGNITE-14543
> URL: https://issues.apache.org/jira/browse/IGNITE-14543
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Failed queries:
> {{SELECT COUNT(*)}}
> {{SELECT COUNT(NULL)}}
> Tests:
> {{aggregate/aggregates/test_count.test_ignored}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14424) Cache group re-encryption does not start after cluster secondary activation.
[
https://issues.apache.org/jira/browse/IGNITE-14424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14424:
--
Affects Version/s: 2.10
> Cache group re-encryption does not start after cluster secondary activation.
>
>
> Key: IGNITE-14424
> URL: https://issues.apache.org/jira/browse/IGNITE-14424
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Cache group re-encryption does not start after cluster secondary activation.
> Reproducer
> {code:java}
> @Test
> public void testDeactivation() throws Exception {
> pageScanRate = 2;
> checkpointFreq = 10;
> T2 nodes = startTestGrids(true);
> IgniteEx node0 = nodes.get1();
> IgniteEx node1 = nodes.get2();
> createEncryptedCache(node0, node1, cacheName(), null);
> loadData(100_000);
>
> node0.encryption().changeCacheGroupKey(Collections.singleton(cacheName())).get();
>
> assertTrue(isReencryptionInProgress(Collections.singleton(cacheName(;
> node0.cluster().state(ClusterState.INACTIVE);
>
> assertFalse(isReencryptionInProgress(Collections.singleton(cacheName(;
>
> node0.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);
>
> node1.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);
> node0.cluster().state(ClusterState.ACTIVE);
> checkGroupKey(CU.cacheId(cacheName()), INITIAL_KEY_ID + 1,
> MAX_AWAIT_MILLIS); // failing here
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14636) Calcite engine. Implement STRING_AGG (aka GROUP_CONCAT, LISTAGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14636:
--
Description:
Tests:
{{aggregate/aggregates/test_aggregate_types.test}}
{{aggregate/aggregates/test_aggregate_types_scalar.test}}
was:
Tests:
{{src/test/sql/aggregate/aggregates/test_aggregate_types.test}}
> Calcite engine. Implement STRING_AGG (aka GROUP_CONCAT, LISTAGG) aggregate
> function
> ---
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14636) Calcite engine. Implement STRING_AGG (aka GROUP_CONCAT, LISTAGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14636:
--
Issue Type: Improvement (was: Task)
> Calcite engine. Implement STRING_AGG (aka GROUP_CONCAT, LISTAGG) aggregate
> function
> ---
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14637) Calcite engine. Implement approximate aggregate functions
Taras Ledkov created IGNITE-14637:
-
Summary: Calcite engine. Implement approximate aggregate functions
Key: IGNITE-14637
URL: https://issues.apache.org/jira/browse/IGNITE-14637
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Implements the approximate aggregate functions:
- {{APPROX_COUNT_DISTINCT}}
- {{APPROX_QUANTILES}}
Tests:
{{aggregate/aggregates/test_approx_quantile.test}}
{{aggregate/aggregates/test_approximate_distinct_count.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9386) control.sh --tx can produce confusing results when limit is set to small value
[ https://issues.apache.org/jira/browse/IGNITE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330074#comment-17330074 ] Alexand Polyakov commented on IGNITE-9386: -- relevant for master (2021.04.23) > control.sh --tx can produce confusing results when limit is set to small value > -- > > Key: IGNITE-9386 > URL: https://issues.apache.org/jira/browse/IGNITE-9386 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Alexey Scherbakov >Priority: Major > > This is happening because currently the limit is applied to primary and > backup transactions, which breaks output post-filtering (removal of primary > and backup transactions from output if near is present). > Possible solution: apply limit only to near valid transactions. If some txs > have no near part (broken tx topology), they should be always visible in > output, probably with special "broken" marking. > Best way to achieve this - implement tx paging on client side (using > continuous mapping) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14638) Calcite engine. Support for INTERSECT operator
Aleksey Plekhanov created IGNITE-14638: -- Summary: Calcite engine. Support for INTERSECT operator Key: IGNITE-14638 URL: https://issues.apache.org/jira/browse/IGNITE-14638 Project: Ignite Issue Type: Improvement Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Currently, INTERSECT operator is not supported -- 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=17330089#comment-17330089 ] Ivan Daschinsky commented on IGNITE-14595: -- [~isapego] thanks for review, merged to master > 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: 50m > 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-13840) Rething API of Init*, change* classes
[ https://issues.apache.org/jira/browse/IGNITE-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330124#comment-17330124 ] Ivan Bessonov commented on IGNITE-13840: PR was approved by [~sdanilov] > Rething API of Init*, change* classes > -- > > Key: IGNITE-13840 > URL: https://issues.apache.org/jira/browse/IGNITE-13840 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Right now, API of Init*, change* classes look too heavy and contain a lot of > code boilerplate. It needs to think about how to simplify it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13840) Rething API of Init*, change* classes
[ https://issues.apache.org/jira/browse/IGNITE-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330130#comment-17330130 ] Ivan Bessonov commented on IGNITE-13840: "Maven" suite is broken in main branch: https://issues.apache.org/jira/browse/IGNITE-14630 > Rething API of Init*, change* classes > -- > > Key: IGNITE-13840 > URL: https://issues.apache.org/jira/browse/IGNITE-13840 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Right now, API of Init*, change* classes look too heavy and contain a lot of > code boilerplate. It needs to think about how to simplify it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14639) Calcite engine. Implement ARG_MIN/MAX aggregate functions
Taras Ledkov created IGNITE-14639: - Summary: Calcite engine. Implement ARG_MIN/MAX aggregate functions Key: IGNITE-14639 URL: https://issues.apache.org/jira/browse/IGNITE-14639 Project: Ignite Issue Type: Improvement Components: sql Reporter: Taras Ledkov Implement aggregate functions - ARG_MIN; - ARG_MAX. SQL standard doesn't contain these functions but the most analytics DB implement ones. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14639) Calcite engine. Implement ARG_MIN/MAX aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14639:
--
Description:
Implement aggregate functions
- ARG_MIN;
- ARG_MAX.
SQL standard doesn't contain these functions but the most analytics DB
implement ones.
Test:
{{aggregate/aggregates/test_arg_min_max.test_ignore}}
was:
Implement aggregate functions
- ARG_MIN;
- ARG_MAX.
SQL standard doesn't contain these functions but the most analytics DB
implement ones.
> Calcite engine. Implement ARG_MIN/MAX aggregate functions
> -
>
> Key: IGNITE-14639
> URL: https://issues.apache.org/jira/browse/IGNITE-14639
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Implement aggregate functions
> - ARG_MIN;
> - ARG_MAX.
> SQL standard doesn't contain these functions but the most analytics DB
> implement ones.
> Test:
> {{aggregate/aggregates/test_arg_min_max.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14543) Calcite engine. Agregate functions fail on scalar values
[
https://issues.apache.org/jira/browse/IGNITE-14543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14543:
--
Summary: Calcite engine. Agregate functions fail on scalar values (was:
Calcite engine. COUNT agregate on scalar values fails)
> Calcite engine. Agregate functions fail on scalar values
>
>
> Key: IGNITE-14543
> URL: https://issues.apache.org/jira/browse/IGNITE-14543
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Failed queries:
> {{SELECT COUNT(*)}}
> {{SELECT COUNT(NULL)}}
> Tests:
> {{aggregate/aggregates/test_count.test_ignored}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14543) Calcite engine. Agregate functions fail on scalar values
[
https://issues.apache.org/jira/browse/IGNITE-14543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14543:
--
Description:
Failed queries:
{{SELECT COUNT(*)}}
{{SELECT COUNT(NULL)}}
{{SELECT AVG(NULL)}}
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
{{aggregate/aggregates/test_aggregate_types_scalar.test_ignore}}
{{aggregate/aggregates/test_avg.test}}
was:
Failed queries:
{{SELECT COUNT(*)}}
{{SELECT COUNT(NULL)}}
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
{{aggregate/aggregates/test_aggregate_types_scalar.test_ignore}}
> Calcite engine. Agregate functions fail on scalar values
>
>
> Key: IGNITE-14543
> URL: https://issues.apache.org/jira/browse/IGNITE-14543
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Failed queries:
> {{SELECT COUNT(*)}}
> {{SELECT COUNT(NULL)}}
> {{SELECT AVG(NULL)}}
> Tests:
> {{aggregate/aggregates/test_count.test_ignored}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test_ignore}}
> {{aggregate/aggregates/test_avg.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14544) Calcite engine. Implement DISTINCT aggregates
[
https://issues.apache.org/jira/browse/IGNITE-14544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14544:
--
Description:
Now, DISTINCT aggregates not implemented.
(e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
{{aggregate/aggregates/test_avg.test}}
was:
Now, DISTINCT aggregates not implemented.
(e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
> Calcite engine. Implement DISTINCT aggregates
> -
>
> Key: IGNITE-14544
> URL: https://issues.apache.org/jira/browse/IGNITE-14544
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Now, DISTINCT aggregates not implemented.
> (e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
> Tests:
> {{aggregate/aggregates/test_count.test_ignored}}
> {{aggregate/aggregates/test_avg.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14636) Calcite engine. Implement LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14636:
--
Summary: Calcite engine. Implement LISTAGG (aka GROUP_CONCAT, STRING_AGG)
aggregate function (was: Calcite engine. Implement STRING_AGG (aka
GROUP_CONCAT, LISTAGG) aggregate function)
> Calcite engine. Implement LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate
> function
> ---
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reassigned IGNITE-14542:
-
Assignee: Konstantin Orlov
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Konstantin Orlov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov resolved IGNITE-14542.
---
Resolution: Fixed
Fixed within https://issues.apache.org/jira/browse/IGNITE-14590
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Konstantin Orlov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reopened IGNITE-14542:
---
Assignee: (was: Konstantin Orlov)
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-14542:
--
Comment: was deleted
(was: Fixed within https://issues.apache.org/jira/browse/IGNITE-14590)
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Konstantin Orlov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14640) Calcite engine. Implement bit aggregate functions
Taras Ledkov created IGNITE-14640:
-
Summary: Calcite engine. Implement bit aggregate functions
Key: IGNITE-14640
URL: https://issues.apache.org/jira/browse/IGNITE-14640
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Implement bit aggregate functions:
- BIT_AND
- BIT_OR
- BIT_XOR
Tests:
{{aggregate/aggregates/test_bit_and.test}}
{{aggregate/aggregates/test_bit_or.test}}
{{aggregate/aggregates/test_bit_xor.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14554) Calcite engine. Provide ability to parse huge numeric literals
[
https://issues.apache.org/jira/browse/IGNITE-14554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov resolved IGNITE-14554.
---
Resolution: Fixed
Fixed by https://issues.apache.org/jira/browse/IGNITE-14590
> Calcite engine. Provide ability to parse huge numeric literals
> --
>
> Key: IGNITE-14554
> URL: https://issues.apache.org/jira/browse/IGNITE-14554
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Minor
>
> Currently literals like this {{17014118346046923173168730371588410572}} can't
> pass validation because they overflow range of long values.
> Affected tests:
> {{modules/calcite/src/test/sql/types/decimal/cast_from_decimal.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14636) Calcite engine. Implement LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330224#comment-17330224
]
Konstantin Orlov commented on IGNITE-14636:
---
Some of this functions already implemented in CALCITE-4335. Let's wait till
1.27.0 will be released.
> Calcite engine. Implement LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate
> function
> ---
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14407) In-memory implementation of Vault
[ https://issues.apache.org/jira/browse/IGNITE-14407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev reassigned IGNITE-14407: Assignee: Mirza Aliev > In-memory implementation of Vault > - > > Key: IGNITE-14407 > URL: https://issues.apache.org/jira/browse/IGNITE-14407 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Mirza Aliev >Priority: Major > > It seems that in-memory implementation can be provided in the first place. It > allows unblocking other activities (dev and unit testing) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14561) Fix javadoc in Configuration module.
[
https://issues.apache.org/jira/browse/IGNITE-14561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330302#comment-17330302
]
Aleksandr Polovtcev commented on IGNITE-14561:
--
The patch looks good.
> Fix javadoc in Configuration module.
>
>
> Key: IGNITE-14561
> URL: https://issues.apache.org/jira/browse/IGNITE-14561
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After IGNITE-13751 had been merged, Javadoc suite failed on TC due to lack of
> javadocs.
> Let's fix "warnings" that is related to Configuration and
> Configuration-annotation-processor modules.
> Startpoint is to run javadoc goal for the apache-ignite project:
> {code:java}
> mvn javadoc:javadoc
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13670) Skip writing null-map and varlen table when possible.
[ https://issues.apache.org/jira/browse/IGNITE-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13670: -- Summary: Skip writing null-map and varlen table when possible. (was: Skip writing null-map and varlen table when possible) > Skip writing null-map and varlen table when possible. > - > > Key: IGNITE-13670 > URL: https://issues.apache.org/jira/browse/IGNITE-13670 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3, newbie > > h3. Motivation. > The nullmap is currently always written to the tuple layout for all columns > even if there are no nullable columns described in the schema. > The same is true and can be done for varlen table. > Seems, we can extend this idea to every single tuple and still have the > ability to compare key/value content fast as byte arrays. > Apparently, this will work for rows of same schema version, but we shouldn't > bother about the schema version, > because anyway, old row will be upgraded to the newer version before > comparison according to the live-schema concept. > h3. Description. > Let's skip an empty nullmap and write just a flag instead. > Let's skip an empty varlen table and write just a flag instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14641) Calcite engine. Implement covariance aggregate functions
Taras Ledkov created IGNITE-14641:
-
Summary: Calcite engine. Implement covariance aggregate functions
Key: IGNITE-14641
URL: https://issues.apache.org/jira/browse/IGNITE-14641
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Implement covariance aggregate functions:
- COVAR_POP,
- COVAR_SAMP,
- REGR_COUNT,
- REGR_SXX,
- REGR_SYY
Test:
{{aggregate/aggregates/test_covar.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14636) Calcite engine. Implement LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14636:
--
Description:
Tests:
{{aggregate/aggregates/test_aggregate_types.test}}
{{aggregate/aggregates/test_aggregate_types_scalar.test}}
{{aggregate/aggregates/test_distinct_string_agg.test_ignore}}
was:
Tests:
{{aggregate/aggregates/test_aggregate_types.test}}
{{aggregate/aggregates/test_aggregate_types_scalar.test}}
> Calcite engine. Implement LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate
> function
> ---
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14544) Calcite engine. Implement DISTINCT aggregates
[
https://issues.apache.org/jira/browse/IGNITE-14544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14544:
--
Description:
Now, DISTINCT aggregates not implemented.
(e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
{{aggregate/aggregates/test_avg.test}}
{{aggregate/aggregates/test_distinct_aggr.test}}
{{aggregate/aggregates/test_distinct_string_agg.test}}
was:
Now, DISTINCT aggregates not implemented.
(e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
{{aggregate/aggregates/test_avg.test}}
> Calcite engine. Implement DISTINCT aggregates
> -
>
> Key: IGNITE-14544
> URL: https://issues.apache.org/jira/browse/IGNITE-14544
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Now, DISTINCT aggregates not implemented.
> (e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
> Tests:
> {{aggregate/aggregates/test_count.test_ignored}}
> {{aggregate/aggregates/test_avg.test}}
> {{aggregate/aggregates/test_distinct_aggr.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14544) Calcite engine. Implement DISTINCT aggregates
[
https://issues.apache.org/jira/browse/IGNITE-14544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14544:
--
Description:
Now, DISTINCT aggregates not implemented.
(e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
Tests:
{{aggregate/aggregates/test_count.test}}
{{aggregate/aggregates/test_avg.test}}
{{aggregate/aggregates/test_distinct_aggr.test}}
{{aggregate/aggregates/test_distinct_string_agg.test}}
was:
Now, DISTINCT aggregates not implemented.
(e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
{{aggregate/aggregates/test_avg.test}}
{{aggregate/aggregates/test_distinct_aggr.test}}
{{aggregate/aggregates/test_distinct_string_agg.test}}
> Calcite engine. Implement DISTINCT aggregates
> -
>
> Key: IGNITE-14544
> URL: https://issues.apache.org/jira/browse/IGNITE-14544
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Now, DISTINCT aggregates not implemented.
> (e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
> Tests:
> {{aggregate/aggregates/test_count.test}}
> {{aggregate/aggregates/test_avg.test}}
> {{aggregate/aggregates/test_distinct_aggr.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14544) Calcite engine. Support DISTINCT aggregates
[
https://issues.apache.org/jira/browse/IGNITE-14544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14544:
--
Summary: Calcite engine. Support DISTINCT aggregates (was: Calcite engine.
Implement DISTINCT aggregates)
> Calcite engine. Support DISTINCT aggregates
> ---
>
> Key: IGNITE-14544
> URL: https://issues.apache.org/jira/browse/IGNITE-14544
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Now, DISTINCT aggregates not implemented.
> (e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
> Tests:
> {{aggregate/aggregates/test_count.test}}
> {{aggregate/aggregates/test_avg.test}}
> {{aggregate/aggregates/test_distinct_aggr.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14639) Calcite engine. Support ARG_MIN/MAX aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14639:
--
Summary: Calcite engine. Support ARG_MIN/MAX aggregate functions (was:
Calcite engine. Implement ARG_MIN/MAX aggregate functions)
> Calcite engine. Support ARG_MIN/MAX aggregate functions
> ---
>
> Key: IGNITE-14639
> URL: https://issues.apache.org/jira/browse/IGNITE-14639
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Implement aggregate functions
> - ARG_MIN;
> - ARG_MAX.
> SQL standard doesn't contain these functions but the most analytics DB
> implement ones.
> Test:
> {{aggregate/aggregates/test_arg_min_max.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14637) Calcite engine. Support for approximate aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14637:
--
Summary: Calcite engine. Support for approximate aggregate functions (was:
Calcite engine. Implement approximate aggregate functions)
> Calcite engine. Support for approximate aggregate functions
> ---
>
> Key: IGNITE-14637
> URL: https://issues.apache.org/jira/browse/IGNITE-14637
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Implements the approximate aggregate functions:
> - {{APPROX_COUNT_DISTINCT}}
> - {{APPROX_QUANTILES}}
> Tests:
> {{aggregate/aggregates/test_approx_quantile.test}}
> {{aggregate/aggregates/test_approximate_distinct_count.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14639) Calcite engine. Support for ARG_MIN/MAX aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14639:
--
Summary: Calcite engine. Support for ARG_MIN/MAX aggregate functions (was:
Calcite engine. Support ARG_MIN/MAX aggregate functions)
> Calcite engine. Support for ARG_MIN/MAX aggregate functions
> ---
>
> Key: IGNITE-14639
> URL: https://issues.apache.org/jira/browse/IGNITE-14639
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Implement aggregate functions
> - ARG_MIN;
> - ARG_MAX.
> SQL standard doesn't contain these functions but the most analytics DB
> implement ones.
> Test:
> {{aggregate/aggregates/test_arg_min_max.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14636) Calcite engine. Support for LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14636:
--
Summary: Calcite engine. Support for LISTAGG (aka GROUP_CONCAT, STRING_AGG)
aggregate function (was: Calcite engine. Implement LISTAGG (aka GROUP_CONCAT,
STRING_AGG) aggregate function)
> Calcite engine. Support for LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate
> function
> -
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14640) Calcite engine. Support for bit aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14640:
--
Summary: Calcite engine. Support for bit aggregate functions (was: Calcite
engine. Implement bit aggregate functions)
> Calcite engine. Support for bit aggregate functions
> ---
>
> Key: IGNITE-14640
> URL: https://issues.apache.org/jira/browse/IGNITE-14640
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Implement bit aggregate functions:
> - BIT_AND
> - BIT_OR
> - BIT_XOR
> Tests:
> {{aggregate/aggregates/test_bit_and.test}}
> {{aggregate/aggregates/test_bit_or.test}}
> {{aggregate/aggregates/test_bit_xor.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14641) Calcite engine. Support for covariance aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14641:
--
Summary: Calcite engine. Support for covariance aggregate functions (was:
Calcite engine. Implement covariance aggregate functions)
> Calcite engine. Support for covariance aggregate functions
> --
>
> Key: IGNITE-14641
> URL: https://issues.apache.org/jira/browse/IGNITE-14641
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Implement covariance aggregate functions:
> - COVAR_POP,
> - COVAR_SAMP,
> - REGR_COUNT,
> - REGR_SXX,
> - REGR_SYY
> Test:
> {{aggregate/aggregates/test_covar.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14642) Calcite engine. Support for standard deviation aggregate functions
Taras Ledkov created IGNITE-14642:
-
Summary: Calcite engine. Support for standard deviation aggregate
functions
Key: IGNITE-14642
URL: https://issues.apache.org/jira/browse/IGNITE-14642
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Support for standard deviation aggregate functions:
- STDDEV_POP;
- STDDEV_SAMP.
Tests:
{{aggregate/aggregates/test_empty_aggregate.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14637) Calcite engine. Support for statistics and approximate statistics aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14637:
--
Summary: Calcite engine. Support for statistics and approximate statistics
aggregate functions (was: Calcite engine. Support for approximate aggregate
functions)
> Calcite engine. Support for statistics and approximate statistics aggregate
> functions
> -
>
> Key: IGNITE-14637
> URL: https://issues.apache.org/jira/browse/IGNITE-14637
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Implements the approximate aggregate functions:
> - {{APPROX_COUNT_DISTINCT}}
> - {{APPROX_QUANTILES}}
> Tests:
> {{aggregate/aggregates/test_approx_quantile.test}}
> {{aggregate/aggregates/test_approximate_distinct_count.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14637) Calcite engine. Support for statistics and approximate statistics aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14637:
--
Priority: Minor (was: Major)
> Calcite engine. Support for statistics and approximate statistics aggregate
> functions
> -
>
> Key: IGNITE-14637
> URL: https://issues.apache.org/jira/browse/IGNITE-14637
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Implements the approximate aggregate functions:
> - {{APPROX_COUNT_DISTINCT}}
> - {{APPROX_QUANTILES}}
> Tests:
> {{aggregate/aggregates/test_approx_quantile.test}}
> {{aggregate/aggregates/test_approximate_distinct_count.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14637) Calcite engine. Support for statistics and approximate statistics aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14637:
--
Description:
Implements the approximate aggregate functions:
- {{QUANTILES}}
- {{HISTOGRAM}}
- {{MODE}}
- {{APPROX_COUNT_DISTINCT}}
- {{APPROX_QUANTILES}}
Tests:
{{aggregate/aggregates/test_approx_quantile.test}}
{{aggregate/aggregates/test_approximate_distinct_count.test}}
{{aggregate/aggregates/test_histogram.test}}
{{aggregate/aggregates/test_mode.test}}
{{aggregate/aggregates/test_quantile.test_ignored}}
{{aggregate/aggregates/test_quantile_list.test_ignored}}
was:
Implements the approximate aggregate functions:
- {{APPROX_COUNT_DISTINCT}}
- {{APPROX_QUANTILES}}
Tests:
{{aggregate/aggregates/test_approx_quantile.test}}
{{aggregate/aggregates/test_approximate_distinct_count.test}}
> Calcite engine. Support for statistics and approximate statistics aggregate
> functions
> -
>
> Key: IGNITE-14637
> URL: https://issues.apache.org/jira/browse/IGNITE-14637
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Implements the approximate aggregate functions:
> - {{QUANTILES}}
> - {{HISTOGRAM}}
> - {{MODE}}
> - {{APPROX_COUNT_DISTINCT}}
> - {{APPROX_QUANTILES}}
> Tests:
> {{aggregate/aggregates/test_approx_quantile.test}}
> {{aggregate/aggregates/test_approximate_distinct_count.test}}
> {{aggregate/aggregates/test_histogram.test}}
> {{aggregate/aggregates/test_mode.test}}
> {{aggregate/aggregates/test_quantile.test_ignored}}
> {{aggregate/aggregates/test_quantile_list.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14643) Calcite engine. Support for linear regression aggregate functions
Taras Ledkov created IGNITE-14643:
-
Summary: Calcite engine. Support for linear regression aggregate
functions
Key: IGNITE-14643
URL: https://issues.apache.org/jira/browse/IGNITE-14643
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Support for linear regression aggregate functions:
- REGR_COUNT;
- REGR_SXX;
- REGR_SYY.
Test:
{{aggregate/aggregates/test_regression.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14642) Calcite engine. Support for standard deviation aggregate functions
[
https://issues.apache.org/jira/browse/IGNITE-14642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14642:
--
Description:
Support for standard deviation aggregate functions:
- STDDEV_POP;
- STDDEV_SAMP.
Tests:
{{aggregate/aggregates/test_empty_aggregate.test}}
{{aggregate/aggregates/test_stddev.test}}
was:
Support for standard deviation aggregate functions:
- STDDEV_POP;
- STDDEV_SAMP.
Tests:
{{aggregate/aggregates/test_empty_aggregate.test}}
> Calcite engine. Support for standard deviation aggregate functions
> --
>
> Key: IGNITE-14642
> URL: https://issues.apache.org/jira/browse/IGNITE-14642
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
>
> Support for standard deviation aggregate functions:
> - STDDEV_POP;
> - STDDEV_SAMP.
> Tests:
> {{aggregate/aggregates/test_empty_aggregate.test}}
> {{aggregate/aggregates/test_stddev.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13444) Cluster deactivation could lead to JVM crash.
[
https://issues.apache.org/jira/browse/IGNITE-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Makedonskaya updated IGNITE-13444:
Release Note: Fixed an issue that led to JVM crash during index removal on
a deactivated cluster
> Cluster deactivation could lead to JVM crash.
> -
>
> Key: IGNITE-13444
> URL: https://issues.apache.org/jira/browse/IGNITE-13444
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We could get JVM crash if a cluster has indexes and index deletion task tries
> to run on deactivated grid. We shouldn't start new tasks on a deactivated
> grid. Also, interrupt the execution of current tasks.
> Scenario:
> * Apply patch:
> {code:java}
> Index:
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (date 1587246501828)@@ -30,6 +30,7 @@ import
> org.apache.ignite.internal.processors.query.h2.database.H2Tree; import
> org.apache.ignite.internal.util.typedef.internal.CU; import
> org.apache.ignite.internal.util.typedef.internal.S;+import
> org.apache.ignite.internal.util.typedef.internal.U; import static
> org.apache.ignite.internal.metric.IoStatisticsType.SORTED_INDEX; @@ -155,6
> +156,8 @@ BPlusTree tree = trees0.get(i);
> try \{+ U.sleep(1L);+
> tree.destroy(null, true); } catch
> (IgniteCheckedException e) \{Index:
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (date 1587247548691)@@ -30,6 +30,7 @@ import
> org.apache.ignite.failure.StopNodeFailureHandler; import
> org.apache.ignite.internal.IgniteEx; import
> org.apache.ignite.internal.processors.cache.index.AbstractIndexingCommonTest;+import
> org.apache.ignite.internal.util.typedef.internal.U; import
> org.apache.ignite.testframework.GridTestUtils; import
> org.h2.result.LazyResult; import org.h2.result.ResultInterface;@@ -78,6 +79,8
> @@ @Override protected void afterTest() throws Exception {
> stopAllGrids(); + U.sleep(2L);+ super.afterTest(); }
> {code}
> * Start {{LocalQueryLazyTest#testDeactivateWithOpenCursor()}} test without
> {{-ea}} VM option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14424) Cache group re-encryption does not start after cluster secondary activation.
[
https://issues.apache.org/jira/browse/IGNITE-14424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330419#comment-17330419
]
Ignite TC Bot commented on IGNITE-14424:
{panel:title=Branch: [pull/9036/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9036/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5979226]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
CacheGroupReencryptionTest.testDeactivation - PASSED{color}
{color:#8b}Basic 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5977470]]
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
CacheGroupReencryptionTest.testDeactivation - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5978843&buildTypeId=IgniteTests24Java8_RunAll]
> Cache group re-encryption does not start after cluster secondary activation.
>
>
> Key: IGNITE-14424
> URL: https://issues.apache.org/jira/browse/IGNITE-14424
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Cache group re-encryption does not start after cluster secondary activation.
> Reproducer
> {code:java}
> @Test
> public void testDeactivation() throws Exception {
> pageScanRate = 2;
> checkpointFreq = 10;
> T2 nodes = startTestGrids(true);
> IgniteEx node0 = nodes.get1();
> IgniteEx node1 = nodes.get2();
> createEncryptedCache(node0, node1, cacheName(), null);
> loadData(100_000);
>
> node0.encryption().changeCacheGroupKey(Collections.singleton(cacheName())).get();
>
> assertTrue(isReencryptionInProgress(Collections.singleton(cacheName(;
> node0.cluster().state(ClusterState.INACTIVE);
>
> assertFalse(isReencryptionInProgress(Collections.singleton(cacheName(;
>
> node0.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);
>
> node1.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);
> node0.cluster().state(ClusterState.ACTIVE);
> checkGroupKey(CU.cacheId(cacheName()), INITIAL_KEY_ID + 1,
> MAX_AWAIT_MILLIS); // failing here
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14044) Cache with node filter is not destroyed properly on the filtered node.
[
https://issues.apache.org/jira/browse/IGNITE-14044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330452#comment-17330452
]
Ignite TC Bot commented on IGNITE-14044:
{panel:title=Branch: [pull/8849/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8849/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5979103]]
* {color:#013220}IgnitePdsTestSuite:
IgnitePdsDestroyCacheTest.testDestroyCacheWithNodeFilter - PASSED{color}
{color:#8b}Thin client: Python{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5979131]]
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy_async(expiry_policy3)
- PASSED{color}
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy_async(expiry_policy1)
- PASSED{color}
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy_async(expiry_policy2)
- PASSED{color}
* {color:#013220}tests.common.test_expiry_policy.test_expiry_policy_async -
PASSED{color}
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy(None)
- PASSED{color}
* {color:#013220}tests.common.test_expiry_policy.test_expiry_policy -
PASSED{color}
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy(expiry_policy3)
- PASSED{color}
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy_async(None)
- PASSED{color}
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy(expiry_policy1)
- PASSED{color}
*
{color:#013220}tests.common.test_expiry_policy.test_create_cache_with_expiry_policy(expiry_policy2)
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5979134&buildTypeId=IgniteTests24Java8_RunAll]
> Cache with node filter is not destroyed properly on the filtered node.
> --
>
> Key: IGNITE-14044
> URL: https://issues.apache.org/jira/browse/IGNITE-14044
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Steps to reproduce the problem:
> # Start 2 nodes
> # Create a cache with node filter (filter second node)
> # Destroy cache
> # Restart nodes
> Expected: cache was destroyed on both nodes.
> Actual: cache was destroyed only on one node, the second node cannot join
> the cluster with the following error:
> {noformat}
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining node has
> caches with data which are not presented on cluster, it could mean that they
> were already destroyed, to add the node to cluster - remove directories with
> the caches[cache1]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2052)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:1197)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:472)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2154)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:278)
> ... 23 more
> {noformat}
> Reproducer
> {code:java}
> public class IgnitePdsDestroyCacheWithNodeFilterTest extends
> GridCommonAbstractTest {
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> return super.getConfiguration(igniteInstanceName)
> .setConsistentId(igniteInstanceName)
> .setDataStorageConfiguration(new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(new DataRegionConfiguration()
> .setPersistenceEnabled(true)));
> }
> @Test
> public void testDestroyCacheWithNodeFilter() throws Exception {
> cleanPersistenceDir();
> Ignite ignite = startGrids(2);
> ignite.cluster().state(ClusterState.ACTIVE);
> UUID nodeId0 = ignite.cluster().localNode().id();
> CacheConfiguration cfg1 = new
> CacheConfiguration<>("cache1")
> .setCacheMode(CacheMode.REPLICATED)
> .setNodeFilter(n -> nodeId0.equals(n.id()));
> IgniteCache cache1 = ignite.createCache(cfg1);
> cache1.destroy();
> forceCheckpoint();
> awaitPartitionMapExchange();
> stopAllGrids();
> ignite = startGrids(2); // failing here
> ignite.clus
[jira] [Updated] (IGNITE-14044) Cache with node filter is not destroyed properly on the filtered node.
[
https://issues.apache.org/jira/browse/IGNITE-14044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14044:
--
Affects Version/s: 2.10
> Cache with node filter is not destroyed properly on the filtered node.
> --
>
> Key: IGNITE-14044
> URL: https://issues.apache.org/jira/browse/IGNITE-14044
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Steps to reproduce the problem:
> # Start 2 nodes
> # Create a cache with node filter (filter second node)
> # Destroy cache
> # Restart nodes
> Expected: cache was destroyed on both nodes.
> Actual: cache was destroyed only on one node, the second node cannot join
> the cluster with the following error:
> {noformat}
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining node has
> caches with data which are not presented on cluster, it could mean that they
> were already destroyed, to add the node to cluster - remove directories with
> the caches[cache1]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2052)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:1197)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:472)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2154)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:278)
> ... 23 more
> {noformat}
> Reproducer
> {code:java}
> public class IgnitePdsDestroyCacheWithNodeFilterTest extends
> GridCommonAbstractTest {
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> return super.getConfiguration(igniteInstanceName)
> .setConsistentId(igniteInstanceName)
> .setDataStorageConfiguration(new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(new DataRegionConfiguration()
> .setPersistenceEnabled(true)));
> }
> @Test
> public void testDestroyCacheWithNodeFilter() throws Exception {
> cleanPersistenceDir();
> Ignite ignite = startGrids(2);
> ignite.cluster().state(ClusterState.ACTIVE);
> UUID nodeId0 = ignite.cluster().localNode().id();
> CacheConfiguration cfg1 = new
> CacheConfiguration<>("cache1")
> .setCacheMode(CacheMode.REPLICATED)
> .setNodeFilter(n -> nodeId0.equals(n.id()));
> IgniteCache cache1 = ignite.createCache(cfg1);
> cache1.destroy();
> forceCheckpoint();
> awaitPartitionMapExchange();
> stopAllGrids();
> ignite = startGrids(2); // failing here
> ignite.cluster().state(ClusterState.ACTIVE);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14044) Cache with node filter is not destroyed properly on the filtered node.
[
https://issues.apache.org/jira/browse/IGNITE-14044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330456#comment-17330456
]
Pavel Pereslegin commented on IGNITE-14044:
---
[~slava.koptilin],
could you take a look at this patch?
> Cache with node filter is not destroyed properly on the filtered node.
> --
>
> Key: IGNITE-14044
> URL: https://issues.apache.org/jira/browse/IGNITE-14044
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Steps to reproduce the problem:
> # Start 2 nodes
> # Create a cache with node filter (filter second node)
> # Destroy cache
> # Restart nodes
> Expected: cache was destroyed on both nodes.
> Actual: cache was destroyed only on one node, the second node cannot join
> the cluster with the following error:
> {noformat}
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining node has
> caches with data which are not presented on cluster, it could mean that they
> were already destroyed, to add the node to cluster - remove directories with
> the caches[cache1]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2052)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:1197)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:472)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2154)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:278)
> ... 23 more
> {noformat}
> Reproducer
> {code:java}
> public class IgnitePdsDestroyCacheWithNodeFilterTest extends
> GridCommonAbstractTest {
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> return super.getConfiguration(igniteInstanceName)
> .setConsistentId(igniteInstanceName)
> .setDataStorageConfiguration(new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(new DataRegionConfiguration()
> .setPersistenceEnabled(true)));
> }
> @Test
> public void testDestroyCacheWithNodeFilter() throws Exception {
> cleanPersistenceDir();
> Ignite ignite = startGrids(2);
> ignite.cluster().state(ClusterState.ACTIVE);
> UUID nodeId0 = ignite.cluster().localNode().id();
> CacheConfiguration cfg1 = new
> CacheConfiguration<>("cache1")
> .setCacheMode(CacheMode.REPLICATED)
> .setNodeFilter(n -> nodeId0.equals(n.id()));
> IgniteCache cache1 = ignite.createCache(cfg1);
> cache1.destroy();
> forceCheckpoint();
> awaitPartitionMapExchange();
> stopAllGrids();
> ignite = startGrids(2); // failing here
> ignite.cluster().state(ClusterState.ACTIVE);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14424) Cache group re-encryption does not start after cluster secondary activation.
[
https://issues.apache.org/jira/browse/IGNITE-14424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330463#comment-17330463
]
Pavel Pereslegin commented on IGNITE-14424:
---
[~NSAmelchev],
could you take a look at this patch?
> Cache group re-encryption does not start after cluster secondary activation.
>
>
> Key: IGNITE-14424
> URL: https://issues.apache.org/jira/browse/IGNITE-14424
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Cache group re-encryption does not start after cluster secondary activation.
> Reproducer
> {code:java}
> @Test
> public void testDeactivation() throws Exception {
> pageScanRate = 2;
> checkpointFreq = 10;
> T2 nodes = startTestGrids(true);
> IgniteEx node0 = nodes.get1();
> IgniteEx node1 = nodes.get2();
> createEncryptedCache(node0, node1, cacheName(), null);
> loadData(100_000);
>
> node0.encryption().changeCacheGroupKey(Collections.singleton(cacheName())).get();
>
> assertTrue(isReencryptionInProgress(Collections.singleton(cacheName(;
> node0.cluster().state(ClusterState.INACTIVE);
>
> assertFalse(isReencryptionInProgress(Collections.singleton(cacheName(;
>
> node0.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);
>
> node1.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);
> node0.cluster().state(ClusterState.ACTIVE);
> checkGroupKey(CU.cacheId(cacheName()), INITIAL_KEY_ID + 1,
> MAX_AWAIT_MILLIS); // failing here
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13181) Ignite support for spark-3.0.0
[ https://issues.apache.org/jira/browse/IGNITE-13181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330802#comment-17330802 ] Dmitry Pavlov commented on IGNITE-13181: I suggest to reach community by writting a email to d...@ignite.apache.org > Ignite support for spark-3.0.0 > -- > > Key: IGNITE-13181 > URL: https://issues.apache.org/jira/browse/IGNITE-13181 > Project: Ignite > Issue Type: New Feature > Components: spark >Affects Versions: 2.8.1 >Reporter: Shenson Joseph >Priority: Blocker > > feature to support apache spark-3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14542:
--
Description:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test_ignored}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow_ignored}}
was:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test_ignored}}
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test_ignored}}
> {{aggregate/aggregates/test_string_agg_many_groups.test_slow_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14636) Calcite engine. Support for LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14636:
--
Description:
Tests:
{{aggregate/aggregates/test_aggregate_types.test}}
{{aggregate/aggregates/test_aggregate_types_scalar.test}}
{{aggregate/aggregates/test_distinct_string_agg.test_ignore}}
{{aggregate/aggregates/test_string_agg.test_ignore}}
{{aggregate/aggregates/test_string_agg_big.test_ignore}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow_ignored}}
was:
Tests:
{{aggregate/aggregates/test_aggregate_types.test}}
{{aggregate/aggregates/test_aggregate_types_scalar.test}}
{{aggregate/aggregates/test_distinct_string_agg.test_ignore}}
> Calcite engine. Support for LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate
> function
> -
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test_ignore}}
> {{aggregate/aggregates/test_string_agg.test_ignore}}
> {{aggregate/aggregates/test_string_agg_big.test_ignore}}
> {{aggregate/aggregates/test_string_agg_many_groups.test_slow_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14542:
--
Description:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
was:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test_ignored}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow_ignored}}
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test}}
> {{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14542:
--
Description:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
{{aggregate/aggregates/test_sum.test}}
was:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test}}
> {{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
> {{aggregate/aggregates/test_sum.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
[
https://issues.apache.org/jira/browse/IGNITE-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14542:
--
Description:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
{{aggregate/aggregates/test_sum.test}}
was:
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test}}
{{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
{{aggregate/aggregates/test_sum.test}}
> Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
> ---
>
> Key: IGNITE-14542
> URL: https://issues.apache.org/jira/browse/IGNITE-14542
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> A lot of cases require dynamic range data source.
> Tests:
> {{aggregate/aggregates/test_perfect_ht.test}}
> {{aggregate/aggregates/test_string_agg_many_groups.test_slow}}
> {{aggregate/aggregates/test_sum.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14644) .NET: Log a suggestion about COMPlus_EnableAlternateStackCheck
Pavel Tupitsyn created IGNITE-14644: --- Summary: .NET: Log a suggestion about COMPlus_EnableAlternateStackCheck Key: IGNITE-14644 URL: https://issues.apache.org/jira/browse/IGNITE-14644 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.11 See https://ignite.apache.org/docs/latest/net-specific/net-troubleshooting#stack-smashing-detected-dotnet-terminated: On Linux, Java overwrites SIGSEGV handler installed by .NET, so NullReferenceException causes a scary "Stack smashing detected" error, which can be fixed by setting COMPlus_EnableAlternateStackCheck environment variable. Write a suggestion to the log if all of the following is true: * OS is Linux (or macOS? Check this) * Runtime version is 3.0 or later * COMPlus_EnableAlternateStackCheck is not set -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14645) Support polymorphic configuration nodes.
Ivan Bessonov created IGNITE-14645:
--
Summary: Support polymorphic configuration nodes.
Key: IGNITE-14645
URL: https://issues.apache.org/jira/browse/IGNITE-14645
Project: Ignite
Issue Type: Sub-task
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov
NOTE: description might not be finished.
h3. Problem
Currently configuration schema structure is very restricted and doesn't allow
any variations in it. This approach comes with a set of problems.
# How do you properly configure {{IpFinder}}? For each type of finder you only
need a few properties.
# How do you configure SQL indexes? Pretty much the same problem.
h3. Interface
For the solution we need to expand abilities of configuration schemas. I
propose the following option:
{code:java}
// Configuration schema that contains polymorphic field.
@Config
class TableConfigurationSchema {
@NamedConfigValue
public IndexConfigurationSchema indexes;
}
// Base class for polymorphic value. Explicitly has all subclasses
// in its description to simplify incremental code generation.
@PolymorphicConfig(impl = {
HashIndexConfigurationSchema.class,
TreeIndexConfigurationSchema.class,
})
class IndexConfigurationSchema {
// This annotation shows that current field defines implementation.
// Specific values are present in implementations declarations.
@Id
@Immutable
@Value
public String type;
}
// One of implementations for index. Id value is defined in annotation.
@PolymorphicInstance(id = "hash")
public static class HashIndexConfigurationSchema extends
IndexConfigurationSchema {
@Immutable
@Value
public String column;
}
// Other implementation for index.
@PolymorphicInstance(id = "tree")
public static class TreeIndexConfigurationSchema extends
IndexConfigurationSchema {
@Immutable
@Value
public String[] columns;
}
{code}
h3. Generated API
We need to tweak API a little bit. I'd love to see as few changes as possible,
so my vision is something like this:
{code:java}
TableConfiguration tableCfg = ...;
tableCfg.indexes().create("hashIndexName", index ->
// Id sets up automatically by the call.
index.asHashIndex().changeColumn("columnName")
).get();
tableCfg.indexes().update("hashIndexName", index ->
// Any cast is allowed to do in change request.
// But this update will fail during processing.
index.asTreeIndex().changeColumns(new String[] {"a", "b"})
);
IndexConfiguration indexCfg = tableCfg.indexes().get("hashIndexName");
// This must be an instance of "HashIndexConfiguration".
HashIndexConfiguration hashCfg = (HashIndexConfiguration)indexCfg;
// This must be instance of HashIndexView,
IndexView indexView = indexCfg.value();
// Maybe this is redundant, I don't know.
assert indexView.isHashIndex();
// Returns the same object with a safe cast.
// Maybe this is redundant as well and regular cast would be enough.
HashIndexView hashView = indexView.asHashIndex();{code}
h3. Implementation Notes
TODO
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14645) Support polymorphic configuration nodes.
[
https://issues.apache.org/jira/browse/IGNITE-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-14645:
---
Description:
NOTE: description might not be finished.
h3. Problem
Currently configuration schema structure is very restricted and doesn't allow
any variations in it. This approach comes with a set of problems.
# How do you properly configure {{IpFinder}}? For each type of finder you only
need a few properties.
# How do you configure SQL indexes? Pretty much the same problem.
h3. Interface
For the solution we need to expand abilities of configuration schemas. I
propose the following option:
{code:java}
// Configuration schema that contains polymorphic field.
@Config
class TableConfigurationSchema {
@NamedConfigValue
public IndexConfigurationSchema indexes;
}
// Base class for polymorphic value. Explicitly has all subclasses
// in its description to simplify incremental code generation.
@PolymorphicConfig(impl = {
HashIndexConfigurationSchema.class,
TreeIndexConfigurationSchema.class,
})
class IndexConfigurationSchema {
// This annotation shows that current field defines implementation.
// Specific values are present in implementations declarations.
@Id
@Immutable
@Value
public String type;
}
// One of implementations for index. Id value is defined in annotation.
@PolymorphicInstance(id = "hash")
public static class HashIndexConfigurationSchema extends
IndexConfigurationSchema {
@Immutable
@Value
public String column;
}
// Other implementation for index.
@PolymorphicInstance(id = "tree")
public static class TreeIndexConfigurationSchema extends
IndexConfigurationSchema {
@Immutable
@Value
public String[] columns;
}
{code}
h3. Generated API
We need to tweak API a little bit. I'd love to see as few changes as possible,
so my vision is something like this:
{code:java}
TableConfiguration tableCfg = ...;
tableCfg.indexes().create("hashIndexName", index ->
// Id sets up automatically by the call.
index.asHashIndex().changeColumn("columnName")
).get();
tableCfg.indexes().update("hashIndexName", index ->
// Any cast is allowed to do in change request.
// But this update will fail during processing.
index.asTreeIndex().changeColumns("a", "b")
);
IndexConfiguration indexCfg = tableCfg.indexes().get("hashIndexName");
// This must be an instance of "HashIndexConfiguration".
HashIndexConfiguration hashCfg = (HashIndexConfiguration)indexCfg;
// This must be instance of HashIndexView,
IndexView indexView = indexCfg.value();
// Maybe this is redundant, I don't know.
assert indexView.isHashIndex();
// Returns the same object with a safe cast.
// Maybe this is redundant as well and regular cast would be enough.
HashIndexView hashView = indexView.asHashIndex();{code}
h3. Implementation Notes
TODO
was:
NOTE: description might not be finished.
h3. Problem
Currently configuration schema structure is very restricted and doesn't allow
any variations in it. This approach comes with a set of problems.
# How do you properly configure {{IpFinder}}? For each type of finder you only
need a few properties.
# How do you configure SQL indexes? Pretty much the same problem.
h3. Interface
For the solution we need to expand abilities of configuration schemas. I
propose the following option:
{code:java}
// Configuration schema that contains polymorphic field.
@Config
class TableConfigurationSchema {
@NamedConfigValue
public IndexConfigurationSchema indexes;
}
// Base class for polymorphic value. Explicitly has all subclasses
// in its description to simplify incremental code generation.
@PolymorphicConfig(impl = {
HashIndexConfigurationSchema.class,
TreeIndexConfigurationSchema.class,
})
class IndexConfigurationSchema {
// This annotation shows that current field defines implementation.
// Specific values are present in implementations declarations.
@Id
@Immutable
@Value
public String type;
}
// One of implementations for index. Id value is defined in annotation.
@PolymorphicInstance(id = "hash")
public static class HashIndexConfigurationSchema extends
IndexConfigurationSchema {
@Immutable
@Value
public String column;
}
// Other implementation for index.
@PolymorphicInstance(id = "tree")
public static class TreeIndexConfigurationSchema extends
IndexConfigurationSchema {
@Immutable
@Value
public String[] columns;
}
{code}
h3. Generated API
We need to tweak API a little bit. I'd love to see as few changes as possible,
so my vision is something like this:
{code:java}
TableConfiguration tableCfg = ...;
tableCfg.indexes().create("hashIndexName", index ->
// Id sets up automatically by the call.
index.asHashIndex().changeColumn("columnName")
).get();
tableCfg.indexes().update("hashIndexName", index ->
// Any cast is allowed to do in change request.
[jira] [Commented] (IGNITE-14623) Calcite. Sort out test scripts at: sql/aggregate/aggregates/*
[
https://issues.apache.org/jira/browse/IGNITE-14623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330899#comment-17330899
]
Stanilovsky Evgeny commented on IGNITE-14623:
-
1 minor comment, overall looks good
> 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
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Calcite. Sort out test scripts at: {{sql/aggregate/aggregates/*}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14646) Support asynchronous table creation
Vladislav Pyatkov created IGNITE-14646:
--
Summary: Support asynchronous table creation
Key: IGNITE-14646
URL: https://issues.apache.org/jira/browse/IGNITE-14646
Project: Ignite
Issue Type: Improvement
Reporter: Vladislav Pyatkov
Today we are using a dirty hack for waiting to create a table in
{{TableManagerImpl#createTable}} method:
{code}
Table tbl = null;
while (tbl == null) {
Thread.sleep(50);
tbl = table(name);
}
{code}
It needs to implement this through a future without a waiting loop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14453) Issue with persistence when using JDK15
[
https://issues.apache.org/jira/browse/IGNITE-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Anderson updated IGNITE-14453:
Attachment: ignite-jdk16.sh
> Issue with persistence when using JDK15
> ---
>
> Key: IGNITE-14453
> URL: https://issues.apache.org/jira/browse/IGNITE-14453
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.10
> Environment: Apache Ignite with openJDK-15 (java version 15.0.1)
>Reporter: Emmanuel Wiesenfeld
>Priority: Major
> Attachments: ignite-jdk16.sh
>
>
> When using the following code:
>
> {code:java}
> IgniteConfiguration cfg = new IgniteConfiguration();
> //data storage configuration
> DataStorageConfiguration storageCfg = new DataStorageConfiguration();
> storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
> cfg.setDataStorageConfiguration(storageCfg);
> Ignite ignite = Ignition.start(cfg);{code}
>
> I get this upon startup:
> {code:java}
> SEVERE: Got exception while starting (will rollback startup routine).
> java.lang.NullPointerException: Cannot invoke
> "java.lang.reflect.Method.invoke(Object, Object[])" because
> "org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.mappingOffset"
> is null
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:449)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:418)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.flush(FileHandleManagerImpl.java:269)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.flush(FileWriteAheadLogManager.java:934)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.tailPointer(GridCacheDatabaseSharedManager.java:1968)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1908)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1299)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2112)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:663)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:328){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14453) Issue with persistence when using JDK15
[
https://issues.apache.org/jira/browse/IGNITE-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331156#comment-17331156
]
Aaron Anderson commented on IGNITE-14453:
-
I dug into this and it appears that as of JDK 15 some memory methods were moved
from java.nio.MappedByteBuffer to
[java.nio.MappedMemoryUtils|https://github.com/openjdk/jdk/blob/master/src/java.base/share/classes/java/nio/MappedMemoryUtils.java]
I started to make a pull request but then I had issues with running some of
the tests and I wasn't sure the best way to handle dual JDK version support.
Attached is a patch of some changes that I made to the Ignite 2.10.0 tag
complied with JDK 11. With this update in place I am able to start up Ignite
and store entries in a cache back by persistence.
> Issue with persistence when using JDK15
> ---
>
> Key: IGNITE-14453
> URL: https://issues.apache.org/jira/browse/IGNITE-14453
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.10
> Environment: Apache Ignite with openJDK-15 (java version 15.0.1)
>Reporter: Emmanuel Wiesenfeld
>Priority: Major
> Attachments: ignite-jdk16.sh
>
>
> When using the following code:
>
> {code:java}
> IgniteConfiguration cfg = new IgniteConfiguration();
> //data storage configuration
> DataStorageConfiguration storageCfg = new DataStorageConfiguration();
> storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
> cfg.setDataStorageConfiguration(storageCfg);
> Ignite ignite = Ignition.start(cfg);{code}
>
> I get this upon startup:
> {code:java}
> SEVERE: Got exception while starting (will rollback startup routine).
> java.lang.NullPointerException: Cannot invoke
> "java.lang.reflect.Method.invoke(Object, Object[])" because
> "org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.mappingOffset"
> is null
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:449)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:418)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.flush(FileHandleManagerImpl.java:269)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.flush(FileWriteAheadLogManager.java:934)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.tailPointer(GridCacheDatabaseSharedManager.java:1968)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1908)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1299)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2112)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:663)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:328){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
