[jira] [Commented] (IGNITE-14703) Add merge-sort reducer for cache queries.
[ https://issues.apache.org/jira/browse/IGNITE-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355500#comment-17355500 ] Maksim Timonin commented on IGNITE-14703: - [~amashenkov] hi! Add visa of the MTCGA bot. > Add merge-sort reducer for cache queries. > - > > Key: IGNITE-14703 > URL: https://issues.apache.org/jira/browse/IGNITE-14703 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Time Spent: 4h 50m > Remaining Estimate: 0h > > MergeSort reducer is required for Index queries that should provide a sorted > result for user. > > Note that text queries does not return sorted result, as lucene invoked > without sort param. So this ticket is only for querying Btree indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14703) Add merge-sort reducer for cache queries.
[
https://issues.apache.org/jira/browse/IGNITE-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355499#comment-17355499
]
Ignite TC Bot commented on IGNITE-14703:
{panel:title=Branch: [pull/9081/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9081/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=6031117]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=7] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=8] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=1] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=2] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=5] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=6] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=3] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=4] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryHighLimitedMultiplePages -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryMultiplePagesNoLimit -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryLimitedMultiplePages -
PASSED{color}
... and 0 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6024512&buildTypeId=IgniteTests24Java8_RunAll]
> Add merge-sort reducer for cache queries.
> -
>
> Key: IGNITE-14703
> URL: https://issues.apache.org/jira/browse/IGNITE-14703
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maksim Timonin
>Assignee: Maksim Timonin
>Priority: Major
> Labels: IEP-71
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> MergeSort reducer is required for Index queries that should provide a sorted
> result for user.
>
> Note that text queries does not return sorted result, as lucene invoked
> without sort param. So this ticket is only for querying Btree indexes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14753) Build via maven 3.8.1 fails
[ https://issues.apache.org/jira/browse/IGNITE-14753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354163#comment-17354163 ] Ilya Korol edited comment on IGNITE-14753 at 6/2/21, 1:34 AM: -- Update versions (migrate from http repositories): apache parent jotm (several tests broke after update, fixed) Fix broken configuration for jar plugin (due to versions upgrade in apache parent): Remove 'useDefaultManifestFile' option from ignite parent pom (due to deprecation) Add classifiers for artifacts in modules/extdata/uri Remove duplicated dependencies definitions from several modules (maven complained to this during builds with warnings) was (Author: korol): Update versions (migrate from http repositories): apache parent jotm (several tests broke after update, fixed) spark-core_2.11 Fix broken configuration for jar plugin (due to versions upgrade in apache parent): Remove 'useDefaultManifestFile' option from ignite parent pom (due to deprecation) Add classifiers for artifacts in modules/extdata/uri Remove duplicated dependencies definitions from several modules (maven complained to this during builds with warnings) > Build via maven 3.8.1 fails > > > Key: IGNITE-14753 > URL: https://issues.apache.org/jira/browse/IGNITE-14753 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ilya Korol >Assignee: Ilya Korol >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Building ignite with latest maven (3.8.1) fails due to http blocking policy. > https://maven.apache.org/docs/3.8.1/release-notes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14753) Build via maven 3.8.1 fails
[
https://issues.apache.org/jira/browse/IGNITE-14753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355429#comment-17355429
]
Ignite TC Bot commented on IGNITE-14753:
{panel:title=Branch: [pull/9116/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9116/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6030481&buildTypeId=IgniteTests24Java8_RunAll]
> Build via maven 3.8.1 fails
>
>
> Key: IGNITE-14753
> URL: https://issues.apache.org/jira/browse/IGNITE-14753
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Ilya Korol
>Assignee: Ilya Korol
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Building ignite with latest maven (3.8.1) fails due to http blocking policy.
> https://maven.apache.org/docs/3.8.1/release-notes.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14529) Add offline utility for analyzing indexes
[
https://issues.apache.org/jira/browse/IGNITE-14529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355342#comment-17355342
]
Ignite TC Bot commented on IGNITE-14529:
{panel:title=Branch: [pull/9115/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9115/head] Base: [master] : New Tests
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Control Utility{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=6031315]]
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testCorrectIdxWithCheckParts - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testCorruptedIdxAndPart - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testCorrectIdxWithFilter - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite: IgniteIndexReaderTest.testEmpty
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testCorruptedIdxWithCheckParts - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testCorruptedPart - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testQryCacheGroup - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testCorruptedIdx - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
IgniteIndexReaderTest.testCorrectIdx - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6031323&buildTypeId=IgniteTests24Java8_RunAll]
> Add offline utility for analyzing indexes
> -
>
> Key: IGNITE-14529
> URL: https://issues.apache.org/jira/browse/IGNITE-14529
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It would be useful to have the possibility for indexes offline validation.
> The utility must check that every configured index (available in MetaTree
> [1]) is reachable from corresponding root page, tree structure is valid and
> no orphan(unreachable) index pages are present in the index.bin persistent
> page store.
> [1]
> org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getIndexNames
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14719) Thin clients: enable partition awareness by default
[ https://issues.apache.org/jira/browse/IGNITE-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14719: Release Note: Thin clients: enable partition awareness by default (Java, .NET, C++) > Thin clients: enable partition awareness by default > --- > > Key: IGNITE-14719 > URL: https://issues.apache.org/jira/browse/IGNITE-14719 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > * Enable partition awareness by default in all thin clients > * Remove experimental status from the docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14719) Thin clients: enable partition awareness by default
[ https://issues.apache.org/jira/browse/IGNITE-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355276#comment-17355276 ] Pavel Tupitsyn commented on IGNITE-14719: - Merged to master: 6fa83f078430daa9daea93ab38bd43154bf6dc69 > Thin clients: enable partition awareness by default > --- > > Key: IGNITE-14719 > URL: https://issues.apache.org/jira/browse/IGNITE-14719 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > * Enable partition awareness by default in all thin clients > * Remove experimental status from the docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14719) Thin clients: enable partition awareness by default
[ https://issues.apache.org/jira/browse/IGNITE-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355252#comment-17355252 ] Igor Sapego commented on IGNITE-14719: -- [~ptupitsyn] looks good to me. > Thin clients: enable partition awareness by default > --- > > Key: IGNITE-14719 > URL: https://issues.apache.org/jira/browse/IGNITE-14719 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > * Enable partition awareness by default in all thin clients > * Remove experimental status from the docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-7231) Cassandra-sessions-pool is running after Ignition.stop
[ https://issues.apache.org/jira/browse/IGNITE-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov reassigned IGNITE-7231: -- Assignee: (was: Anton Kurbanov) > Cassandra-sessions-pool is running after Ignition.stop > -- > > Key: IGNITE-7231 > URL: https://issues.apache.org/jira/browse/IGNITE-7231 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Priority: Minor > Attachments: ThreadDump.txt > > > Cassandra-sessions-pool is running after Ignition.stop. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14801) Add tests for commands to manage metadata
[
https://issues.apache.org/jira/browse/IGNITE-14801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355199#comment-17355199
]
Ignite TC Bot commented on IGNITE-14801:
{panel:title=Branch: [pull/9137/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9137/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Control Utility{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6029606]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerMetadataTest.testRemoveUpdateUnderLoad - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerMetadataTest.testTypeMergedAfterRemoveUpdate - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerMetadataTest.testMetadataListDetailsAfterTypeRemoving -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerMetadataTest.testTypeCantBeMergedAfterRemoveUpdateWithIncompatibleChanges
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6029614&buildTypeId=IgniteTests24Java8_RunAll]
> Add tests for commands to manage metadata
> -
>
> Key: IGNITE-14801
> URL: https://issues.apache.org/jira/browse/IGNITE-14801
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add tests for commands to manage metadata (see IGNITE-13154).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14801) Add tests for commands to manage metadata
[ https://issues.apache.org/jira/browse/IGNITE-14801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355200#comment-17355200 ] Taras Ledkov commented on IGNITE-14801: --- [~korlov], please review the patch. > Add tests for commands to manage metadata > - > > Key: IGNITE-14801 > URL: https://issues.apache.org/jira/browse/IGNITE-14801 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > Add tests for commands to manage metadata (see IGNITE-13154). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14719) Thin clients: enable partition awareness by default
[
https://issues.apache.org/jira/browse/IGNITE-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14719:
Comment: was deleted
(was: {panel:title=Branch: [pull/9141/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Out Of Memory
Error , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6030529]]
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6030537]]
* exe: CacheTest.TestCacheWithExpiryPolicyOnUpdate - Test has low fail rate in
base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9141/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6030091&buildTypeId=IgniteTests24Java8_RunAll])
> Thin clients: enable partition awareness by default
> ---
>
> Key: IGNITE-14719
> URL: https://issues.apache.org/jira/browse/IGNITE-14719
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * Enable partition awareness by default in all thin clients
> * Remove experimental status from the docs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14719) Thin clients: enable partition awareness by default
[
https://issues.apache.org/jira/browse/IGNITE-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355190#comment-17355190
]
Ignite TC Bot commented on IGNITE-14719:
{panel:title=Branch: [pull/9141/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6031490]]
* exe: DefaultLoggerTest.TestJavaLogger - Test has low fail rate in base branch
0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9141/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6030091&buildTypeId=IgniteTests24Java8_RunAll]
> Thin clients: enable partition awareness by default
> ---
>
> Key: IGNITE-14719
> URL: https://issues.apache.org/jira/browse/IGNITE-14719
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * Enable partition awareness by default in all thin clients
> * Remove experimental status from the docs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14811) .NET: Replace FxCop with Roslyn-based analyzers
Pavel Tupitsyn created IGNITE-14811: --- Summary: .NET: Replace FxCop with Roslyn-based analyzers Key: IGNITE-14811 URL: https://issues.apache.org/jira/browse/IGNITE-14811 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.11 * FxCop is deprecated long time ago * It is Windows-only Remove FxCop and set up build-time Roslyn-based code analysis in DotNetCore solution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14808) Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
[
https://issues.apache.org/jira/browse/IGNITE-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355160#comment-17355160
]
Stanilovsky Evgeny commented on IGNITE-14808:
-
[~korlov] take a look plz ?
> Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
> -
>
> Key: IGNITE-14808
> URL: https://issues.apache.org/jira/browse/IGNITE-14808
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
> Time Spent: 10m
> Remaining Estimate: 0h
>
> queries like
> {noformat}
> FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
> NULLS FIRST
> {noformat} will bring to erroneous results. Also some tests from /sql/join*
> have no ordering thus results are not equal to pattern.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14810) Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
[
https://issues.apache.org/jira/browse/IGNITE-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny resolved IGNITE-14810.
-
Resolution: Not A Bug
> Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
>
>
> Key: IGNITE-14810
> URL: https://issues.apache.org/jira/browse/IGNITE-14810
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
> For now simple JOIN requests like:
> {noformat}
> SELECT * FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k
> ORDER BY i
> {noformat}
> can be planned only through MergeJoin or NestedLoopJoin it would be useful to
> extend it with CNLJ too. Starting point :
> {{FilterSpoolMergeToSortedIndexSpoolRule#onMatch}}
> We have to add new rule
> {{FilterSpoolMergeToSortedIndexSpoolRule_ForceCollation}} which forces
> collation by the filter condition.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14810) Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
[
https://issues.apache.org/jira/browse/IGNITE-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14810:
--
Description:
For now simple JOIN requests like:
{noformat}
SELECT * FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k
ORDER BY i
{noformat}
can be planned only through MergeJoin or NestedLoopJoin it would be useful to
extend it with CNLJ too. Starting point :
{{FilterSpoolMergeToSortedIndexSpoolRule#onMatch}}
We have to add new rule
{{FilterSpoolMergeToSortedIndexSpoolRule_ForceCollation}} which forces
collation by the filter condition.
was:
For now simple JOIN requests like:
{noformat}
SELECT * FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k
ORDER BY i
{noformat}
can be planned only through MergeJoin or NestedLoopJoin it would be useful to
extend it with CNLJ too. Starting point :
FilterSpoolMergeToSortedIndexSpoolRule#onMatch
> Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
>
>
> Key: IGNITE-14810
> URL: https://issues.apache.org/jira/browse/IGNITE-14810
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
> For now simple JOIN requests like:
> {noformat}
> SELECT * FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k
> ORDER BY i
> {noformat}
> can be planned only through MergeJoin or NestedLoopJoin it would be useful to
> extend it with CNLJ too. Starting point :
> {{FilterSpoolMergeToSortedIndexSpoolRule#onMatch}}
> We have to add new rule
> {{FilterSpoolMergeToSortedIndexSpoolRule_ForceCollation}} which forces
> collation by the filter condition.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14719) Thin clients: enable partition awareness by default
[
https://issues.apache.org/jira/browse/IGNITE-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14719:
Comment: was deleted
(was: {panel:title=Branch: [pull/9141/head] Base: [master] : Possible Blockers
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6030050]]
* IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_2 - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Examples{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6030001]]
* IgniteExamplesSelfTestSuite:
BasicExamplesMultiNodeSelfTest.testClosureExample - Test has low fail rate in
base branch 0,0% and is not flaky
{color:#d04437}Cache (Restarts) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6030042]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=6030065]]
* dll: IgniteConfigurationTest.TestDefaultValueAttributes - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Binary Objects{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6029993]]
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6030008]]
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6030071]]
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET{color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=6030064]]
{color:#d04437}Cache (Restarts) 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6030043]]
* IgniteCacheRestartTestSuite2:
IgniteCacheGetRestartTest.testGetRestartReplicated - Test has low fail rate in
base branch 0,0% and is not flaky
* org.apache.ignite.testsuites.IgniteCacheRestartTestSuite2:
org.apache.ignite.internal.processors.cache.distributed.IgniteCacheGetRestartTest.
- History for base branch is absent.
{color:#d04437}Compute (Grid){color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=6029998]]
{panel}
{panel:title=Branch: [pull/9141/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Cache (Restarts) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6030043]]
* {color:#8b}org.apache.ignite.testsuites.IgniteCacheRestartTestSuite2:
org.apache.ignite.internal.processors.cache.distributed.IgniteCacheGetRestartTest.
- FAILED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6030091&buildTypeId=IgniteTests24Java8_RunAll])
> Thin clients: enable partition awareness by default
> ---
>
> Key: IGNITE-14719
> URL: https://issues.apache.org/jira/browse/IGNITE-14719
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * Enable partition awareness by default in all thin clients
> * Remove experimental status from the docs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14719) Thin clients: enable partition awareness by default
[
https://issues.apache.org/jira/browse/IGNITE-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355137#comment-17355137
]
Ignite TC Bot commented on IGNITE-14719:
{panel:title=Branch: [pull/9141/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Out Of Memory
Error , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6030529]]
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6030537]]
* exe: CacheTest.TestCacheWithExpiryPolicyOnUpdate - Test has low fail rate in
base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9141/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6030091&buildTypeId=IgniteTests24Java8_RunAll]
> Thin clients: enable partition awareness by default
> ---
>
> Key: IGNITE-14719
> URL: https://issues.apache.org/jira/browse/IGNITE-14719
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * Enable partition awareness by default in all thin clients
> * Remove experimental status from the docs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14810) Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
[
https://issues.apache.org/jira/browse/IGNITE-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny updated IGNITE-14810:
Summary: Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
(was: Calcite. SimpleJOIN with f1=f2 cannot be planned with CNLJ.)
> Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
>
>
> Key: IGNITE-14810
> URL: https://issues.apache.org/jira/browse/IGNITE-14810
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
> For now simple JOIN requests like:
> {noformat}
> SELECT * FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k
> ORDER BY i
> {noformat}
> can be planned only through MergeJoin or NestedLoopJoin it would be useful to
> extend it with CNLJ too. Starting point :
> FilterSpoolMergeToSortedIndexSpoolRule#onMatch
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14810) Calcite. SimpleJOIN with f1=f2 cannot be planned with CNLJ.
Stanilovsky Evgeny created IGNITE-14810:
---
Summary: Calcite. SimpleJOIN with f1=f2 cannot be planned with
CNLJ.
Key: IGNITE-14810
URL: https://issues.apache.org/jira/browse/IGNITE-14810
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Stanilovsky Evgeny
For now simple JOIN requests like:
{noformat}
SELECT * FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k
ORDER BY i
{noformat}
can be planned only through MergeJoin or NestedLoopJoin it would be useful to
extend it with CNLJ too. Starting point :
FilterSpoolMergeToSortedIndexSpoolRule#onMatch
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14809) Implement IndexQuery predicate operation
Maksim Timonin created IGNITE-14809: --- Summary: Implement IndexQuery predicate operation Key: IGNITE-14809 URL: https://issues.apache.org/jira/browse/IGNITE-14809 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Maksim Timonin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14248) Handle exceptions in PartitionReservationManager.onDoneAfterTopologyUnlock properly
[
https://issues.apache.org/jira/browse/IGNITE-14248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355126#comment-17355126
]
Vladimir Pligin commented on IGNITE-14248:
--
Hi [~slava.koptilin],
It's all good now.
> Handle exceptions in PartitionReservationManager.onDoneAfterTopologyUnlock
> properly
> ---
>
> Key: IGNITE-14248
> URL: https://issues.apache.org/jira/browse/IGNITE-14248
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.9.1
>Reporter: Vladimir Pligin
>Assignee: Vladimir Pligin
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If an exception (or even Error) is thrown inside of the method then the node
> turns into some unrecoverable state. Here's an example.
> # an exchange is about to finish, it's time to invalidate partition
> reservations.
> # exchange thread delegates it to a thread in the management pool
> # management pool tries to allocate a new thread (maybe it's idle and
> therefore empty)
> # for example ulimit is reached, the error is
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> # It's being logged, no further action is taken
> # partitions are reserved forever
> Message:
>
> {code:java}
> 2021-02-25 05:52:03.242 [exchange-worker-#182] ERROR
> o.a.i.i.p.q.h.t.PartitionReservationManager - Unexpected exception on start
> reservations cleanup
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1343)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runLocal(GridClosureProcessor.java:847)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.PartitionReservationManager.onDoneAfterTopologyUnlock(PartitionReservationManager.java:323)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2617)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:159)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:475)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:1064)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3375)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3194)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
>
>
> Code of PartitionReservationManager.onDoneAfterTopologyUnlock:
> {code:java}
> @Override public void onDoneAfterTopologyUnlock(final
> GridDhtPartitionsExchangeFuture fut) {
> try {
> // Must not do anything at the exchange thread. Dispatch to the
> management thread pool.
> ctx.closure().runLocal(() -> {
> AffinityTopologyVersion topVer =
> ctx.cache().context().exchange()
>
> .lastAffinityChangedTopologyVersion(fut.topologyVersion());
> reservations.forEach((key, r) -> {
> if (r != REPLICATED_RESERVABLE &&
> !F.eq(key.topologyVersion(), topVer)) {
> assert r instanceof GridDhtPartitionsReservation;
>((GridDhtPartitionsReservation)r).invalidate();
> }
> });
> },
> GridIoPolicy.MANAGEMENT_POOL);
> }
> catch (Throwable e) {
> log.error("Unexpected exception on start reservations cleanup",
> e);
> }
> }
> {code}
>
>
> My vision is that there are two basic approaches:
> * to kill the node (it's already non-functional at this point), seems to be
> a FH job.
> * try to recover somehow (to be honest it's not clear how exactly)
> This particular OOM situation seems unrecoverable in fact. It's an
> environment misconfiguration. It would be great to in
[jira] [Commented] (IGNITE-14715) Create an annotation processor for generating network message implementations
[
https://issues.apache.org/jira/browse/IGNITE-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355093#comment-17355093
]
Aleksandr Polovtcev commented on IGNITE-14715:
--
Introduced two new annotations:
1. `AutoMessage` marks a message interface as a candidate for implementation
generation. `autoSerializable` parameter can be used to avoid generating
serialization classes (e.g. for compatibility with Raft messages).
2. `ModuleMessageTypes` declares a module descriptor containing a module name
and a module type.
Generated message implementations are immutable, new message instances can be
created using the generated Builder interfaces and a Factory.
> Create an annotation processor for generating network message implementations
> -
>
> Key: IGNITE-14715
> URL: https://issues.apache.org/jira/browse/IGNITE-14715
> Project: Ignite
> Issue Type: Sub-task
> Components: networking
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Minor
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently all {{NetworkMessage}} implementations are created by hand which is
> inconvenient (e.g. one needs to declare constructors and getters). It is
> proposed to automatically generate these implementations using an annotation
> processor.
> h3. Implementation details
> * Custom messages should be declared as interfaces extending
> {{NetworkMessage}}. Methods in these interfaces should correspond to the
> message fields, for example:
> {code:java}
> @Message(type = ACTION_REQUEST)
> public interface ActionRequest extends NetworkMessage {
> String groupId();
> Command command();
> }
> {code}
> * Every message interface should be annotated with the {{@Message}}
> interface, with a *message type* parameter of type {{short}}, unique across a
> *module*. All message types should be manually listed in an interface marked
> with the {{@MessageTypes}} annotation with a *module identifier*. For example:
> {code:java}
> @MessageTypes(moduleType = 10)
> class RaftMessageTypes {
> public final short ACTION_REQUEST = 1;
> }
> {code}
> * Message implementations should have a generated {{Builder}} interface for
> creating new messages:
> {code:java}
> public interface Builder {
> Builder command(Command cmd);
> Builder groupId(String groupId);
> ActionRequest build();
> }
> {code}
> * {{Builder}} instances should be obtained using a generated factory, based
> on the current module type:
> {code:java}
> public interface RaftClientMessageFactory {
> ActionRequestBuilder actionRequest();
> ActionResponseBuilder actionResponse();
> // ...
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14791) Support byte[] configuration values
[ https://issues.apache.org/jira/browse/IGNITE-14791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-14791: --- Labels: ignite-3 (was: ) > Support byte[] configuration values > --- > > Key: IGNITE-14791 > URL: https://issues.apache.org/jira/browse/IGNITE-14791 > Project: Ignite > Issue Type: Sub-task >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > > Right now "smallest" array type that we have is int[], it may not be > convenient for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14791) Support byte[] configuration values
[ https://issues.apache.org/jira/browse/IGNITE-14791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-14791: --- Affects Version/s: 3.0.0-alpha2 > Support byte[] configuration values > --- > > Key: IGNITE-14791 > URL: https://issues.apache.org/jira/browse/IGNITE-14791 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 3.0.0-alpha2 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > > Right now "smallest" array type that we have is int[], it may not be > convenient for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14747) RocksDB research: configuration, lifecycle, basic integration
[ https://issues.apache.org/jira/browse/IGNITE-14747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-14747: -- Assignee: Ivan Bessonov > RocksDB research: configuration, lifecycle, basic integration > - > > Key: IGNITE-14747 > URL: https://issues.apache.org/jira/browse/IGNITE-14747 > Project: Ignite > Issue Type: New Feature >Reporter: Sergey Chugunov >Assignee: Ivan Bessonov >Priority: Major > Labels: iep-74, ignite-3 > Fix For: 3.0 > > > In accordance with > [IEP-74|https://cwiki.apache.org/confluence/display/IGNITE/IEP-74+Data+Storage] > first implementation of persistent Storage will be based on RocksDB K-V > storage. > Thus research is needed on how to integrate it into ignite-3 realm. The > following questions should be covered: > # What additional configuration properties are needed. > # How to reconcile lifecycle of RocksDB instance with Ignite node lifecycle. > # How RocksDB abstractions (e.g. partitions) match with Ignite abstractions. > Also scope of tasks to implement basic Storage API over RocksDB should be > defined. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14745) Storage API and basic configuration module
[
https://issues.apache.org/jira/browse/IGNITE-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov reassigned IGNITE-14745:
--
Assignee: Ivan Bessonov
> Storage API and basic configuration module
> --
>
> Key: IGNITE-14745
> URL: https://issues.apache.org/jira/browse/IGNITE-14745
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Chugunov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: iep-74, ignite-3
> Fix For: 3.0
>
>
> Introduce basic Storage API described in
> [IEP-74|https://cwiki.apache.org/confluence/display/IGNITE/IEP-74+Data+Storage]
> in a separate module.
> For now Storage API should contain only four basic methods to read, update
> and remove keys from Storage and to iterate over available keys:
> {code:java}
> /** Interface providing methods to read, remove and update keys in storage. */
> public interface Storage {
> /** Reads a DataRow for a given Key. */
> public DataRow read(Key key);
>
> /** Removes DataRow associated with a given Key. */
> public void remove(Key key);
>
> /** Executes an update with custom logic implemented by UpdateClosure
> interface. */
> public update(Key key, UpdateClosure clo);
>
> /** Obtains Iterator over some DataRows in storage. */
> public Iterator iterator(/* parameters */).
> }
> {code}
> This simplistic API is based on IgniteCacheOffheapManager from existing code
> base of Ignite 2.x. Only essential methods were left for the initial version
> of interface but it obviously will be refined during development.
> Details about some classes like Key or UpdateClosure are not clear yet and
> can be omitted (basic stub classes may be used).
> Implement basic configuration that is expected to be common for any Storage
> implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14791) Support byte[] configuration values
[ https://issues.apache.org/jira/browse/IGNITE-14791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev reassigned IGNITE-14791: Assignee: Aleksandr Polovtcev > Support byte[] configuration values > --- > > Key: IGNITE-14791 > URL: https://issues.apache.org/jira/browse/IGNITE-14791 > Project: Ignite > Issue Type: Sub-task >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > > Right now "smallest" array type that we have is int[], it may not be > convenient for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14715) Create an annotation processor for generating network message implementations
[
https://issues.apache.org/jira/browse/IGNITE-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-14715:
-
Release Note: (was: Introduced two new annotations:
1. `AutoMessage` marks a message interface as a candidate for implementation
generation. `autoSerializable` parameter can be used to avoid generating
serialization classes (e.g. for compatibility with Raft messages).
2. `ModuleMessageTypes` declares a module descriptor containing a module name
and a module type.
Generated message implementations are immutable, new message instances can be
created using the generated Builder interfaces and a Factory.)
> Create an annotation processor for generating network message implementations
> -
>
> Key: IGNITE-14715
> URL: https://issues.apache.org/jira/browse/IGNITE-14715
> Project: Ignite
> Issue Type: Sub-task
> Components: networking
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Minor
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently all {{NetworkMessage}} implementations are created by hand which is
> inconvenient (e.g. one needs to declare constructors and getters). It is
> proposed to automatically generate these implementations using an annotation
> processor.
> h3. Implementation details
> * Custom messages should be declared as interfaces extending
> {{NetworkMessage}}. Methods in these interfaces should correspond to the
> message fields, for example:
> {code:java}
> @Message(type = ACTION_REQUEST)
> public interface ActionRequest extends NetworkMessage {
> String groupId();
> Command command();
> }
> {code}
> * Every message interface should be annotated with the {{@Message}}
> interface, with a *message type* parameter of type {{short}}, unique across a
> *module*. All message types should be manually listed in an interface marked
> with the {{@MessageTypes}} annotation with a *module identifier*. For example:
> {code:java}
> @MessageTypes(moduleType = 10)
> class RaftMessageTypes {
> public final short ACTION_REQUEST = 1;
> }
> {code}
> * Message implementations should have a generated {{Builder}} interface for
> creating new messages:
> {code:java}
> public interface Builder {
> Builder command(Command cmd);
> Builder groupId(String groupId);
> ActionRequest build();
> }
> {code}
> * {{Builder}} instances should be obtained using a generated factory, based
> on the current module type:
> {code:java}
> public interface RaftClientMessageFactory {
> ActionRequestBuilder actionRequest();
> ActionResponseBuilder actionResponse();
> // ...
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14807) Eliminate usage of deprecated api within Ignite rels and rules
[ https://issues.apache.org/jira/browse/IGNITE-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14807: -- Description: Affected rels: * AbstractIgniteJoin * IgniteProject * AbstractIgniteConverterRule * FilterScanMergeRule was: Affected rels: * AbstractIgniteJoin * IgniteProject * AbstractIgniteConverterRule > Eliminate usage of deprecated api within Ignite rels and rules > -- > > Key: IGNITE-14807 > URL: https://issues.apache.org/jira/browse/IGNITE-14807 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Priority: Major > > Affected rels: > * AbstractIgniteJoin > * IgniteProject > * AbstractIgniteConverterRule > * FilterScanMergeRule -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14807) Eliminate usage of deprecated constructor of parent class within IgniteRels
[ https://issues.apache.org/jira/browse/IGNITE-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14807: -- Description: Affected rels: * AbstractIgniteJoin * IgniteProject * AbstractIgniteConverterRule was:Subj. > Eliminate usage of deprecated constructor of parent class within IgniteRels > --- > > Key: IGNITE-14807 > URL: https://issues.apache.org/jira/browse/IGNITE-14807 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Priority: Major > > Affected rels: > * AbstractIgniteJoin > * IgniteProject > * AbstractIgniteConverterRule -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14807) Eliminate usage of deprecated api within Ignite rels and rules
[ https://issues.apache.org/jira/browse/IGNITE-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14807: -- Summary: Eliminate usage of deprecated api within Ignite rels and rules (was: Eliminate usage of deprecated constructor of parent class within IgniteRels) > Eliminate usage of deprecated api within Ignite rels and rules > -- > > Key: IGNITE-14807 > URL: https://issues.apache.org/jira/browse/IGNITE-14807 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Priority: Major > > Affected rels: > * AbstractIgniteJoin > * IgniteProject > * AbstractIgniteConverterRule -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14808) Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
Stanilovsky Evgeny created IGNITE-14808:
---
Summary: Calcite. RIGHT|FULL Join operations are lost nulls sort
ordering.
Key: IGNITE-14808
URL: https://issues.apache.org/jira/browse/IGNITE-14808
Project: Ignite
Issue Type: Bug
Components: sql
Environment: queries like
{noformat}
FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
NULLS FIRST
{noformat} will bring to erroneous results. Also some tests from /sql/join*
have no ordering thus results are not equal to pattern.
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14808) Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
[
https://issues.apache.org/jira/browse/IGNITE-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny updated IGNITE-14808:
Description:
queries like
{noformat}
FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
NULLS FIRST
{noformat} will bring to erroneous results. Also some tests from /sql/join*
have no ordering thus results are not equal to pattern.
> Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
> -
>
> Key: IGNITE-14808
> URL: https://issues.apache.org/jira/browse/IGNITE-14808
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
> queries like
> {noformat}
> FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
> NULLS FIRST
> {noformat} will bring to erroneous results. Also some tests from /sql/join*
> have no ordering thus results are not equal to pattern.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14808) Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
[
https://issues.apache.org/jira/browse/IGNITE-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny updated IGNITE-14808:
Environment: (was: queries like
{noformat}
FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
NULLS FIRST
{noformat} will bring to erroneous results. Also some tests from /sql/join*
have no ordering thus results are not equal to pattern.
)
> Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
> -
>
> Key: IGNITE-14808
> URL: https://issues.apache.org/jira/browse/IGNITE-14808
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14807) Eliminate usage of deprecated constructor of parent class within IgniteRels
[ https://issues.apache.org/jira/browse/IGNITE-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14807: -- Summary: Eliminate usage of deprecated constructor of parent class within IgniteRels (was: Eliminate usage of deprecated constructor of parent class within IgnireRels) > Eliminate usage of deprecated constructor of parent class within IgniteRels > --- > > Key: IGNITE-14807 > URL: https://issues.apache.org/jira/browse/IGNITE-14807 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Priority: Major > > Subj. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14807) Eliminate usage of deprecated constructor of parent class within IgnireRels
[ https://issues.apache.org/jira/browse/IGNITE-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14807: -- Summary: Eliminate usage of deprecated constructor of parent class within IgnireRels (was: Eliminate usage of deprecated constructor of parent class within AbstractIgniteJoin) > Eliminate usage of deprecated constructor of parent class within IgnireRels > --- > > Key: IGNITE-14807 > URL: https://issues.apache.org/jira/browse/IGNITE-14807 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Priority: Major > > Subj. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355071#comment-17355071 ] Peter Ivanov commented on IGNITE-14017: --- Hi! I've seen the attachment, thanks! I will attend to issue later this week. > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Attachments: Dockerfile > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14807) Eliminate usage of deprecated constructor of parent class within AbstractIgniteJoin
Konstantin Orlov created IGNITE-14807: - Summary: Eliminate usage of deprecated constructor of parent class within AbstractIgniteJoin Key: IGNITE-14807 URL: https://issues.apache.org/jira/browse/IGNITE-14807 Project: Ignite Issue Type: Improvement Components: sql Reporter: Konstantin Orlov Subj. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14799) Create a method for range request by a prefix
[
https://issues.apache.org/jira/browse/IGNITE-14799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov reassigned IGNITE-14799:
---
Assignee: Kirill Gusakov
> Create a method for range request by a prefix
> -
>
> Key: IGNITE-14799
> URL: https://issues.apache.org/jira/browse/IGNITE-14799
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3
>
> Meta Storage manager provides methods for range request with left and right
> border, but it does not continent for internal configuration.
> We got used searching a configuration key by its prefix. So that need to add
> a possibility to get range of entries by prefix:
> {code}
> Cursor range(@NotNull ByteArray keyPrefix, long revUpperBound);
> Cursor range(@NotNull ByteArray keyPrefix);
> {code}
> Like it was done for Watch in Meta Storage manager.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355066#comment-17355066 ] Vibhuti Sawant commented on IGNITE-14017: - Hi [~vveider] I have updated [^Dockerfile] for s390x with the review comments received. Attaching the same here. Please let me know if any more changes are needed. > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Attachments: Dockerfile > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14187) .NET Thin Client: DataStreamer
[ https://issues.apache.org/jira/browse/IGNITE-14187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355063#comment-17355063 ] Igor Sapego commented on IGNITE-14187: -- [~ptupitsyn] overall looks good, but please see my comments in PR. > .NET Thin Client: DataStreamer > -- > > Key: IGNITE-14187 > URL: https://issues.apache.org/jira/browse/IGNITE-14187 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, iep-68 > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Add data streaming to Thin Client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12248) Apache Calcite based query execution engine
[ https://issues.apache.org/jira/browse/IGNITE-12248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-12248: - Assignee: Taras Ledkov > Apache Calcite based query execution engine > --- > > Key: IGNITE-12248 > URL: https://issues.apache.org/jira/browse/IGNITE-12248 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Igor Seliverstov >Assignee: Taras Ledkov >Priority: Major > Time Spent: 3h 10m > Remaining Estimate: 0h > > Currently used H2 based query execution engine has a number of critical > limitations Which do not allow to execute an arbitrary query. > The ticket aims to show potential of a new, Calcite based, execution engine > which may act not worse than current one on co-located queries, provide a > boost for queries, using distributed joins, and provide an ability to execute > arbitrary queries, requiring more than one map-reduce step in execution flow. > [IEP > link|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130028084] > [Dev list > thread|http://apache-ignite-developers.2346864.n4.nabble.com/New-SQL-execution-engine-td43724.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vibhuti Sawant updated IGNITE-14017: Attachment: Dockerfile > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Attachments: Dockerfile > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14703) Add merge-sort reducer for cache queries.
[ https://issues.apache.org/jira/browse/IGNITE-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-14703: Reviewer: Andrey Mashenkov > Add merge-sort reducer for cache queries. > - > > Key: IGNITE-14703 > URL: https://issues.apache.org/jira/browse/IGNITE-14703 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Time Spent: 4h 50m > Remaining Estimate: 0h > > MergeSort reducer is required for Index queries that should provide a sorted > result for user. > > Note that text queries does not return sorted result, as lucene invoked > without sort param. So this ticket is only for querying Btree indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14703) Add merge-sort reducer for cache queries.
[ https://issues.apache.org/jira/browse/IGNITE-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354992#comment-17354992 ] Maksim Timonin commented on IGNITE-14703: - Hi [~amashenkov] ! I've fixed some comments and answered on others. Could you please have a look? > Add merge-sort reducer for cache queries. > - > > Key: IGNITE-14703 > URL: https://issues.apache.org/jira/browse/IGNITE-14703 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Time Spent: 4h 50m > Remaining Estimate: 0h > > MergeSort reducer is required for Index queries that should provide a sorted > result for user. > > Note that text queries does not return sorted result, as lucene invoked > without sort param. So this ticket is only for querying Btree indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14120) select count * returns multiple rows
[ https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354924#comment-17354924 ] Ilya Korol commented on IGNITE-14120: - I've created reproducer and described my investigation results here https://github.com/solveme/ignite/blob/ignite-14120/modules/indexing/src/test/java/org/apache/ignite/client/MultiRowReproducerTest.java > select count * returns multiple rows > > > Key: IGNITE-14120 > URL: https://issues.apache.org/jira/browse/IGNITE-14120 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8.1 >Reporter: Isaac Zhu >Assignee: Yury Gerzhedovich >Priority: Major > > I have a partitioned table which has 1 backup, the *queryParallelism* is set > to 4. > The table primary key is column "ID", > If I do this query: > select count( * ) from my_table where ID = 1000; > It will return 4 rows: > 1 > 0 > 0 > 0 > > If I query by other not primary-key columns of this table, the result is > good, like: > select count( *) from my_table where name = 'abcd' > result is: > 0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14802) Flaky test ConnectionManagerTest#testReuseIncomingConnection
[ https://issues.apache.org/jira/browse/IGNITE-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-14802: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Flaky test ConnectionManagerTest#testReuseIncomingConnection > > > Key: IGNITE-14802 > URL: https://issues.apache.org/jira/browse/IGNITE-14802 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14802) Flaky test ConnectionManagerTest#testReuseIncomingConnection
[ https://issues.apache.org/jira/browse/IGNITE-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-14802: --- Affects Version/s: 3.0.0-alpha2 > Flaky test ConnectionManagerTest#testReuseIncomingConnection > > > Key: IGNITE-14802 > URL: https://issues.apache.org/jira/browse/IGNITE-14802 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha2 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14806) Synchronize localListener class name via discovery for displaying in CONTINUOUS_QUERIES system view
Ilya Kazakov created IGNITE-14806: - Summary: Synchronize localListener class name via discovery for displaying in CONTINUOUS_QUERIES system view Key: IGNITE-14806 URL: https://issues.apache.org/jira/browse/IGNITE-14806 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.10 Reporter: Ilya Kazakov Assignee: Ilya Kazakov CQ system view has LOCAL_LISTENER and LOCAL_TRANSFORMED_LISTENER fields. But these fields are not null only in case when we query the system view from the node which was deploying the CQ. In any other case, these fields will be null, because localListemer and localTransformedListened are not deployed on remote nodes. Thus to understand which localListener has the CQ, we should query system view from the node which was deploying the CQ. Often CQ client nodes deploy CQ, but there is no way to query CQ on the client node. It turns out there are many situations where we cannot find out which localListener is being used. I propose to make the localListener class name synchronized between nodes via discovery. Not deploying localListener on remote nodes, but just name synchronization. And this name will be used for LOCAL_LISTENER field in system view in case when localListened are not deployed on the node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
