[jira] [Updated] (IGNITE-21973) Extend test coverage for SQL F201(CAST function)
[ https://issues.apache.org/jira/browse/IGNITE-21973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-21973: -- Fix Version/s: 3.0.0-beta2 > Extend test coverage for SQL F201(CAST function) > > > Key: IGNITE-21973 > URL: https://issues.apache.org/jira/browse/IGNITE-21973 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Maksim Zhuravkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Test coverage for SQL F201(CAST function) is poor. > Let's increase the test coverage. > > ref - test/sql/cast/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21973) Extend test coverage for SQL F201(CAST function)
[ https://issues.apache.org/jira/browse/IGNITE-21973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-21973: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Extend test coverage for SQL F201(CAST function) > > > Key: IGNITE-21973 > URL: https://issues.apache.org/jira/browse/IGNITE-21973 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Maksim Zhuravkov >Priority: Major > Labels: ignite-3 > Time Spent: 1h 40m > Remaining Estimate: 0h > > Test coverage for SQL F201(CAST function) is poor. > Let's increase the test coverage. > > ref - test/sql/cast/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17086) SQL: long query warning not printed for lazy queries
[ https://issues.apache.org/jira/browse/IGNITE-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy reassigned IGNITE-17086: --- Assignee: Oleg Valuyskiy > SQL: long query warning not printed for lazy queries > > > Key: IGNITE-17086 > URL: https://issues.apache.org/jira/browse/IGNITE-17086 > Project: Ignite > Issue Type: Bug >Reporter: Nikita Amelchev >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > Attachments: LongQueryWarningTest.java > > > Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22534) Add double constructor and serialization/deserialization code to the decimal type
Dmitrii Zabotlin created IGNITE-22534: - Summary: Add double constructor and serialization/deserialization code to the decimal type Key: IGNITE-22534 URL: https://issues.apache.org/jira/browse/IGNITE-22534 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Dmitrii Zabotlin Assignee: Dmitrii Zabotlin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22270) MarshallerException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-22270: - Assignee: Andrey Mashenkov > MarshallerException uses INTERNAL_ERR code > -- > > Key: IGNITE-22270 > URL: https://issues.apache.org/jira/browse/IGNITE-22270 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > *INTERNAL_ERR* does not make sense for *MarshallerException* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22533) Extra error when trying to run non-existant sql file
Igor Gusev created IGNITE-22533: --- Summary: Extra error when trying to run non-existant sql file Key: IGNITE-22533 URL: https://issues.apache.org/jira/browse/IGNITE-22533 Project: Ignite Issue Type: Task Reporter: Igor Gusev When trying to execute a non-existant sql file, there is an unknown error and then a real error: ``` [defaultNode]> sql --file=world.sq Unknown error File [/mnt/d/Work/gg9/gridgain9-cli-9.0.127-SNAPSHOT/../../../world.sq] not found ``` We need to have only one error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22532) --metastorage-group should be optional
[
https://issues.apache.org/jira/browse/IGNITE-22532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-22532:
---
Labels: ignite-3 (was: )
> --metastorage-group should be optional
> --
>
> Key: IGNITE-22532
> URL: https://issues.apache.org/jira/browse/IGNITE-22532
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3
>
> {code:bash}
> node1]> cluster init --cluster-name=TEST
> --cluster-management-group=node1,node2,node3
> Missing required options: '--metastorage-group=',
> '--name='
> Usage: cluster init [-hv] --name= [--url=]
> [--cluster-management-group=[, name>...]]... --metastorage-group=[, name>...] [--metastorage-group=[, name>...]]... [--config= | --config-file=]
> Initializes an Ignite cluster
> --cluster-management-group=[,...]
> Names of nodes (use comma-separated list of node
>names '--cluster-management-group node1, node2'
>to specify more than one node) those will host
>the Cluster Management Group.If omitted, then
>--meta-store-node values will also supply the
>nodes for the Cluster Management Group.
> --config= Cluster configuration that will be applied during
>the cluster initialization
> --config-file= Path to cluster configuration file
> -h, --help Show help for the specified command
> --metastorage-group=[,...]
> Metastorage group nodes (use comma-separated list
>of node names '--metastorage-group node1,
> node2'
>to specify more than one node) that will host
>the Meta Storage.If the --metastorage-group
>parameter is omitted, the same nodes will also
>host the Cluster Management Group.
> --name= Human-readable name of the cluster
> --url= URL of cluster endpoint. It can be any node
> URL.If
>not set, then the default URL from the profile
>settings will be used
> -v, --verbose Show additional information: logs, REST
> calls.This
>flag is useful for debugging
> [node1]>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22532) --metastorage-group should be optional
Aleksandr created IGNITE-22532:
--
Summary: --metastorage-group should be optional
Key: IGNITE-22532
URL: https://issues.apache.org/jira/browse/IGNITE-22532
Project: Ignite
Issue Type: Improvement
Reporter: Aleksandr
{code:bash}
node1]> cluster init --cluster-name=TEST
--cluster-management-group=node1,node2,node3
Missing required options: '--metastorage-group=',
'--name='
Usage: cluster init [-hv] --name= [--url=]
[--cluster-management-group=[,...]]... --metastorage-group=[,...] [--metastorage-group=[,...]]... [--config= | --config-file=]
Initializes an Ignite cluster
--cluster-management-group=[,...]
Names of nodes (use comma-separated list of node
names '--cluster-management-group node1, node2'
to specify more than one node) those will host
the Cluster Management Group.If omitted, then
--meta-store-node values will also supply the
nodes for the Cluster Management Group.
--config= Cluster configuration that will be applied during
the cluster initialization
--config-file= Path to cluster configuration file
-h, --help Show help for the specified command
--metastorage-group=[,...]
Metastorage group nodes (use comma-separated list
of node names '--metastorage-group node1, node2'
to specify more than one node) that will host
the Meta Storage.If the --metastorage-group
parameter is omitted, the same nodes will also
host the Cluster Management Group.
--name= Human-readable name of the cluster
--url= URL of cluster endpoint. It can be any node URL.If
not set, then the default URL from the profile
settings will be used
-v, --verbose Show additional information: logs, REST calls.This
flag is useful for debugging
[node1]>
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22512) Make MapReduceTask methods asynchronous
[ https://issues.apache.org/jira/browse/IGNITE-22512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855934#comment-17855934 ] Mikhail Pochatkin commented on IGNITE-22512: LGTM Thanks! Merged to main 0069defae43414a72c8c24285195ddc5034771a8 > Make MapReduceTask methods asynchronous > --- > > Key: IGNITE-22512 > URL: https://issues.apache.org/jira/browse/IGNITE-22512 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > > After compute job's execute method was made asynchronous, it makes sense to > make the same change for the map reduce task. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22427) Fix JobExecution.cancelAsync semantics
[
https://issues.apache.org/jira/browse/IGNITE-22427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855932#comment-17855932
]
Mikhail Pochatkin commented on IGNITE-22427:
LGTM Thanks!
Merged to main 139ef93389b1af910e2ce8d58e9ec9ed84eb74b9
> Fix JobExecution.cancelAsync semantics
> --
>
> Key: IGNITE-22427
> URL: https://issues.apache.org/jira/browse/IGNITE-22427
> Project: Ignite
> Issue Type: Improvement
> Components: compute
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Javadoc says:
> {code}
> returns {@code false} when the job couldn't be cancelled (either it's not yet
> started...
> {code}
> If the job is not yet started, it should be removed from the queue:
> * Make sure the method works as expected
> * Fix javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22433) Add TaskExecutionContext.isCancelled
[ https://issues.apache.org/jira/browse/IGNITE-22433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855912#comment-17855912 ] Mikhail Pochatkin commented on IGNITE-22433: LGTM Thanks! Merged to main 6c9c9a26c6e177380f5cadec3ca367d946cfdbdf > Add TaskExecutionContext.isCancelled > > > Key: IGNITE-22433 > URL: https://issues.apache.org/jira/browse/IGNITE-22433 > Project: Ignite > Issue Type: Improvement > Components: compute >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 40m > Remaining Estimate: 0h > > Add *TaskExecutionContext.isCancelled* to compliment > *JobExecutionContext.isCancelled* (see IGNITE-22428) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22521) ItIgniteNodeRestartTest.testSequentialAsyncTableCreationThenAlterZoneThenRestartOnMsSnapshot is flaky
[ https://issues.apache.org/jira/browse/IGNITE-22521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-22521: - Labels: ignite-3 (was: ) > ItIgniteNodeRestartTest.testSequentialAsyncTableCreationThenAlterZoneThenRestartOnMsSnapshot > is flaky > - > > Key: IGNITE-22521 > URL: https://issues.apache.org/jira/browse/IGNITE-22521 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22522) Remove temporary code, which was introduced for iterative collocation development
[ https://issues.apache.org/jira/browse/IGNITE-22522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-22522: - Labels: ignite-3 (was: ) > Remove temporary code, which was introduced for iterative collocation > development > - > > Key: IGNITE-22522 > URL: https://issues.apache.org/jira/browse/IGNITE-22522 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Gusakov >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22508) Support Pojos in ComputeJob
[ https://issues.apache.org/jira/browse/IGNITE-22508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-22508: - Labels: ignite-3 (was: ) > Support Pojos in ComputeJob > --- > > Key: IGNITE-22508 > URL: https://issues.apache.org/jira/browse/IGNITE-22508 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Priority: Major > Labels: ignite-3 > > After IGNITE-22477 is done, we have to support pojo serde into/from > BinaryTuple. PlatformTestRunner.ColocationHashJob should be enabled also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22506) Table size can be useful in many ways including SQL planning. Also users expect to have such an API exposed to them.
[
https://issues.apache.org/jira/browse/IGNITE-22506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-22506:
-
Labels: ignite-3 (was: )
> Table size can be useful in many ways including SQL planning. Also users
> expect to have such an API exposed to them.
>
>
> Key: IGNITE-22506
> URL: https://issues.apache.org/jira/browse/IGNITE-22506
> Project: Ignite
> Issue Type: Epic
>Reporter: Vladimir Pligin
>Priority: Major
> Labels: ignite-3
>
> Currently there is no equivalent for cache.size().
> The only way to get the size is
> {code:java}
> select count(*) from table {code}
> And this is a is slow operation as it scans the entire dataset.
> Initially we should start by providing an eventually-consistent size
> table.sizeEstimate() It needs to be the true size under no load, and it can
> kind of show whatever under load. It is NOT a transactional method. We might
> even forbid to call it in a transactional context.
> For SQL, let's at least make sure that count can execute over the index
> without reading the actual data. This would be a useful optimization for many
> cases and should give a semi-reasonable performance for both RW and RO.
> I think it's also possible to delegate select count from table to
> table.sizeEstimate() when it isn't in an explicit transaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22480) Sql. Optimize performance of multistatement with simple inserts
[ https://issues.apache.org/jira/browse/IGNITE-22480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-22480: - Labels: ignite-3 (was: ) > Sql. Optimize performance of multistatement with simple inserts > --- > > Key: IGNITE-22480 > URL: https://issues.apache.org/jira/browse/IGNITE-22480 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Pavel Pereslegin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Execution multistatement contains a big amount of INSERT statements take to > much time. For example, world.sql from AI2 contains about 5k insert > statements that took more than 2 minutes on my local machine. However, if the > multistatement rewrite to a few inserts contains multi values (e.g. insert > into t(a,b) values(1,2) values (2,3) values.) then it took just a few > seconds. > The fast check shows that most of the time consuptions by expression > compilation. > We have a few options for how it could be resolved: > 1. Use expression interpretation for simple cases instead of compilation to > java class. > 2. Dynamically rewrite such inserts to prepared statements. > 3. On AST level extract values (it will work just for literals) and create > tuple for inserting by hands. > Options ordered by the hardness of implementation. Let's start from 3rd, as > the simplest to implement, and check how it will work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22462) Sql. Add planner test to verify type coercion for set operations like UNION, INTERSECT and EXCEPT
[ https://issues.apache.org/jira/browse/IGNITE-22462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-22462: - Labels: ignite-3 (was: ) > Sql. Add planner test to verify type coercion for set operations like UNION, > INTERSECT and EXCEPT > - > > Key: IGNITE-22462 > URL: https://issues.apache.org/jira/browse/IGNITE-22462 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > Let's add new tests to validate type coercion for set operations like UNION, > INTERSECT and EXCEPT. The tests should be as easy as possible, every test > case must answer a question "what are expected types of each set operation > when we use a given numeric type pair?" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22531) NPE on configuration update
[ https://issues.apache.org/jira/browse/IGNITE-22531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev resolved IGNITE-22531. -- Resolution: Invalid > NPE on configuration update > --- > > Key: IGNITE-22531 > URL: https://issues.apache.org/jira/browse/IGNITE-22531 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Priority: Critical > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22531) NPE on configuration update
Aleksandr Polovtsev created IGNITE-22531: Summary: NPE on configuration update Key: IGNITE-22531 URL: https://issues.apache.org/jira/browse/IGNITE-22531 Project: Ignite Issue Type: Bug Reporter: Aleksandr Polovtsev -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22510) Configuration is used before start
[ https://issues.apache.org/jira/browse/IGNITE-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-22510: - Description: MetaStorageWriteHandler#evictIdempotentCommandsCache uses distributed configuration in order to retrieve maxClockSkew. Given method was mistakenly called from within MS onWrite that may be evaluated on MS raft group start prior to distributed configuration start. As a result we may catch a NPE. > Configuration is used before start > -- > > Key: IGNITE-22510 > URL: https://issues.apache.org/jira/browse/IGNITE-22510 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > MetaStorageWriteHandler#evictIdempotentCommandsCache uses distributed > configuration in order to retrieve maxClockSkew. > Given method was mistakenly called from within MS onWrite that may be > evaluated on MS raft group start prior to distributed configuration start. > As a result we may catch a NPE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22073) Sql. Add processing of the provided query timeout
[
https://issues.apache.org/jira/browse/IGNITE-22073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-22073:
-
Assignee: (was: Pavel Pereslegin)
> Sql. Add processing of the provided query timeout
> -
>
> Key: IGNITE-22073
> URL: https://issues.apache.org/jira/browse/IGNITE-22073
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> Public org.apache.ignite.sql.Statement contains {{queryTimeout}} parameter,
> which user can change using {{StatementBuilder}}.
> {code:java}
> /**
> * Sets a query timeout.
> *
> * @param timeout Query timeout value.
> * @param timeUnit Timeunit.
> * @return {@code this} for chaining.
> */
> StatementBuilder queryTimeout(long timeout, TimeUnit timeUnit);
> {code}
> I'm guessing that by using this option the user can expect the query to be
> aborted when it times out. We need to implement handling of this option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22530) CDC: Add regex filters for cache names
[ https://issues.apache.org/jira/browse/IGNITE-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-22530: --- Description: *Motivation:* Currently, we can specify cache names _only explicitly as list_ in configuration files. But, if we create new cache, it will not be processed by CDC, until cluster and CDC applications are not restarted with updated configuration. For example, if we need all caches to be replicated, it seems that most convenient way to do so, is to specify some kind of asterisk or regex filter. *Proposed solution:* # Add regex filters to all CDC classes with configured cache names: CdcConsumer implementations, ConflictResolver implementations and KafkaToIgnite streamers. # Current way to specify caches list must remain available in order to preserve compatibility. # Optional exclude filter also should be implemented. # Multiple include and exclude filters should be supported. # It should be compatible with realtime CDC. was: *Motivation:* Currently, we can specify cache names _only explicitly as list_ in configuration files. But, if we create new cache, it will not be processed by CDC, until cluster and CDC applications are not restarted with updated configuration. For example, if we need all caches to be replicated, it seems that most convenient way to do so, is to specify some kind of asterisk or regex filter. *Proposed solution:* # Add regex filters to all CDC classes with configured cache names: CdcConsumer implementations, ConflictResolver implementations and KafkaToIgnite streamers. # Current way to specify caches list must remain available in order to preserve compatibility. # Optional exclude filter also should be implemented. # Multiple include and exclude filters should be implemented. # It should be compatible with realtime CDC. > CDC: Add regex filters for cache names > -- > > Key: IGNITE-22530 > URL: https://issues.apache.org/jira/browse/IGNITE-22530 > Project: Ignite > Issue Type: New Feature > Components: extensions >Reporter: Ilya Shishkov >Priority: Major > Labels: IEP-59, ise > > *Motivation:* > Currently, we can specify cache names _only explicitly as list_ in > configuration files. But, if we create new cache, it will not be processed by > CDC, until cluster and CDC applications are not restarted with updated > configuration. > For example, if we need all caches to be replicated, it seems that most > convenient way to do so, is to specify some kind of asterisk or regex filter. > *Proposed solution:* > # Add regex filters to all CDC classes with configured cache names: > CdcConsumer implementations, ConflictResolver implementations and > KafkaToIgnite streamers. > # Current way to specify caches list must remain available in order to > preserve compatibility. > # Optional exclude filter also should be implemented. > # Multiple include and exclude filters should be supported. > # It should be compatible with realtime CDC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22530) CDC: Add regex filters for cache names
[
https://issues.apache.org/jira/browse/IGNITE-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-22530:
---
Description:
*Motivation:*
Currently, we can specify cache names _only explicitly as list_ in
configuration files. But, if we create new cache, it will not be processed by
CDC, until cluster and CDC applications are not restarted with updated
configuration.
For example, if we need all caches to be replicated, it seems that most
convenient way to do so, is to specify some kind of asterisk or regex filter.
*Proposed solution:*
# Add regex filters to all CDC classes with configured cache names: CdcConsumer
implementations, ConflictResolver implementations and KafkaToIgnite streamers.
# Current way to specify caches list must remain available in order to preserve
compatibility.
# Optional exclude filter also should be implemented.
# Multiple include and exclude filters should be implemented.
# It should be compatible with realtime CDC.
was:
We need metrics for received events count and last received event timestamp for
the {{KafkaToIgniteStreamer}}, because there can be situations, when events
sent by {{IgniteToKafkaStreamer}} are lost in Kafka due to Kafka failures or
topic's retention configuration.
In such situations we should be able to compare to sent messages count on
source cluster with received messages count on destination one. Timestamp of
last received event would be also useful.
> CDC: Add regex filters for cache names
> --
>
> Key: IGNITE-22530
> URL: https://issues.apache.org/jira/browse/IGNITE-22530
> Project: Ignite
> Issue Type: New Feature
> Components: extensions
>Reporter: Ilya Shishkov
>Priority: Major
> Labels: IEP-59, ise
>
> *Motivation:*
> Currently, we can specify cache names _only explicitly as list_ in
> configuration files. But, if we create new cache, it will not be processed by
> CDC, until cluster and CDC applications are not restarted with updated
> configuration.
> For example, if we need all caches to be replicated, it seems that most
> convenient way to do so, is to specify some kind of asterisk or regex filter.
> *Proposed solution:*
> # Add regex filters to all CDC classes with configured cache names:
> CdcConsumer implementations, ConflictResolver implementations and
> KafkaToIgnite streamers.
> # Current way to specify caches list must remain available in order to
> preserve compatibility.
> # Optional exclude filter also should be implemented.
> # Multiple include and exclude filters should be implemented.
> # It should be compatible with realtime CDC.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22430) Rename JobStatus to JobState and vice versa
[ https://issues.apache.org/jira/browse/IGNITE-22430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev reassigned IGNITE-22430: - Assignee: Vadim Pakhnushev > Rename JobStatus to JobState and vice versa > --- > > Key: IGNITE-22430 > URL: https://issues.apache.org/jira/browse/IGNITE-22430 > Project: Ignite > Issue Type: Improvement > Components: compute >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > * *o.a.i.compute.JobStatus* -> *JobState* > * *JobState* -> *JobStatus* > *Status* is more suitable for enums. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21491) Calcite engine: AssertionError in case of multiple statements queries
[
https://issues.apache.org/jira/browse/IGNITE-21491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky resolved IGNITE-21491.
--
Fix Version/s: 2.17
Resolution: Fixed
[~alexpl] Thanks for review, merged
> Calcite engine: AssertionError in case of multiple statements queries
> --
>
> Key: IGNITE-21491
> URL: https://issues.apache.org/jira/browse/IGNITE-21491
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikita Amelchev
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When using the calcite engine and the thin client, an error occurs in case of
> a query with multiple statements:
> {noformat}
> Failed to process client request
> [req=o.a.i.i.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest@5683de08,
> msg=null]
> java.lang.AssertionError: null
> at
> org.apache.ignite.internal.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest.process(ClientCacheSqlFieldsQueryRequest.java:152)
>
> {noformat}
> In the old engine there was a readable message: Multiple statements queries
> are not supported.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21491) Calcite engine: AssertionError in case of multiple statements queries
[
https://issues.apache.org/jira/browse/IGNITE-21491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855867#comment-17855867
]
Ignite TC Bot commented on IGNITE-21491:
{panel:title=Branch: [pull/11394/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11394/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7919793]]
* {color:#013220}IgniteCalciteTestSuite:
MultiLineQueryTest.testMultilineThrowsProperException[engine=h2] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
MultiLineQueryTest.testMultilineThrowsProperException[engine=calcite] -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7918767&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine: AssertionError in case of multiple statements queries
> --
>
> Key: IGNITE-21491
> URL: https://issues.apache.org/jira/browse/IGNITE-21491
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikita Amelchev
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using the calcite engine and the thin client, an error occurs in case of
> a query with multiple statements:
> {noformat}
> Failed to process client request
> [req=o.a.i.i.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest@5683de08,
> msg=null]
> java.lang.AssertionError: null
> at
> org.apache.ignite.internal.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest.process(ClientCacheSqlFieldsQueryRequest.java:152)
>
> {noformat}
> In the old engine there was a readable message: Multiple statements queries
> are not supported.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-20263) Get rid of DataStorageConfigurationSchema
[
https://issues.apache.org/jira/browse/IGNITE-20263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko resolved IGNITE-20263.
--
Resolution: Won't Do
No need to do this because there is no such configuration anymore.
> Get rid of DataStorageConfigurationSchema
> -
>
> Key: IGNITE-20263
> URL: https://issues.apache.org/jira/browse/IGNITE-20263
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> We need to get rid of
> {*}org.apache.ignite.internal.schema.configuration.storage.DataStorageConfigurationSchema{*},
> its descendants and the code associated with it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22530) CDC: Add regex filters for cache names
[
https://issues.apache.org/jira/browse/IGNITE-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov reassigned IGNITE-22530:
--
Assignee: Ilya Shishkov (was: Maksim Davydov)
> CDC: Add regex filters for cache names
> --
>
> Key: IGNITE-22530
> URL: https://issues.apache.org/jira/browse/IGNITE-22530
> Project: Ignite
> Issue Type: New Feature
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Major
> Labels: IEP-59, ise
>
> We need metrics for received events count and last received event timestamp
> for the {{KafkaToIgniteStreamer}}, because there can be situations, when
> events sent by {{IgniteToKafkaStreamer}} are lost in Kafka due to Kafka
> failures or topic's retention configuration.
> In such situations we should be able to compare to sent messages count on
> source cluster with received messages count on destination one. Timestamp of
> last received event would be also useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22530) CDC: Add regex filters for cache names
[
https://issues.apache.org/jira/browse/IGNITE-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-22530:
---
Priority: Minor (was: Major)
> CDC: Add regex filters for cache names
> --
>
> Key: IGNITE-22530
> URL: https://issues.apache.org/jira/browse/IGNITE-22530
> Project: Ignite
> Issue Type: New Feature
> Components: extensions
>Reporter: Ilya Shishkov
>Priority: Minor
> Labels: IEP-59, ise
>
> We need metrics for received events count and last received event timestamp
> for the {{KafkaToIgniteStreamer}}, because there can be situations, when
> events sent by {{IgniteToKafkaStreamer}} are lost in Kafka due to Kafka
> failures or topic's retention configuration.
> In such situations we should be able to compare to sent messages count on
> source cluster with received messages count on destination one. Timestamp of
> last received event would be also useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22530) CDC: Add regex filters for cache names
[
https://issues.apache.org/jira/browse/IGNITE-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov reassigned IGNITE-22530:
--
Assignee: (was: Ilya Shishkov)
> CDC: Add regex filters for cache names
> --
>
> Key: IGNITE-22530
> URL: https://issues.apache.org/jira/browse/IGNITE-22530
> Project: Ignite
> Issue Type: New Feature
> Components: extensions
>Reporter: Ilya Shishkov
>Priority: Major
> Labels: IEP-59, ise
>
> We need metrics for received events count and last received event timestamp
> for the {{KafkaToIgniteStreamer}}, because there can be situations, when
> events sent by {{IgniteToKafkaStreamer}} are lost in Kafka due to Kafka
> failures or topic's retention configuration.
> In such situations we should be able to compare to sent messages count on
> source cluster with received messages count on destination one. Timestamp of
> last received event would be also useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22530) CDC: Add regex filters for cache names
Ilya Shishkov created IGNITE-22530:
--
Summary: CDC: Add regex filters for cache names
Key: IGNITE-22530
URL: https://issues.apache.org/jira/browse/IGNITE-22530
Project: Ignite
Issue Type: New Feature
Components: extensions
Reporter: Ilya Shishkov
Assignee: Maksim Davydov
We need metrics for received events count and last received event timestamp for
the {{KafkaToIgniteStreamer}}, because there can be situations, when events
sent by {{IgniteToKafkaStreamer}} are lost in Kafka due to Kafka failures or
topic's retention configuration.
In such situations we should be able to compare to sent messages count on
source cluster with received messages count on destination one. Timestamp of
last received event would be also useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22530) CDC: Add regex filters for cache names
[
https://issues.apache.org/jira/browse/IGNITE-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-22530:
---
Priority: Major (was: Minor)
> CDC: Add regex filters for cache names
> --
>
> Key: IGNITE-22530
> URL: https://issues.apache.org/jira/browse/IGNITE-22530
> Project: Ignite
> Issue Type: New Feature
> Components: extensions
>Reporter: Ilya Shishkov
>Priority: Major
> Labels: IEP-59, ise
>
> We need metrics for received events count and last received event timestamp
> for the {{KafkaToIgniteStreamer}}, because there can be situations, when
> events sent by {{IgniteToKafkaStreamer}} are lost in Kafka due to Kafka
> failures or topic's retention configuration.
> In such situations we should be able to compare to sent messages count on
> source cluster with received messages count on destination one. Timestamp of
> last received event would be also useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22264) Startup instructions in examples are outdated
[ https://issues.apache.org/jira/browse/IGNITE-22264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Artiukhov reassigned IGNITE-22264: --- Assignee: Ivan Artiukhov > Startup instructions in examples are outdated > - > > Key: IGNITE-22264 > URL: https://issues.apache.org/jira/browse/IGNITE-22264 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Pavel Tupitsyn >Assignee: Ivan Artiukhov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Verify startup instructions (at the top of every example), make sure they > work with upcoming Ignite beta2. > https://github.com/apache/ignite-3/tree/main/examples/src/main/java/org/apache/ignite/example -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22529) Make platforms CMake more usable as subproject
Dmitrii Zabotlin created IGNITE-22529: - Summary: Make platforms CMake more usable as subproject Key: IGNITE-22529 URL: https://issues.apache.org/jira/browse/IGNITE-22529 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Dmitrii Zabotlin Assignee: Dmitrii Zabotlin Make cmake in platforms module a bit friendly to be included as subproject. We should choose cmake variables more carefully to have consistent paths when platforms included as subproject. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22505) Page memory meta pages are allocated without reuse
[ https://issues.apache.org/jira/browse/IGNITE-22505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22505: - Fix Version/s: 3.0.0-beta2 > Page memory meta pages are allocated without reuse > > > Key: IGNITE-22505 > URL: https://issues.apache.org/jira/browse/IGNITE-22505 > Project: Ignite > Issue Type: Improvement > Components: data structures >Reporter: Philipp Shergalis >Assignee: Philipp Shergalis >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Currently we always allocate new page creating a new tree, thus leaking > memory, instead of recycling page from reuseList -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22467) PlacementDriver should have a method to return an assignments for a specified partition
[ https://issues.apache.org/jira/browse/IGNITE-22467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin reassigned IGNITE-22467: Assignee: Alexander Lapin > PlacementDriver should have a method to return an assignments for a specified > partition > --- > > Key: IGNITE-22467 > URL: https://issues.apache.org/jira/browse/IGNITE-22467 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > > TBD -- This message was sent by Atlassian Jira (v8.20.10#820010)
