[jira] [Created] (IGNITE-20466) Investigate running sonar checks from fork repositories
Maxim Muzafarov created IGNITE-20466: Summary: Investigate running sonar checks from fork repositories Key: IGNITE-20466 URL: https://issues.apache.org/jira/browse/IGNITE-20466 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Investigate running sonar checks from fork repositories. See the discussion here: https://github.com/actions/checkout/issues/518 Additionally, we can run checks after a pull-request has been approved by a maintainer: https://github.com/orgs/community/discussions/25372 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20019) Introduce SystemViewManager
[ https://issues.apache.org/jira/browse/IGNITE-20019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767604#comment-17767604 ] Pavel Pereslegin commented on IGNITE-20019: --- [~korlov], [~mzhuravkov], do a review of the proposed changes, please. > Introduce SystemViewManager > --- > > Key: IGNITE-20019 > URL: https://issues.apache.org/jira/browse/IGNITE-20019 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Pavel Pereslegin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > SystemViewManager is a component responsible for managing the system views': > * during start, any component may register view definition to the view > manager. View manager must ensure that there is no clashes in the views' > names. > * before node is going to be validated, view manager must enhance node > attributes (LogicalNode class) with list of clusterViews registered so far. > Later, sql engine will be using this information to map queries over cluster > views properly > * after node has passed validation and ready to join logical topology, view > manager must register all views to the catalog. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-20019) Introduce SystemViewManager
[ https://issues.apache.org/jira/browse/IGNITE-20019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767604#comment-17767604 ] Pavel Pereslegin edited comment on IGNITE-20019 at 9/21/23 3:14 PM: [~korlov], [~mzhuravkov], do a review of the proposed changes, please. was (Author: xtern): [~korlov], [~mzhuravkov], do a review of the proposed changes, please. > Introduce SystemViewManager > --- > > Key: IGNITE-20019 > URL: https://issues.apache.org/jira/browse/IGNITE-20019 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Pavel Pereslegin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > SystemViewManager is a component responsible for managing the system views': > * during start, any component may register view definition to the view > manager. View manager must ensure that there is no clashes in the views' > names. > * before node is going to be validated, view manager must enhance node > attributes (LogicalNode class) with list of clusterViews registered so far. > Later, sql engine will be using this information to map queries over cluster > views properly > * after node has passed validation and ready to join logical topology, view > manager must register all views to the catalog. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20019) Introduce SystemViewManager
[ https://issues.apache.org/jira/browse/IGNITE-20019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-20019: -- Fix Version/s: 3.0.0-beta2 > Introduce SystemViewManager > --- > > Key: IGNITE-20019 > URL: https://issues.apache.org/jira/browse/IGNITE-20019 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Pavel Pereslegin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > SystemViewManager is a component responsible for managing the system views': > * during start, any component may register view definition to the view > manager. View manager must ensure that there is no clashes in the views' > names. > * before node is going to be validated, view manager must enhance node > attributes (LogicalNode class) with list of clusterViews registered so far. > Later, sql engine will be using this information to map queries over cluster > views properly > * after node has passed validation and ready to join logical topology, view > manager must register all views to the catalog. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20387) Remap most exceptions to SqlExceptions for SQL API
[ https://issues.apache.org/jira/browse/IGNITE-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich reassigned IGNITE-20387: -- Assignee: Yury Gerzhedovich > Remap most exceptions to SqlExceptions for SQL API > -- > > Key: IGNITE-20387 > URL: https://issues.apache.org/jira/browse/IGNITE-20387 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > As of now SQL API could throw different type of Exceptions like a > TableAlreadyExistsException, TableNotFoundException, > ColumnAlreadyExistsException and so one. It looks incorrect due to SQL API > should operate just SqlExceptions. > Let's do right mapping in SqlExceptionMapperProvider. > To have more simple test also let's try to generify synchoonus and > asynchronous test (see ItSqlSynchronousApiTest and ItSqlAsynchronousApiTest). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20465) *.mvccEnabled() removal
[ https://issues.apache.org/jira/browse/IGNITE-20465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20465: -- Ignite Flags: (was: Docs Required,Release Notes Required) > *.mvccEnabled() removal > --- > > Key: IGNITE-20465 > URL: https://issues.apache.org/jira/browse/IGNITE-20465 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20465) *.mvccEnabled() removal
[ https://issues.apache.org/jira/browse/IGNITE-20465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20465: -- Fix Version/s: 2.16 > *.mvccEnabled() removal > --- > > Key: IGNITE-20465 > URL: https://issues.apache.org/jira/browse/IGNITE-20465 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20356) Sql. Rework RowHandler "set" operation.
[
https://issues.apache.org/jira/browse/IGNITE-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-20356:
-
Assignee: Pavel Pereslegin
> Sql. Rework RowHandler "set" operation.
> ---
>
> Key: IGNITE-20356
> URL: https://issues.apache.org/jira/browse/IGNITE-20356
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> In IGNITE-19791, a wrapper over {{BinaryTuple}} was added.
> This wrapper ({{BinaryTupleRowWrapper}}) does not support the "{{set()}}"
> method
> Instead of using {{set(int, RowT, Object)}} method, we can use the
> {{append(RowT, Object)}} method to add field values sequentially.
> We need:
> * Add a new RowFactory method that will return a builder that allows you to
> append values to row and build the row.
> * Remove the {{RowHandler#set()}} method and rework all related code/tests
> to use the builder.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20465) *.mvccEnabled() removal
Anton Vinogradov created IGNITE-20465: - Summary: *.mvccEnabled() removal Key: IGNITE-20465 URL: https://issues.apache.org/jira/browse/IGNITE-20465 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19988) Add index creation (population) status to index view
[ https://issues.apache.org/jira/browse/IGNITE-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov reassigned IGNITE-19988: --- Assignee: Mikhail Petrov > Add index creation (population) status to index view > > > Key: IGNITE-19988 > URL: https://issues.apache.org/jira/browse/IGNITE-19988 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.15 >Reporter: Ivan Daschinsky >Assignee: Mikhail Petrov >Priority: Major > Labels: ise > Fix For: 2.16 > > > Sometimes index creation can be quite long. A user might start queries > without waiting for finish of the index creation process and see slow > queries. It is necessary to provide index status information to users by > exposing it in the index system view. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20464) Add consistent id to the index validate result.
[ https://issues.apache.org/jira/browse/IGNITE-20464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin reassigned IGNITE-20464: - Assignee: (was: Vladimir Steshin) > Add consistent id to the index validate result. > --- > > Key: IGNITE-20464 > URL: https://issues.apache.org/jira/browse/IGNITE-20464 > Project: Ignite > Issue Type: Task >Reporter: Vladimir Steshin >Priority: Minor > Labels: ise > > Output of '--cache validate_indexes' command might have node consistent id > like the result of the idle verify. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20464) Add consistent id to the index validate result.
Vladimir Steshin created IGNITE-20464: - Summary: Add consistent id to the index validate result. Key: IGNITE-20464 URL: https://issues.apache.org/jira/browse/IGNITE-20464 Project: Ignite Issue Type: Task Reporter: Vladimir Steshin Assignee: Vladimir Steshin Output of '--cache validate_indexes' command might have node consistent id like the result of the idle verify. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20464) Add consistent id to the index validate result.
[ https://issues.apache.org/jira/browse/IGNITE-20464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-20464: -- Labels: ise (was: ) > Add consistent id to the index validate result. > --- > > Key: IGNITE-20464 > URL: https://issues.apache.org/jira/browse/IGNITE-20464 > Project: Ignite > Issue Type: Task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Labels: ise > > Output of '--cache validate_indexes' command might have node consistent id > like the result of the idle verify. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20420) Streamer metrics missing in ClientMetricSource.Holder.metrics
[ https://issues.apache.org/jira/browse/IGNITE-20420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767444#comment-17767444 ] Pavel Tupitsyn commented on IGNITE-20420: - Merged to main: 9429a3c61860f82cbbe23e0cc433b34d6c42508e > Streamer metrics missing in ClientMetricSource.Holder.metrics > - > > Key: IGNITE-20420 > URL: https://issues.apache.org/jira/browse/IGNITE-20420 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > *ClientMetricSource.Holder.metrics* does not have streamer metrics > (*streamerBatchesSent* etc). > Add a test to check that all metrics are registered (via reflection). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20420) Streamer metrics missing in ClientMetricSource.Holder.metrics
[ https://issues.apache.org/jira/browse/IGNITE-20420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767442#comment-17767442 ] Igor Sapego commented on IGNITE-20420: -- Looks good to me > Streamer metrics missing in ClientMetricSource.Holder.metrics > - > > Key: IGNITE-20420 > URL: https://issues.apache.org/jira/browse/IGNITE-20420 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > *ClientMetricSource.Holder.metrics* does not have streamer metrics > (*streamerBatchesSent* etc). > Add a test to check that all metrics are registered (via reflection). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20342) Rollback transaction for SQL execution issues
[ https://issues.apache.org/jira/browse/IGNITE-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov reassigned IGNITE-20342: - Assignee: Maksim Zhuravkov > Rollback transaction for SQL execution issues > - > > Key: IGNITE-20342 > URL: https://issues.apache.org/jira/browse/IGNITE-20342 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Maksim Zhuravkov >Priority: Major > Labels: ignite-3 > > During execution any data modification we could have runtime error, for > example divide to zero, which lead to cancellation of execution. Right now we > don't rollback transaction for the case and part of modification could be > applied despite of the error. > In ideal word we should be rollbacked just the DML statement, but right now > we don't support savepoint in transaction protocol. So, let's rollback any > type of transaction, explicit and implicit, for any DML statement in case > error is occurred. > Test which could show one of the case of the problem is > org.apache.ignite.internal.sql.api.ItSqlSynchronousApiTest#runtimeErrorInTransaction -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17882) Remove org.apache.ignite.binary.BinaryObject from public API
[ https://issues.apache.org/jira/browse/IGNITE-17882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov reassigned IGNITE-17882: - Assignee: Maksim Zhuravkov > Remove org.apache.ignite.binary.BinaryObject from public API > > > Key: IGNITE-17882 > URL: https://issues.apache.org/jira/browse/IGNITE-17882 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Assignee: Maksim Zhuravkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > It does not make sense to have BinaryObject interface in the public API until > IGNITE-14316 is resolved (this ticket should introduce the right interface(s) > at least). > For now, let's just remove BinaryObject. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19950) Snapshot of in-memory cache groups
[
https://issues.apache.org/jira/browse/IGNITE-19950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767394#comment-17767394
]
Ignite TC Bot commented on IGNITE-19950:
{panel:title=Branch: [pull/10936/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10936/head] Base: [master] : New Tests
(272)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Disk Page Compressions 1{color} [[tests
135|https://ci2.ignite.apache.org/viewLog.html?buildId=7344348]]
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testDumpCancelOnIteratorWriteError[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentEntryProcessor[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentRemovals[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testDumpWithExplicitExpireTime[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentInserts[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testDumpWithImplicitExpireTime[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testConcurrentDumpCreationThrows[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentInserts[nodes=1,backups=0,persistence=true,mode=ATOMIC]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testDumpWithImplicitExpireTime[nodes=1,backups=0,persistence=true,mode=ATOMIC]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testConcurrentDumpCreationThrows[nodes=1,backups=0,persistence=true,mode=ATOMIC]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteCacheDumpSelfTest.testDumpCancelOnIteratorWriteError[nodes=1,backups=0,persistence=true,mode=ATOMIC]
- PASSED{color}
... and 124 new tests
{color:#8b}Snapshots{color} [[tests
135|https://ci2.ignite.apache.org/viewLog.html?buildId=7342876]]
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testConcurrentDumpCreationThrows[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testDumpCancelOnIteratorWriteError[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentEntryProcessor[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentRemovals[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentInserts[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testDumpWithImplicitExpireTime[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testDumpCancelOnFileCreateError[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testWithConcurrentInserts[nodes=1,backups=0,persistence=true,mode=ATOMIC]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testDumpWithImplicitExpireTime[nodes=1,backups=0,persistence=true,mode=ATOMIC]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testConcurrentDumpCreationThrows[nodes=1,backups=0,persistence=true,mode=ATOMIC]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteCacheDumpSelfTest.testDumpWithExplicitExpireTime[nodes=1,backups=0,persistence=true,mode=TRANSACTIONAL]
- PASSED{color}
... and 124 new tests
{color:#8b}Queries 3{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7342869]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
DumpCacheConfigTest.testSQLTableDump - PASSED{color}
{color:#8b}Queries 3 (lazy=true){color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7342870]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
DumpCacheConfigTest.testSQLTableDump - PASSED{color}
{panel}
[TeamCity
[jira] [Created] (IGNITE-20463) Sql. Integration of TX-related statemnets into sql script processor.
Evgeny Stanilovsky created IGNITE-20463: --- Summary: Sql. Integration of TX-related statemnets into sql script processor. Key: IGNITE-20463 URL: https://issues.apache.org/jira/browse/IGNITE-20463 Project: Ignite Issue Type: New Feature Components: sql Affects Versions: 3.0.0-beta1 Reporter: Evgeny Stanilovsky Script processor [1] need to process tx related statements. After parsing appropriate transaction syntax it need to be retained and processed in script processor. [1] https://issues.apache.org/jira/browse/IGNITE-20443 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20444) Sql. Add restrictions for execution tx related statements with single statement mode.
[
https://issues.apache.org/jira/browse/IGNITE-20444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-20444:
Description:
Append single statement restrictions for using with new tx related sql syntax
[1] implementation.
{code:java}
try (Session ses = client.sql().createSession()) {
ses.execute(
null, "_new transactional statement from ignite-20442_"
<-- such calls need to be rejected
).close();
ses.execute(
null,
"some other sql statement"
).close();
}
{code}
[1] https://issues.apache.org/jira/browse/IGNITE-20442
was:
Append single statement restrictions for using with new tx related sql syntax
[1] implementation.
[1] https://issues.apache.org/jira/browse/IGNITE-20442
> Sql. Add restrictions for execution tx related statements with single
> statement mode.
> -
>
> Key: IGNITE-20444
> URL: https://issues.apache.org/jira/browse/IGNITE-20444
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: ignite-3
>
> Append single statement restrictions for using with new tx related sql syntax
> [1] implementation.
> {code:java}
> try (Session ses = client.sql().createSession()) {
> ses.execute(
> null, "_new transactional statement from
> ignite-20442_" <-- such calls need to be rejected
> ).close();
> ses.execute(
> null,
> "some other sql statement"
> ).close();
> }
> {code}
> [1] https://issues.apache.org/jira/browse/IGNITE-20442
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
