[jira] [Commented] (IGNITE-16401) Working in async manner for new SQL engine
[ https://issues.apache.org/jira/browse/IGNITE-16401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539328#comment-17539328 ] Evgeny Stanilovsky commented on IGNITE-16401: - [~korlov] does labels are correct here ? > Working in async manner for new SQL engine > -- > > Key: IGNITE-16401 > URL: https://issues.apache.org/jira/browse/IGNITE-16401 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: calcite, calcite3-required, ignite-3 > Time Spent: 4h 20m > Remaining Estimate: 0h > > As of now SQL working in synchronous mode. Seems we shouldn't block main > thread and have separate thread pool for planning, other tasks should use > executor pool. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-14196) SQL Calcite: prepare examples for documentation
[ https://issues.apache.org/jira/browse/IGNITE-14196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-14196: Labels: calcite (was: calcite3-required) > SQL Calcite: prepare examples for documentation > --- > > Key: IGNITE-14196 > URL: https://issues.apache.org/jira/browse/IGNITE-14196 > Project: Ignite > Issue Type: Task > Components: examples, sql > Environment: SQL >Reporter: Yury Gerzhedovich >Assignee: Aleksey Plekhanov >Priority: Major > Labels: calcite > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > Seems the first pre-alpha version of the Calcite engine will be released > together with the next version of Apache Ignite (2.11). So it required to > start preparing documentation. > The first step is preparing examples with explanation comments. Let's do it. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16826) Calcite engine. Support old "CREATE TABLE WITH options" syntax
[
https://issues.apache.org/jira/browse/IGNITE-16826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-16826:
Labels: calcite calcite2-required (was: calcite calcite2-required
calcite3-required)
> Calcite engine. Support old "CREATE TABLE WITH options" syntax
> --
>
> Key: IGNITE-16826
> URL: https://issues.apache.org/jira/browse/IGNITE-16826
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, calcite2-required
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, options for CREATE TABLE should be in format: \{{WITH key1="val1",
> key2="val2"}} (each option value double-quoted), but in H2-based query engine
> format was a little bit different: \{{WITH "key1=val1, key2=val2"}} (the
> whole option list double-quoted).
> We should support both syntaxes, since there are a lot of old-syntax queries
> in examples, documentation, etc.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-16550) Redesign SchemaRegistry to use causality tokens
[
https://issues.apache.org/jira/browse/IGNITE-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539053#comment-17539053
]
Vladislav Pyatkov commented on IGNITE-16550:
[~Denis Chudov] I left a few comments in the PR. Please look at them.
> Redesign SchemaRegistry to use causality tokens
> ---
>
> Key: IGNITE-16550
> URL: https://issues.apache.org/jira/browse/IGNITE-16550
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Denis Chudov
>Priority: Major
> Labels: ignite-3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
> the reason all method do not apply a token and work synchronously.
> After the redesign part of the methods should be removed
> (SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
> should entirely depend on causality.
> Possibly the new methods will return futures.
> UPD:
> It was decided that in the current ticket it's worth to decouple Schema logic
> from the {{TableManager}} and create a new manager called {{SchemaManager}},
> so we can integrate causality tokens logic to the {{SchemaManager}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17009) Support fragmented RowVersions
Roman Puchkovskiy created IGNITE-17009: -- Summary: Support fragmented RowVersions Key: IGNITE-17009 URL: https://issues.apache.org/jira/browse/IGNITE-17009 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-alpha5 RowVersionDataIo#writeFragmentData() needs to be properly implemented -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17008) Add support for NextLink field in VersionChain
Roman Puchkovskiy created IGNITE-17008: -- Summary: Add support for NextLink field in VersionChain Key: IGNITE-17008 URL: https://issues.apache.org/jira/browse/IGNITE-17008 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-alpha5 As described in IGNITE-16933 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17007) TxAbstractTest#testBalance is flaky
[
https://issues.apache.org/jira/browse/IGNITE-17007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-17007:
-
Labels: ignite-3 (was: )
> TxAbstractTest#testBalance is flaky
> ---
>
> Key: IGNITE-17007
> URL: https://issues.apache.org/jira/browse/IGNITE-17007
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Module_Table_2895.log
>
>
> Implementations of {{TxAbstractTest#testBalance}} sometimes fail when running
> on TeamCity:
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable?mode=builds#all-projects
> I wasn't able to reproduce these failures locally, so this might be a
> TC-specific issue.
> Example error log:
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable/6575460
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17007) TxAbstractTest#testBalance is flaky
[
https://issues.apache.org/jira/browse/IGNITE-17007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-17007:
-
Attachment: _Integration_Tests_Module_Table_2895.log
> TxAbstractTest#testBalance is flaky
> ---
>
> Key: IGNITE-17007
> URL: https://issues.apache.org/jira/browse/IGNITE-17007
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Module_Table_2895.log
>
>
> Implementations of {{TxAbstractTest#testBalance}} sometimes fail when running
> on TeamCity:
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable?mode=builds#all-projects
> I wasn't able to reproduce these failures locally, so this might be a
> TC-specific issue.
> Example error log:
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable/6575460
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17007) TxAbstractTest#testBalance is flaky
[
https://issues.apache.org/jira/browse/IGNITE-17007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-17007:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> TxAbstractTest#testBalance is flaky
> ---
>
> Key: IGNITE-17007
> URL: https://issues.apache.org/jira/browse/IGNITE-17007
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Priority: Major
>
> Implementations of {{TxAbstractTest#testBalance}} sometimes fail when running
> on TeamCity:
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable?mode=builds#all-projects
> I wasn't able to reproduce these failures locally, so this might be a
> TC-specific issue.
> Example error log:
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable/6575460
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17007) TxAbstractTest#testBalance is flaky
Aleksandr Polovtcev created IGNITE-17007:
Summary: TxAbstractTest#testBalance is flaky
Key: IGNITE-17007
URL: https://issues.apache.org/jira/browse/IGNITE-17007
Project: Ignite
Issue Type: Bug
Reporter: Aleksandr Polovtcev
Implementations of {{TxAbstractTest#testBalance}} sometimes fail when running
on TeamCity:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable?mode=builds#all-projects
I wasn't able to reproduce these failures locally, so this might be a
TC-specific issue.
Example error log:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleTable/6575460
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17006) Add protection against arbitrary page memory links in LinkRowId
[ https://issues.apache.org/jira/browse/IGNITE-17006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-17006: --- Epic Link: IGNITE-16923 > Add protection against arbitrary page memory links in LinkRowId > --- > > Key: IGNITE-17006 > URL: https://issues.apache.org/jira/browse/IGNITE-17006 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > It's theoretically possible to pass an arbitrary page memory link (via > LinkRowId) which might cause troubles: > # If pageId exceeds page memory limit, the JVM might crash > # If the page with this pageId was never initialized, an attempt to read > will fail with an internal assertion (because lock state will be 0) > A possibility for item ID to be invalid is already handled. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17006) Add protection against arbitrary page memory links in LinkRowId
Roman Puchkovskiy created IGNITE-17006: -- Summary: Add protection against arbitrary page memory links in LinkRowId Key: IGNITE-17006 URL: https://issues.apache.org/jira/browse/IGNITE-17006 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-alpha5 It's theoretically possible to pass an arbitrary page memory link (via LinkRowId) which might cause troubles: # If pageId exceeds page memory limit, the JVM might crash # If the page with this pageId was never initialized, an attempt to read will fail with an internal assertion (because lock state will be 0) A possibility for item ID to be invalid is already handled. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17004) Add documentation of the catching up process in JRaft
[ https://issues.apache.org/jira/browse/IGNITE-17004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538884#comment-17538884 ] Alexander Lapin commented on IGNITE-17004: -- [~maliev] LGTM > Add documentation of the catching up process in JRaft > - > > Key: IGNITE-17004 > URL: https://issues.apache.org/jira/browse/IGNITE-17004 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > > When we worked on IGNITE-16801, it was important to understand the reasons > why node's catching up process could fail, so we decided to document catching > up process -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16920) Calcite Engine. COUNT() lacks trivial optimization.
[ https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-16920: -- Summary: Calcite Engine. COUNT() lacks trivial optimization. (was: Calcite Engine. COUNT() lacks optimization.) > Calcite Engine. COUNT() lacks trivial optimization. > --- > > Key: IGNITE-16920 > URL: https://issues.apache.org/jira/browse/IGNITE-16920 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.13 >Reporter: YuJue Li >Assignee: Vladimir Steshin >Priority: Major > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Attachments: PI_COM_DAY.sql, example-calcite.xml, > image-2022-05-01-13-35-59-275.png > > > !image-2022-05-01-13-35-59-275.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16124) deleteAllById has wrong signature
[
https://issues.apache.org/jira/browse/IGNITE-16124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538863#comment-17538863
]
Maxim Muzafarov commented on IGNITE-16124:
--
[~YozFr]
Please, check the following:
https://search.maven.org/artifact/org.apache.ignite/ignite-spring-data-ext/2.0.0/jar
https://dist.apache.org/repos/dist/release/ignite/ignite-extensions/ignite-spring-data-ext/2.0.0/
> deleteAllById has wrong signature
> -
>
> Key: IGNITE-16124
> URL: https://issues.apache.org/jira/browse/IGNITE-16124
> Project: Ignite
> Issue Type: Bug
> Components: extensions
>Reporter: Michael Reiche
>Assignee: Andrey Belyaev
>Priority: Major
>
> java: name clash: deleteAllById(java.lang.Iterable) in
> org.apache.ignite.springdata20.repository.IgniteRepository and
> deleteAllById(java.lang.Iterable) in
> org.springframework.data.repository.CrudRepository have the same erasure, yet
> neither overrides the other
>
> 2.6.0-RC1
> 2.9.1
>
>
>
> org.apache.ignite
> ignite-spring-data_2.0
> ${ignite.version}
>
>
> org.apache.ignite
> ignite-core
> ${ignite.version}
>
>
> org.apache.ignite
> ignite-indexing
> ${ignite.version}
>
>
> org.apache.ignite
> ignite-spring
> ${ignite.version}
>
>
> org.springframework.data
> spring-data-commons
> ${spring.data.version}
>
>
> If ignite-spring-data is used instead of ingite-spring-data_2.0, the method
> deleteAll is flagged
> java: name clash: deleteAll(java.lang.Iterable com.example.ignite.EmployeeDTO>) in
> org.springframework.data.repository.CrudRepository and
> deleteAll(java.lang.Iterable) in
> org.apache.ignite.springdata.repository.IgniteRepository have the same
> erasure, yet neither overrides the other
> And 2.2-ext gives the following:
> org.apache.ignite
> ignite-spring-data-2.2-ext
> 1.0.0
> java: name clash: deleteAllById(java.lang.Iterable) in
> org.apache.ignite.springdata22.repository.IgniteRepository and
> deleteAllById(java.lang.Iterable) in
> org.springframework.data.repository.CrudRepository have the same erasure, yet
> neither overrides the other
> package com.example.ignite;
> import org.apache.ignite.springdata.repository.IgniteRepository;
> import org.apache.ignite.springdata.repository.config.RepositoryConfig;
> @RepositoryConfig(cacheName = "myCache")
> public interface EmployeeRepository extends
> IgniteRepository
> { EmployeeDTO getEmployeeDTOById(ID id); }
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[ https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin reassigned IGNITE-16920: - Assignee: Vladimir Steshin > Calcite Engine. COUNT() lacks optimization. > --- > > Key: IGNITE-16920 > URL: https://issues.apache.org/jira/browse/IGNITE-16920 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.13 >Reporter: YuJue Li >Assignee: Vladimir Steshin >Priority: Major > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Attachments: PI_COM_DAY.sql, example-calcite.xml, > image-2022-05-01-13-35-59-275.png > > > !image-2022-05-01-13-35-59-275.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[
https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538856#comment-17538856
]
Vladimir Steshin edited comment on IGNITE-16920 at 5/18/22 2:02 PM:
Calcite doesn't use index like H2. There is IGNITE-13919 already.
*H2:*
{code:java}
H2TreeIndex::getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
And sums the counts from the index segments.
*Calcite:*
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
was (Author: vladsz83):
Calcite doesn't use index, counting records in metapages like H2. There is
IGNITE-13919 already.
What H2 does:
{code:java}
H2TreeIndex::getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
And sums the counts from the index segments.
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
> Calcite Engine. COUNT() lacks optimization.
> ---
>
> Key: IGNITE-16920
> URL: https://issues.apache.org/jira/browse/IGNITE-16920
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.13
>Reporter: YuJue Li
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.14
>
> Attachments: PI_COM_DAY.sql, example-calcite.xml,
> image-2022-05-01-13-35-59-275.png
>
>
> !image-2022-05-01-13-35-59-275.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[
https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538856#comment-17538856
]
Vladimir Steshin edited comment on IGNITE-16920 at 5/18/22 2:01 PM:
Calcite doesn't use index, counting records in metapages like H2. There is
IGNITE-13919 already.
What H2 does:
{code:java}
H2TreeIndex::getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
And sums the counts from the index segments.
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
was (Author: vladsz83):
Calcite doesn't use index, counting records in metapages like H2. There is
IGNITE-13919 already.
What H2 does:
{code:java}
H2TreeIndex::getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
> Calcite Engine. COUNT() lacks optimization.
> ---
>
> Key: IGNITE-16920
> URL: https://issues.apache.org/jira/browse/IGNITE-16920
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.13
>Reporter: YuJue Li
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.14
>
> Attachments: PI_COM_DAY.sql, example-calcite.xml,
> image-2022-05-01-13-35-59-275.png
>
>
> !image-2022-05-01-13-35-59-275.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[
https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538856#comment-17538856
]
Vladimir Steshin edited comment on IGNITE-16920 at 5/18/22 2:00 PM:
Calcite doesn't use index, counting records in metapages like H2. There is
IGNITE-13919 already.
What H2 does:
{code:java}
H2TreeIndex::getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
was (Author: vladsz83):
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex::getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
> Calcite Engine. COUNT() lacks optimization.
> ---
>
> Key: IGNITE-16920
> URL: https://issues.apache.org/jira/browse/IGNITE-16920
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.13
>Reporter: YuJue Li
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.14
>
> Attachments: PI_COM_DAY.sql, example-calcite.xml,
> image-2022-05-01-13-35-59-275.png
>
>
> !image-2022-05-01-13-35-59-275.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[
https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538856#comment-17538856
]
Vladimir Steshin edited comment on IGNITE-16920 at 5/18/22 1:58 PM:
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex::getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
was (Author: vladsz83):
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex:: getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
> Calcite Engine. COUNT() lacks optimization.
> ---
>
> Key: IGNITE-16920
> URL: https://issues.apache.org/jira/browse/IGNITE-16920
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.13
>Reporter: YuJue Li
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.14
>
> Attachments: PI_COM_DAY.sql, example-calcite.xml,
> image-2022-05-01-13-35-59-275.png
>
>
> !image-2022-05-01-13-35-59-275.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[
https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538856#comment-17538856
]
Vladimir Steshin edited comment on IGNITE-16920 at 5/18/22 1:57 PM:
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex:: getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
was (Author: vladsz83):
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex:: getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
> Calcite Engine. COUNT() lacks optimization.
> ---
>
> Key: IGNITE-16920
> URL: https://issues.apache.org/jira/browse/IGNITE-16920
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.13
>Reporter: YuJue Li
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.14
>
> Attachments: PI_COM_DAY.sql, example-calcite.xml,
> image-2022-05-01-13-35-59-275.png
>
>
> !image-2022-05-01-13-35-59-275.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[
https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538856#comment-17538856
]
Vladimir Steshin edited comment on IGNITE-16920 at 5/18/22 1:57 PM:
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex:: getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
was (Author: vladsz83):
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex:: getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
{code:java}
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
{code}
> Calcite Engine. COUNT() lacks optimization.
> ---
>
> Key: IGNITE-16920
> URL: https://issues.apache.org/jira/browse/IGNITE-16920
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.13
>Reporter: YuJue Li
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.14
>
> Attachments: PI_COM_DAY.sql, example-calcite.xml,
> image-2022-05-01-13-35-59-275.png
>
>
> !image-2022-05-01-13-35-59-275.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[
https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538856#comment-17538856
]
Vladimir Steshin commented on IGNITE-16920:
---
Calcite doesn't use index, counting records in metapages like H2.
What H2 does:
{code:java}
H2TreeIndex:: getRowCount()
public long InlineIndexImpl::count(int segment, IndexQueryContext qryCtx)
throws IgniteCheckedException {
return segments[segment].size(filterClosure(qryCtx));
}
metaPage -> records number
{code}
Calcite:
IgniteReduceHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteExchange(distribution=[single])
IgniteMapHashAggregate(group=[{}], COUNT(*)=[COUNT()])
IgniteTableScan(table=[[PUBLIC, PI_COM_DAY]])
> Calcite Engine. COUNT() lacks optimization.
> ---
>
> Key: IGNITE-16920
> URL: https://issues.apache.org/jira/browse/IGNITE-16920
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.13
>Reporter: YuJue Li
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.14
>
> Attachments: PI_COM_DAY.sql, example-calcite.xml,
> image-2022-05-01-13-35-59-275.png
>
>
> !image-2022-05-01-13-35-59-275.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[ https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-16920: -- Priority: Major (was: Critical) > Calcite Engine. COUNT() lacks optimization. > --- > > Key: IGNITE-16920 > URL: https://issues.apache.org/jira/browse/IGNITE-16920 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.13 >Reporter: YuJue Li >Priority: Major > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Attachments: PI_COM_DAY.sql, example-calcite.xml, > image-2022-05-01-13-35-59-275.png > > > !image-2022-05-01-13-35-59-275.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16920) Calcite Engine. COUNT() lacks optimization.
[ https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-16920: -- Summary: Calcite Engine. COUNT() lacks optimization. (was: The performance of the COUNT function in the Calcite based SQL Engine is significantly lower than that in the H2 based SQL Engine) > Calcite Engine. COUNT() lacks optimization. > --- > > Key: IGNITE-16920 > URL: https://issues.apache.org/jira/browse/IGNITE-16920 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.13 >Reporter: YuJue Li >Priority: Critical > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Attachments: PI_COM_DAY.sql, example-calcite.xml, > image-2022-05-01-13-35-59-275.png > > > !image-2022-05-01-13-35-59-275.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-16992) Partial node in ItIgniteNodeRestartTest should join the CMG
[
https://issues.apache.org/jira/browse/IGNITE-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev resolved IGNITE-16992.
--
Resolution: Invalid
> Partial node in ItIgniteNodeRestartTest should join the CMG
> ---
>
> Key: IGNITE-16992
> URL: https://issues.apache.org/jira/browse/IGNITE-16992
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
>
> {{ItIgniteNodeRestartTest#testMetastorageStop}} test fails if the node,
> started in {{startPartialNode}}, executes {{cmgManager.joinFuture()}}. For
> some reason, it stops receiving Meta Storage revision updates after the Meta
> Storage node is restarted.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17005) Implement metrics for a snapshot create operation
Amelchev Nikita created IGNITE-17005: Summary: Implement metrics for a snapshot create operation Key: IGNITE-17005 URL: https://issues.apache.org/jira/browse/IGNITE-17005 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Snapshot create operation can take a long time, we must be able to track its progress using metrics. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17004) Add documentation of the catching up process in JRaft
Mirza Aliev created IGNITE-17004: Summary: Add documentation of the catching up process in JRaft Key: IGNITE-17004 URL: https://issues.apache.org/jira/browse/IGNITE-17004 Project: Ignite Issue Type: Task Reporter: Mirza Aliev Assignee: Mirza Aliev When we worked on IGNITE-16801, it was important to understand the reasons why node's catching up process could fail, so we decided to document catching up process -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16119) Caclite engine. Refactor IgniteBuiltInMethod and IgniteMethod classes
[
https://issues.apache.org/jira/browse/IGNITE-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-16119:
Labels: calcite (was: calcite calcite3-required)
> Caclite engine. Refactor IgniteBuiltInMethod and IgniteMethod classes
> -
>
> Key: IGNITE-16119
> URL: https://issues.apache.org/jira/browse/IGNITE-16119
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Looks like {{IgniteBuiltInMethod}} and {{IgniteMethod}} classes have the same
> purpose. We should choose and leave one of them.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17001) Useless ERROR in server logs like Duplicate key during INSERT
[
https://issues.apache.org/jira/browse/IGNITE-17001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-17001:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Useless ERROR in server logs like Duplicate key during INSERT
> -
>
> Key: IGNITE-17001
> URL: https://issues.apache.org/jira/browse/IGNITE-17001
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During execute SQL we have exceptions which looks like do not require any
> actions from administrator. So it’s looks like we don’t need this one in
> logs. As example:
> {code}
> [2022-03-22T14:16:09,423][ERROR][client-connector-#187%nebula-node%][JdbcRequestHandler]
> Failed to execute SQL query [reqId=5411, req=JdbcQueryExecuteRequest
> [schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=I
> NSERT INTO ref_bid_prd_crew_dtl VALUES
> ('201904','U174148','Initload','2019-07-03 07:48:10',NULL,NULL),
> args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=true,
> partResReq=false, explicitTimeout=false, sup
> er=JdbcRequest [type=2, reqId=5411]]]
> org.apache.ignite.transactions.TransactionDuplicateKeyException: Duplicate
> key during INSERT
> [key=SQL_PUBLIC_REF_BID_PRD_CREW_DTL_e46b9a63d00b9bb81931d447fdf13491_KEY
> [idHash=1167531818, hash=2095161702, BID_PRD=
> 201904, FILE_NBR=U174148]]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.dmlDoInsert(DmlUtils.java:206)
> ~[ignite-indexing-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.processSelectResult(DmlUtils.java:169)
> ~[ignite-indexing-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateNonTransactional(IgniteH2Indexing.java:3199)
> ~[ignite-indexing-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdate(IgniteH2Indexing.java:3043)
> ~[ignite-indexing-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateDistributed(IgniteH2Indexing.java:2970)
> ~[ignite-indexing-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeDml(IgniteH2Indexing.java:1319)
> ~[ignite-indexing-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1240)
> ~[ignite-indexing-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:2887)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:2883)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:35)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:3435)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$3(GridQueryProcessor.java:2903)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2941)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2877)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2835)
> ~[ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:656)
> [ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:321)
> [ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:258)
> [ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:210)
> [ignite-core-8.8.16.jar:8.8.16]
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:58)
> [ignite-core-8.8.16.jar:8.8.16]
> at
>
[jira] [Created] (IGNITE-17003) SqlDataTypesCoverageTests.testDecimalDataType failes flaky
Taras Ledkov created IGNITE-17003:
-
Summary: SqlDataTypesCoverageTests.testDecimalDataType failes flaky
Key: IGNITE-17003
URL: https://issues.apache.org/jira/browse/IGNITE-17003
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Taras Ledkov
Assignee: Taras Ledkov
Fix For: 2.14
There is a problem with this critical test - when start full test class there
is high posibuility to get error on first tests. By default first test is
testDecimalDataType. Every time I get different errors - it makes a suggestion
about side effect of started cluster. Test doesn’t fail starting separately.
Case of fail: [atomicityMode=ATOMIC, cacheMode=PARTITIONED, ttlFactory=null,
backups=2, evictionFactory=null, onheapCacheEnabled=false,
writeSyncMode=FULL_ASYNC, persistenceEnabled=false]
*Root cause:*
The test is invalid for {{FULL_ASYNC }}mode.
The sequential execute
UPDATE …
SELECT …
cannot guarantee visibility UPDATE changes for the SELECT query when FULL_ASYNC
mode is used.
*Possible fixes:*
There can be two ways:
don’t use FULL_ASYNC mode at the test.
wait for UPDATE changes is applied.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17003) SqlDataTypesCoverageTests.testDecimalDataType failes flaky
[
https://issues.apache.org/jira/browse/IGNITE-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-17003:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> SqlDataTypesCoverageTests.testDecimalDataType failes flaky
> --
>
> Key: IGNITE-17003
> URL: https://issues.apache.org/jira/browse/IGNITE-17003
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.14
>
>
> There is a problem with this critical test - when start full test class there
> is high posibuility to get error on first tests. By default first test is
> testDecimalDataType. Every time I get different errors - it makes a
> suggestion about side effect of started cluster. Test doesn’t fail starting
> separately.
> Case of fail: [atomicityMode=ATOMIC, cacheMode=PARTITIONED, ttlFactory=null,
> backups=2, evictionFactory=null, onheapCacheEnabled=false,
> writeSyncMode=FULL_ASYNC, persistenceEnabled=false]
> *Root cause:*
> The test is invalid for {{FULL_ASYNC }}mode.
> The sequential execute
> UPDATE …
> SELECT …
> cannot guarantee visibility UPDATE changes for the SELECT query when
> FULL_ASYNC mode is used.
> *Possible fixes:*
> There can be two ways:
> don’t use FULL_ASYNC mode at the test.
> wait for UPDATE changes is applied.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17002) Indexes rebuild in Maintenance Mode
[ https://issues.apache.org/jira/browse/IGNITE-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-17002: - Description: Now Ignite supports entering Maintenance Mode after index corruption automatically - this was implemented in linked issue. But there are use-cases when user needs to request rebuilding specific indexes in MM, so we need to provide a control.sh API to make these requests. Also for better integration with monitoring tools it is nice to provide an API to check status of rebuilding task and print message to logs when each task is finished and all tasks are finished. was: Now Ignite supports entering Maintenance Mode after index corruption automatically. But there are use-cases when user needs to request rebuilding specific indexes in MM, so we need to provide a control.sh API to make these requests. Also for better integration with monitoring tools it is nice to provide an API to check status of rebuilding task and print message to logs when each task is finished and all tasks are finished. > Indexes rebuild in Maintenance Mode > --- > > Key: IGNITE-17002 > URL: https://issues.apache.org/jira/browse/IGNITE-17002 > Project: Ignite > Issue Type: Improvement > Components: control.sh, persistence >Reporter: Sergey Chugunov >Priority: Major > Fix For: 2.14 > > > Now Ignite supports entering Maintenance Mode after index corruption > automatically - this was implemented in linked issue. > But there are use-cases when user needs to request rebuilding specific > indexes in MM, so we need to provide a control.sh API to make these requests. > Also for better integration with monitoring tools it is nice to provide an > API to check status of rebuilding task and print message to logs when each > task is finished and all tasks are finished. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17002) Indexes rebuild in Maintenance Mode
Sergey Chugunov created IGNITE-17002: Summary: Indexes rebuild in Maintenance Mode Key: IGNITE-17002 URL: https://issues.apache.org/jira/browse/IGNITE-17002 Project: Ignite Issue Type: Improvement Components: control.sh, persistence Reporter: Sergey Chugunov Fix For: 2.14 Now Ignite supports entering Maintenance Mode after index corruption automatically. But there are use-cases when user needs to request rebuilding specific indexes in MM, so we need to provide a control.sh API to make these requests. Also for better integration with monitoring tools it is nice to provide an API to check status of rebuilding task and print message to logs when each task is finished and all tasks are finished. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538763#comment-17538763
]
Norbert Löffler commented on IGNITE-16136:
--
Dear development experts, can it be expected that this problem will be
addressed in the next few days or weeks? We would very much appreciate a
solution. Sincerely Norbert
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(Ljava/util/concurrent/ConcurrentMap;ILjava/lang/ClassLoader;Lorg/apache/ignite/marshaller/MarshallerContext;Lorg/apache/ignite/internal/marshaller/optimized/OptimizedMarshallerIdMapper;)Lorg/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor;
> (OptimizedMarshallerUtils.java:264)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:341)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:198)
> at
> java.io.ObjectInputStream.readObject(Ljava/lang/Class;)Ljava/lang/Object;
> (ObjectInputStream.java:484)
> at
[jira] [Resolved] (IGNITE-15942) Add support for h2 1.4.200 version to Ignite and Spring Ignite Data packages
[ https://issues.apache.org/jira/browse/IGNITE-15942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li resolved IGNITE-15942. --- Resolution: Won't Fix > Add support for h2 1.4.200 version to Ignite and Spring Ignite Data packages > > > Key: IGNITE-15942 > URL: https://issues.apache.org/jira/browse/IGNITE-15942 > Project: Ignite > Issue Type: Improvement >Reporter: Julius Kabugu >Priority: Major > > Today, when we create Ignite thick clients, the ignite client packages and > Spring Ignite Data require h2 database version 1.4.197. Upgrading to 1.4.200 > breaks the clients. However, h2 1.4.197 has been flagged by security scans > due to a number of vulnerabilities. > The request is to update Ignite client packages to use H2 database version > 1.4.200. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-15942) Add support for h2 1.4.200 version to Ignite and Spring Ignite Data packages
[ https://issues.apache.org/jira/browse/IGNITE-15942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538727#comment-17538727 ] YuJue Li commented on IGNITE-15942: --- [https://github.com/h2database/h2database/pull/2227] > Add support for h2 1.4.200 version to Ignite and Spring Ignite Data packages > > > Key: IGNITE-15942 > URL: https://issues.apache.org/jira/browse/IGNITE-15942 > Project: Ignite > Issue Type: Improvement >Reporter: Julius Kabugu >Priority: Major > > Today, when we create Ignite thick clients, the ignite client packages and > Spring Ignite Data require h2 database version 1.4.197. Upgrading to 1.4.200 > breaks the clients. However, h2 1.4.197 has been flagged by security scans > due to a number of vulnerabilities. > The request is to update Ignite client packages to use H2 database version > 1.4.200. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-15241) Ignite H2 Security Vulnerabilities
[
https://issues.apache.org/jira/browse/IGNITE-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YuJue Li resolved IGNITE-15241.
---
Resolution: Won't Fix
> Ignite H2 Security Vulnerabilities
> --
>
> Key: IGNITE-15241
> URL: https://issues.apache.org/jira/browse/IGNITE-15241
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
> Labels: cggg
> Original Estimate: 80h
> Remaining Estimate: 80h
>
> Upgrade H2 dependency of the ignite-indexing module to the latest version
> 1.4.200.
> Apache Ignite SQL (module {{ignite-indexing}}) depends on H2 database version
> 1.4.197, which has these two [security
> vulnerabilities|https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/year-2018/H2database-H2.html]
> [CVE-2018-14335|https://www.cvedetails.com/cve/CVE-2018-14335/] is regarded
> as a critical vulnerability by our analyzer (Black Duck SCA) and makes it
> impossible to use Ignite SQL due to security policies. We realize this
> vulnerability is probably not even applicable to the H2 in Ignite since there
> is no H2 database or H2 backups in Ignite. Still the security policies are
> very formal and do not allow that anyway.
> We believe there are lots of other enterprises having the same issue. For
> example, there is another issue IGNITE-14381 referencing the same problem.
> The latest H2 1.4.200 has no vulnerabilities.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-15241) Ignite H2 Security Vulnerabilities
[
https://issues.apache.org/jira/browse/IGNITE-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538725#comment-17538725
]
YuJue Li commented on IGNITE-15241:
---
[https://github.com/h2database/h2database/pull/2227]
> Ignite H2 Security Vulnerabilities
> --
>
> Key: IGNITE-15241
> URL: https://issues.apache.org/jira/browse/IGNITE-15241
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
> Labels: cggg
> Original Estimate: 80h
> Remaining Estimate: 80h
>
> Upgrade H2 dependency of the ignite-indexing module to the latest version
> 1.4.200.
> Apache Ignite SQL (module {{ignite-indexing}}) depends on H2 database version
> 1.4.197, which has these two [security
> vulnerabilities|https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/year-2018/H2database-H2.html]
> [CVE-2018-14335|https://www.cvedetails.com/cve/CVE-2018-14335/] is regarded
> as a critical vulnerability by our analyzer (Black Duck SCA) and makes it
> impossible to use Ignite SQL due to security policies. We realize this
> vulnerability is probably not even applicable to the H2 in Ignite since there
> is no H2 database or H2 backups in Ignite. Still the security policies are
> very formal and do not allow that anyway.
> We believe there are lots of other enterprises having the same issue. For
> example, there is another issue IGNITE-14381 referencing the same problem.
> The latest H2 1.4.200 has no vulnerabilities.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17001) Useless ERROR in server logs like Duplicate key during INSERT
Taras Ledkov created IGNITE-17001:
-
Summary: Useless ERROR in server logs like Duplicate key during
INSERT
Key: IGNITE-17001
URL: https://issues.apache.org/jira/browse/IGNITE-17001
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Taras Ledkov
Assignee: Taras Ledkov
Fix For: 2.14
During execute SQL we have exceptions which looks like do not require any
actions from administrator. So it’s looks like we don’t need this one in logs.
As example:
{code}
[2022-03-22T14:16:09,423][ERROR][client-connector-#187%nebula-node%][JdbcRequestHandler]
Failed to execute SQL query [reqId=5411, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=I
NSERT INTO ref_bid_prd_crew_dtl VALUES
('201904','U174148','Initload','2019-07-03 07:48:10',NULL,NULL), args=Object[]
[], stmtType=ANY_STATEMENT_TYPE, autoCommit=true, partResReq=false,
explicitTimeout=false, sup
er=JdbcRequest [type=2, reqId=5411]]]
org.apache.ignite.transactions.TransactionDuplicateKeyException: Duplicate key
during INSERT
[key=SQL_PUBLIC_REF_BID_PRD_CREW_DTL_e46b9a63d00b9bb81931d447fdf13491_KEY
[idHash=1167531818, hash=2095161702, BID_PRD=
201904, FILE_NBR=U174148]]
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.dmlDoInsert(DmlUtils.java:206)
~[ignite-indexing-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.processSelectResult(DmlUtils.java:169)
~[ignite-indexing-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateNonTransactional(IgniteH2Indexing.java:3199)
~[ignite-indexing-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdate(IgniteH2Indexing.java:3043)
~[ignite-indexing-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateDistributed(IgniteH2Indexing.java:2970)
~[ignite-indexing-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeDml(IgniteH2Indexing.java:1319)
~[ignite-indexing-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1240)
~[ignite-indexing-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:2887)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:2883)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:35)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:3435)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$3(GridQueryProcessor.java:2903)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2941)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2877)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2835)
~[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:656)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:321)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:258)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:210)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:58)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:278)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:135)
[ignite-core-8.8.16.jar:8.8.16]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
[ignite-core-8.8.16.jar:8.8.16]
[jira] [Commented] (IGNITE-17000) The h2database version 1.4.197 has a security vulnerability.
[ https://issues.apache.org/jira/browse/IGNITE-17000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538719#comment-17538719 ] YuJue Li commented on IGNITE-17000: --- https://github.com/h2database/h2database/pull/2227 > The h2database version 1.4.197 has a security vulnerability. > > > Key: IGNITE-17000 > URL: https://issues.apache.org/jira/browse/IGNITE-17000 > Project: Ignite > Issue Type: Bug >Reporter: biandeqiang >Priority: Major > > The h2database version 1.4.197 has a security vulnerability. > The suggested content that upgrade the h2database to 1.4.200 for ignite. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17000) The h2database version 1.4.197 has a security vulnerability.
[ https://issues.apache.org/jira/browse/IGNITE-17000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li resolved IGNITE-17000. --- Resolution: Won't Fix > The h2database version 1.4.197 has a security vulnerability. > > > Key: IGNITE-17000 > URL: https://issues.apache.org/jira/browse/IGNITE-17000 > Project: Ignite > Issue Type: Bug >Reporter: biandeqiang >Priority: Major > > The h2database version 1.4.197 has a security vulnerability. > The suggested content that upgrade the h2database to 1.4.200 for ignite. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16542) Ignite h2 security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538718#comment-17538718 ] YuJue Li commented on IGNITE-16542: --- https://github.com/h2database/h2database/pull/2227 > Ignite h2 security vulnerabilities > -- > > Key: IGNITE-16542 > URL: https://issues.apache.org/jira/browse/IGNITE-16542 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.12 >Reporter: Pratiksha P >Priority: Major > > I face below vulnaribilities while using ignite 2.12.0 or 2.11.0 version > # CVE-2018-10054 > # CVE-2018-14335 > # CVE-2022-23221 > # CVE-2021-42392 > # CVE-2021-23463 > Is there is any solution available for above issues. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-16542) Ignite h2 security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li resolved IGNITE-16542. --- Resolution: Won't Fix > Ignite h2 security vulnerabilities > -- > > Key: IGNITE-16542 > URL: https://issues.apache.org/jira/browse/IGNITE-16542 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.12 >Reporter: Pratiksha P >Priority: Major > > I face below vulnaribilities while using ignite 2.12.0 or 2.11.0 version > # CVE-2018-10054 > # CVE-2018-14335 > # CVE-2022-23221 > # CVE-2021-42392 > # CVE-2021-23463 > Is there is any solution available for above issues. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-16384) H2 database used in Ignite has high security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li resolved IGNITE-16384. --- Resolution: Won't Fix > H2 database used in Ignite has high security vulnerabilities > > > Key: IGNITE-16384 > URL: https://issues.apache.org/jira/browse/IGNITE-16384 > Project: Ignite > Issue Type: Bug > Components: h2-limitation >Affects Versions: 2.11 >Reporter: Anitha Sornaraja >Priority: Critical > > The H2 database used in Apache Ignite has several high security > vulnerabilities. Our security scan is showing the following vulnerabilities: > CVE-2021-42392 > CVE-2021-23463 > CVE-2022-23221 > > Please upgrade the version of H2 database used to 2.0.206. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16384) H2 database used in Ignite has high security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538717#comment-17538717 ] YuJue Li commented on IGNITE-16384: --- https://github.com/h2database/h2database/pull/2227 > H2 database used in Ignite has high security vulnerabilities > > > Key: IGNITE-16384 > URL: https://issues.apache.org/jira/browse/IGNITE-16384 > Project: Ignite > Issue Type: Bug > Components: h2-limitation >Affects Versions: 2.11 >Reporter: Anitha Sornaraja >Priority: Critical > > The H2 database used in Apache Ignite has several high security > vulnerabilities. Our security scan is showing the following vulnerabilities: > CVE-2021-42392 > CVE-2021-23463 > CVE-2022-23221 > > Please upgrade the version of H2 database used to 2.0.206. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16905) Sql. ClassCastException when deserialising TIMESTAMP literal
[
https://issues.apache.org/jira/browse/IGNITE-16905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538707#comment-17538707
]
Alexander Lapin commented on IGNITE-16905:
--
[~korlov] test
> Sql. ClassCastException when deserialising TIMESTAMP literal
>
>
> Key: IGNITE-16905
> URL: https://issues.apache.org/jira/browse/IGNITE-16905
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: calcite, ignite-3
>
> The problem appears to be caused by an inconsistency of RelReader and
> RexBuilder: RelReader diserializes every integer value as a value of type
> Integer, but the RexBuilder assumes that for TIMESTAMP literal a value of
> type Long will be passed, and make the explicit cast:
> {code:java}
> // RexBuilder#clean(Object, RelDataType)
> case TIMESTAMP:
> if (o instanceof TimestampString) {
> return o;
> } else if (o instanceof Calendar) {
> if (!((Calendar) o).getTimeZone().equals(DateTimeUtils.UTC_ZONE)) {
> throw new AssertionError();
> }
> return TimestampString.fromCalendarFields((Calendar) o);
> } else {
> return TimestampString.fromMillisSinceEpoch((Long) o);
> } {code}
>
> Here is a stack trace:
> {noformat}
> Caused by: java.lang.ClassCastException: class java.lang.Integer cannot be
> cast to class java.lang.Long (java.lang.Integer and java.lang.Long are in
> module java.base of loader 'bootstrap')
> at org.apache.calcite.rex.RexBuilder.clean(RexBuilder.java:1780)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1558)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1520)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJson.toRex(RelJson.java:759)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJsonReader$RelInputImpl.getTuple(RelJsonReader.java:367)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJsonReader$RelInputImpl.getTuples(RelJsonReader.java:347)
> ... 24 more {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] (IGNITE-16905) Sql. ClassCastException when deserialising TIMESTAMP literal
[ https://issues.apache.org/jira/browse/IGNITE-16905 ]
Alexander Lapin deleted comment on IGNITE-16905:
--
was (Author: alapin):
[~korlov] test
> Sql. ClassCastException when deserialising TIMESTAMP literal
>
>
> Key: IGNITE-16905
> URL: https://issues.apache.org/jira/browse/IGNITE-16905
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: calcite, ignite-3
>
> The problem appears to be caused by an inconsistency of RelReader and
> RexBuilder: RelReader diserializes every integer value as a value of type
> Integer, but the RexBuilder assumes that for TIMESTAMP literal a value of
> type Long will be passed, and make the explicit cast:
> {code:java}
> // RexBuilder#clean(Object, RelDataType)
> case TIMESTAMP:
> if (o instanceof TimestampString) {
> return o;
> } else if (o instanceof Calendar) {
> if (!((Calendar) o).getTimeZone().equals(DateTimeUtils.UTC_ZONE)) {
> throw new AssertionError();
> }
> return TimestampString.fromCalendarFields((Calendar) o);
> } else {
> return TimestampString.fromMillisSinceEpoch((Long) o);
> } {code}
>
> Here is a stack trace:
> {noformat}
> Caused by: java.lang.ClassCastException: class java.lang.Integer cannot be
> cast to class java.lang.Long (java.lang.Integer and java.lang.Long are in
> module java.base of loader 'bootstrap')
> at org.apache.calcite.rex.RexBuilder.clean(RexBuilder.java:1780)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1558)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1520)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJson.toRex(RelJson.java:759)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJsonReader$RelInputImpl.getTuple(RelJsonReader.java:367)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJsonReader$RelInputImpl.getTuples(RelJsonReader.java:347)
> ... 24 more {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16999) Sql. Refactor IgniteBuiltInMethod and IgniteMethod classes.
[ https://issues.apache.org/jira/browse/IGNITE-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16999: Labels: calcite ignite-3 (was: calcite calcite3-required ignite-3) > Sql. Refactor IgniteBuiltInMethod and IgniteMethod classes. > --- > > Key: IGNITE-16999 > URL: https://issues.apache.org/jira/browse/IGNITE-16999 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: calcite, ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Adopt https://issues.apache.org/jira/browse/IGNITE-16119 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17000) The h2database version 1.4.197 has a security vulnerability.
biandeqiang created IGNITE-17000: Summary: The h2database version 1.4.197 has a security vulnerability. Key: IGNITE-17000 URL: https://issues.apache.org/jira/browse/IGNITE-17000 Project: Ignite Issue Type: Bug Reporter: biandeqiang The h2database version 1.4.197 has a security vulnerability. The suggested content that upgrade the h2database to 1.4.200 for ignite. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16988) [Native Persistence 3.0] Porting FileIO from 2.0
[ https://issues.apache.org/jira/browse/IGNITE-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16988: - Reviewer: Ivan Bessonov > [Native Persistence 3.0] Porting FileIO from 2.0 > > > Key: IGNITE-16988 > URL: https://issues.apache.org/jira/browse/IGNITE-16988 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > To continue porting the checkpoint from 2.0, we need to port the code > associated with > *org.apache.ignite.internal.processors.cache.persistence.file.FileIO* into a > separate module. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16998) [Native Persistence 3.0] Add configuration for checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16998: - Reviewer: Ivan Bessonov > [Native Persistence 3.0] Add configuration for checkpoint > - > > Key: IGNITE-16998 > URL: https://issues.apache.org/jira/browse/IGNITE-16998 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > We need to add a configuration for the checkpoint, you can look at all > *TODO*s in *org.apache.ignite.internal.pagememory.persistence.checkpoint*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16318) Empty binary object is incorrect written/read/modified
[
https://issues.apache.org/jira/browse/IGNITE-16318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538637#comment-17538637
]
Konstantin Orlov commented on IGNITE-16318:
---
[~tledkov-gridgain] , LGTM!
> Empty binary object is incorrect written/read/modified
> --
>
> Key: IGNITE-16318
> URL: https://issues.apache.org/jira/browse/IGNITE-16318
> Project: Ignite
> Issue Type: Bug
> Components: binary, cache
>Reporter: Andrey Belyaev
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Cache interceptor cause problem of missing binary scheme if sql insert
> contains only entry key fields and no one value field pass in query.
> There is exception happened if inside interceptor we try to make
> BinaryObjectBuilder from entry value BinaryObject (#toBuilder()) and then
> request builder for any field.
> Interceptor example:
> {code:java}
> new CacheInterceptorAdapter() {
> @Nullable
> @Override public BinaryObject onBeforePut(Cache.Entry BinaryObject> entry, BinaryObject newVal) {
> BinaryObjectBuilder newValBuilder = newVal.toBuilder();
> String bValue = newValBuilder.getField("B"); // Cannot find schema
> for object with compact footer
> // ...
> }
> } {code}
> It's a pretty serious error which currupt and shutdown grid.
> Code example:
> {code:java}
> LinkedHashMap fields = new LinkedHashMap<>();
> fields.put("A", "java.lang.String");
> fields.put("B", "java.lang.String");
> fields.put("C", "java.lang.String");
> Set keyFields = new LinkedHashSet<>();
> keyFields.add("A");
> CacheInterceptorAdapter cacheInterceptorAdapter = new
> CacheInterceptorAdapter() {
> @Nullable
> @Override public BinaryObject onBeforePut(Cache.Entry BinaryObject> entry, BinaryObject newVal) {
> BinaryObjectBuilder newValBuilder = newVal.toBuilder();
> String bValue = newValBuilder.getField("B"); // Cannot find schema
> for object with compact footer
> if (bValue == null || bValue.isEmpty()) {
> newValBuilder.setField("B", "Some value");
> }
> return newValBuilder.build();
> }
> };
> CacheConfiguration cacheConfiguration = new CacheConfiguration<>()
> .setName("TEST_CACHE")
> .setKeyConfiguration(new CacheKeyConfiguration()
> .setTypeName("TEST_CACHE_KEY")
> .setAffinityKeyFieldName("InternalId"))
> .setQueryEntities(Collections.singleton(new QueryEntity()
> .setTableName("TEST_CACHE")
> .setKeyType("TEST_CACHE_KEY")
> .setValueType("TEST_CACHE_VALUE")
> .setFields(fields)
> .setKeyFields(keyFields)))
> .setInterceptor(cacheInterceptorAdapter);
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration()
> .setCacheConfiguration(cacheConfiguration);
> try (Ignite ignite = Ignition.start(igniteConfiguration)) {
> IgniteCache testCache = ignite.getOrCreateCache("TEST_CACHE");
> // putSql
> testCache.query(new SqlFieldsQuery("INSERT INTO TEST_CACHE (A) VALUES
> ('1234')"));
> }{code}
> Exception:
> {code:java}
> [2022-01-18 13:12:32,727][ERROR][main][CacheObjectBinaryProcessorImpl] Timed
> out while waiting for schema update [typeId=1147851335, schemaId=0]
> [2022-01-18 13:12:32,730][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-838655627, pageIds=[844420635166307], msg=Runtime failure
> on search row: SearchRow [key=TEST_CACHE_KEY [idHash=100929741,
> hash=-639470899, A=123], hash=-639470899, cacheId=0
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-838655627, pageIds=[844420635166307],
> msg=Runtime failure on search row: SearchRow [key=TEST_CACHE_KEY
> [idHash=100929741, hash=-639470899, A=123], hash=-639470899, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6237)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1988)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1742)
> at
>
[jira] [Updated] (IGNITE-16986) Incorrect GridCacheManager#stop parameters
[ https://issues.apache.org/jira/browse/IGNITE-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-16986: Affects Version/s: 2.13 > Incorrect GridCacheManager#stop parameters > --- > > Key: IGNITE-16986 > URL: https://issues.apache.org/jira/browse/IGNITE-16986 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if > the whole cache group is going to be destroyed. However, this leads to > GridCacheManager#stop receiving incorrect destroy argument and potentially > not performing some tasks (for example, not dropping statistics). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16998) [Native Persistence 3.0] Add configuration for checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16998: - Summary: [Native Persistence 3.0] Add configuration for checkpoint (was: [Native Persistence 3.0] Add configuration for checkpoint.) > [Native Persistence 3.0] Add configuration for checkpoint > - > > Key: IGNITE-16998 > URL: https://issues.apache.org/jira/browse/IGNITE-16998 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > We need to add a configuration for the checkpoint, you can look at all > *TODO*s in *org.apache.ignite.internal.pagememory.persistence.checkpoint*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-14814) SQL statistics: drop statistics on cache destroy / DROP TABLE
[ https://issues.apache.org/jira/browse/IGNITE-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov resolved IGNITE-14814. - Fix Version/s: 2.14 Resolution: Fixed This issue was fixed by https://issues.apache.org/jira/browse/IGNITE-16986 > SQL statistics: drop statistics on cache destroy / DROP TABLE > - > > Key: IGNITE-14814 > URL: https://issues.apache.org/jira/browse/IGNITE-14814 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Alexander Belyak >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.14 > > > Now we cannot drop statistics automatically on cache destroy. > It depends on GridCacheProcessor#stopCache destroy flag. It is false when the > all caches from a group are stopped. In this case group -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-14814) SQL statistics: drop statistics on cache destroy / DROP TABLE
[ https://issues.apache.org/jira/browse/IGNITE-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov reassigned IGNITE-14814: --- Assignee: Semyon Danilov > SQL statistics: drop statistics on cache destroy / DROP TABLE > - > > Key: IGNITE-14814 > URL: https://issues.apache.org/jira/browse/IGNITE-14814 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Alexander Belyak >Assignee: Semyon Danilov >Priority: Major > > Now we cannot drop statistics automatically on cache destroy. > It depends on GridCacheProcessor#stopCache destroy flag. It is false when the > all caches from a group are stopped. In this case group -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-16999) Sql. Refactor IgniteBuiltInMethod and IgniteMethod classes.
Evgeny Stanilovsky created IGNITE-16999: --- Summary: Sql. Refactor IgniteBuiltInMethod and IgniteMethod classes. Key: IGNITE-16999 URL: https://issues.apache.org/jira/browse/IGNITE-16999 Project: Ignite Issue Type: Improvement Components: sql Reporter: Evgeny Stanilovsky Assignee: Evgeny Stanilovsky Adopt https://issues.apache.org/jira/browse/IGNITE-16119 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16999) Sql. Refactor IgniteBuiltInMethod and IgniteMethod classes.
[ https://issues.apache.org/jira/browse/IGNITE-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16999: Labels: calcite calcite3-required ignite-3 (was: ignite-3) > Sql. Refactor IgniteBuiltInMethod and IgniteMethod classes. > --- > > Key: IGNITE-16999 > URL: https://issues.apache.org/jira/browse/IGNITE-16999 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: calcite, calcite3-required, ignite-3 > > Adopt https://issues.apache.org/jira/browse/IGNITE-16119 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-16998) [Native Persistence 3.0] Add configuration for checkpoint.
Kirill Tkalenko created IGNITE-16998: Summary: [Native Persistence 3.0] Add configuration for checkpoint. Key: IGNITE-16998 URL: https://issues.apache.org/jira/browse/IGNITE-16998 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 3.0.0-alpha5 We need to add a configuration for the checkpoint, you can look at all *TODO*s in *org.apache.ignite.internal.pagememory.persistence.checkpoint*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16986) Incorrect GridCacheManager#stop parameters
[ https://issues.apache.org/jira/browse/IGNITE-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538627#comment-17538627 ] Kirill Tkalenko commented on IGNITE-16986: -- [~sdanilov] Looks good to me. > Incorrect GridCacheManager#stop parameters > --- > > Key: IGNITE-16986 > URL: https://issues.apache.org/jira/browse/IGNITE-16986 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if > the whole cache group is going to be destroyed. However, this leads to > GridCacheManager#stop receiving incorrect destroy argument and potentially > not performing some tasks (for example, not dropping statistics). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16986) Incorrect GridCacheManager#stop parameters
[ https://issues.apache.org/jira/browse/IGNITE-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16986: - Reviewer: Kirill Tkalenko > Incorrect GridCacheManager#stop parameters > --- > > Key: IGNITE-16986 > URL: https://issues.apache.org/jira/browse/IGNITE-16986 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if > the whole cache group is going to be destroyed. However, this leads to > GridCacheManager#stop receiving incorrect destroy argument and potentially > not performing some tasks (for example, not dropping statistics). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16986) Incorrect GridCacheProcessor#stop parameters
[ https://issues.apache.org/jira/browse/IGNITE-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-16986: Description: IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if the whole cache group is going to be destroyed. However, this leads to GridCacheManager#stop receiving incorrect destroy argument and potentially not performing some tasks (for example, not dropping statistics). > Incorrect GridCacheProcessor#stop parameters > - > > Key: IGNITE-16986 > URL: https://issues.apache.org/jira/browse/IGNITE-16986 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if > the whole cache group is going to be destroyed. However, this leads to > GridCacheManager#stop receiving incorrect destroy argument and potentially > not performing some tasks (for example, not dropping statistics). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16986) Incorrect GridCacheManager#stop parameters
[ https://issues.apache.org/jira/browse/IGNITE-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-16986: Summary: Incorrect GridCacheManager#stop parameters (was: Incorrect GridCacheProcessor#stop parameters ) > Incorrect GridCacheManager#stop parameters > --- > > Key: IGNITE-16986 > URL: https://issues.apache.org/jira/browse/IGNITE-16986 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if > the whole cache group is going to be destroyed. However, this leads to > GridCacheManager#stop receiving incorrect destroy argument and potentially > not performing some tasks (for example, not dropping statistics). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-16997) Design baseline concept
Alexander Lapin created IGNITE-16997: Summary: Design baseline concept Key: IGNITE-16997 URL: https://issues.apache.org/jira/browse/IGNITE-16997 Project: Ignite Issue Type: Task Reporter: Alexander Lapin TBD -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16318) Empty binary object is incorrect written/read/modified
[
https://issues.apache.org/jira/browse/IGNITE-16318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538601#comment-17538601
]
Ignite TC Bot commented on IGNITE-16318:
{panel:title=Branch: [pull/10021/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10021/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Binary Objects{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=6572776]]
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerNonCompactSelfTest.emptyObjectBuilder[useBinaryArrays = false]
- PASSED{color}
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerSelfTest.emptyObjectBuilder[useBinaryArrays = true] -
PASSED{color}
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerSelfTest.emptyObjectBuilder[useBinaryArrays = false] -
PASSED{color}
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerNonCompactSelfTest.emptyObjectBuilder[useBinaryArrays = true] -
PASSED{color}
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerNonCompactSelfTest.emptyObjectBinarylizable[useBinaryArrays =
true] - PASSED{color}
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerNonCompactSelfTest.emptyObjectBinarylizable[useBinaryArrays =
false] - PASSED{color}
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerSelfTest.emptyObjectBinarylizable[useBinaryArrays = true] -
PASSED{color}
* {color:#013220}IgniteBinaryObjectsTestSuite:
BinaryMarshallerSelfTest.emptyObjectBinarylizable[useBinaryArrays = false] -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6572878buildTypeId=IgniteTests24Java8_RunAll]
> Empty binary object is incorrect written/read/modified
> --
>
> Key: IGNITE-16318
> URL: https://issues.apache.org/jira/browse/IGNITE-16318
> Project: Ignite
> Issue Type: Bug
> Components: binary, cache
>Reporter: Andrey Belyaev
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Cache interceptor cause problem of missing binary scheme if sql insert
> contains only entry key fields and no one value field pass in query.
> There is exception happened if inside interceptor we try to make
> BinaryObjectBuilder from entry value BinaryObject (#toBuilder()) and then
> request builder for any field.
> Interceptor example:
> {code:java}
> new CacheInterceptorAdapter() {
> @Nullable
> @Override public BinaryObject onBeforePut(Cache.Entry BinaryObject> entry, BinaryObject newVal) {
> BinaryObjectBuilder newValBuilder = newVal.toBuilder();
> String bValue = newValBuilder.getField("B"); // Cannot find schema
> for object with compact footer
> // ...
> }
> } {code}
> It's a pretty serious error which currupt and shutdown grid.
> Code example:
> {code:java}
> LinkedHashMap fields = new LinkedHashMap<>();
> fields.put("A", "java.lang.String");
> fields.put("B", "java.lang.String");
> fields.put("C", "java.lang.String");
> Set keyFields = new LinkedHashSet<>();
> keyFields.add("A");
> CacheInterceptorAdapter cacheInterceptorAdapter = new
> CacheInterceptorAdapter() {
> @Nullable
> @Override public BinaryObject onBeforePut(Cache.Entry BinaryObject> entry, BinaryObject newVal) {
> BinaryObjectBuilder newValBuilder = newVal.toBuilder();
> String bValue = newValBuilder.getField("B"); // Cannot find schema
> for object with compact footer
> if (bValue == null || bValue.isEmpty()) {
> newValBuilder.setField("B", "Some value");
> }
> return newValBuilder.build();
> }
> };
> CacheConfiguration cacheConfiguration = new CacheConfiguration<>()
> .setName("TEST_CACHE")
> .setKeyConfiguration(new CacheKeyConfiguration()
> .setTypeName("TEST_CACHE_KEY")
> .setAffinityKeyFieldName("InternalId"))
> .setQueryEntities(Collections.singleton(new QueryEntity()
> .setTableName("TEST_CACHE")
> .setKeyType("TEST_CACHE_KEY")
> .setValueType("TEST_CACHE_VALUE")
> .setFields(fields)
> .setKeyFields(keyFields)))
> .setInterceptor(cacheInterceptorAdapter);
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration()
> .setCacheConfiguration(cacheConfiguration);
> try (Ignite ignite = Ignition.start(igniteConfiguration)) {
> IgniteCache testCache = ignite.getOrCreateCache("TEST_CACHE");
> // putSql
> testCache.query(new SqlFieldsQuery("INSERT INTO TEST_CACHE (A) VALUES
> ('1234')"));
> }{code}
[jira] [Updated] (IGNITE-16989) Annoying "Failed to ping node" warn messages in logs.
[ https://issues.apache.org/jira/browse/IGNITE-16989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16989: Labels: ise storage-engine (was: storage-engine) > Annoying "Failed to ping node" warn messages in logs. > - > > Key: IGNITE-16989 > URL: https://issues.apache.org/jira/browse/IGNITE-16989 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.13 >Reporter: Evgeny Stanilovsky >Priority: Major > Labels: ise, storage-engine > > From user list [1], seems there is present annoying uninformative message in > logs, possible we neet to print only one of such a kind of messages and wrap > others into trace or debug severity? > [1] https://lists.apache.org/thread/1mkng62pco1nsjtdgm881m5ny9v3rogd > [~vladsz83] fyi too. -- This message was sent by Atlassian Jira (v8.20.7#820007)
