[jira] [Commented] (IGNITE-18117) Populate DistributionZoneManager with MetaStorage listeners to distribution zone events
[ https://issues.apache.org/jira/browse/IGNITE-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645139#comment-17645139 ] Alexander Lapin commented on IGNITE-18117: -- [~maliev] LGTM > Populate DistributionZoneManager with MetaStorage listeners to distribution > zone events > --- > > Key: IGNITE-18117 > URL: https://issues.apache.org/jira/browse/IGNITE-18117 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > h3. Motivation > This thicket is about reaction to distribution zone reconfiguration events > (adding, updating, removing). DistributionConfiguratoinManager should > register corresponding configuration listeners with an appropriate handlers > that will recalculate dataNodes for added/updated distribution zones or > remove keys for dropped ones. > h3. Definition of Done > * DataNodes keys in meta storage are updated for each distribution zone > along with triggerRevision helper key as a result of distribution zones > creation, update or drop. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14636) Calcite engine. Support for LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-14636:
Labels: calcite3-required (was: calcite2-required calcite3-required)
> Calcite engine. Support for LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate
> function
> -
>
> Key: IGNITE-14636
> URL: https://issues.apache.org/jira/browse/IGNITE-14636
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite3-required
> Fix For: 2.14
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Tests:
> {{aggregate/aggregates/test_aggregate_types.test}}
> {{aggregate/aggregates/test_aggregate_types_scalar.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test_ignore}}
> {{aggregate/aggregates/test_string_agg.test_ignore}}
> {{aggregate/aggregates/test_string_agg_big.test_ignore}}
> {{aggregate/aggregates/test_string_agg_many_groups.test_slow_ignored}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13030) Calcite integration. Push projections to scans and avoid reading full row when possible
[
https://issues.apache.org/jira/browse/IGNITE-13030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-13030:
---
Labels: calcite calcite3-required (was: calcite2-required
calcite3-required)
> Calcite integration. Push projections to scans and avoid reading full row
> when possible
> ---
>
> Key: IGNITE-13030
> URL: https://issues.apache.org/jira/browse/IGNITE-13030
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Roman Kondakov
>Assignee: Aleksey Plekhanov
>Priority: Minor
> Labels: calcite, calcite3-required
> Fix For: 2.15
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> We can establish index-only scans in some cases. For example, if the column
> {{depId}} is indexed (and totally inlined), we can to execute a query like:
> {code:java}
> SELECT depId FROM emp
> {code}
> and collects resultset without pagememory lookups.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13030) Calcite integration. Push projections to scans and avoid reading full row when possible
[
https://issues.apache.org/jira/browse/IGNITE-13030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-13030:
---
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Calcite integration. Push projections to scans and avoid reading full row
> when possible
> ---
>
> Key: IGNITE-13030
> URL: https://issues.apache.org/jira/browse/IGNITE-13030
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Roman Kondakov
>Assignee: Aleksey Plekhanov
>Priority: Minor
> Labels: calcite, calcite3-required
> Fix For: 2.15
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> We can establish index-only scans in some cases. For example, if the column
> {{depId}} is indexed (and totally inlined), we can to execute a query like:
> {code:java}
> SELECT depId FROM emp
> {code}
> and collects resultset without pagememory lookups.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18346) .NET return Ignite version with a wrong timestamp part
[
https://issues.apache.org/jira/browse/IGNITE-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645093#comment-17645093
]
Ignite TC Bot commented on IGNITE-18346:
{panel:title=Branch: [pull/10426/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10426/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6950985]]
* {color:#013220}DotNetCore:
IgniteProductVersionTests.TestVersionStringMatchesIgniteVersionInLog -
PASSED{color}
{color:#8b}Platform .NET (Windows){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6950986]]
* {color:#013220}exe:
IgniteProductVersionTests.TestVersionStringMatchesIgniteVersionInLog -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6951017&buildTypeId=IgniteTests24Java8_RunAll]
> .NET return Ignite version with a wrong timestamp part
> --
>
> Key: IGNITE-18346
> URL: https://issues.apache.org/jira/browse/IGNITE-18346
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.14
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.15
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following code reproduces the issue:
> {code:c#}
> var node = Ignition.Start(cfg);
> Console.WriteLine("Version: " + node.GetVersion());
> {code}
> For version 2.14:
> {noformat}
> Expected: 2.14.0#20220929-sha1:951e8deb
> Actual: 2.14.0#19700102-sha1:951e8deb
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18347) .NET: B+Tree is corrupted when string value has emoticons
[
https://issues.apache.org/jira/browse/IGNITE-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danut Radoaica updated IGNITE-18347:
Environment:
Apache Ignite: v2.14.0
JDK: v1.11
.NET Core: v6.0
Azure Kubernetes Service (AKS)
StorageClass: (provisioner: disk.csi.azure.com, skuname: Premium_ZRS)
was:
Apache Ignite: v2.14.0
JDK: v1.11
.NET Core: v6.0
> .NET: B+Tree is corrupted when string value has emoticons
> -
>
> Key: IGNITE-18347
> URL: https://issues.apache.org/jira/browse/IGNITE-18347
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.14
> Environment: Apache Ignite: v2.14.0
> JDK: v1.11
> .NET Core: v6.0
> Azure Kubernetes Service (AKS)
> StorageClass: (provisioner: disk.csi.azure.com, skuname: Premium_ZRS)
>Reporter: Danut Radoaica
>Priority: Major
>
> exception: "JVM will be halted immediately due to the failure:
> [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1229361758, pageIds=[1129924291198982],
> groupName=Druid.DataAccess.DbEntities.LiveChatConversation, msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=937,
> val=6194b7bf-64a0-4b00-87eb-2660ecc3536a, hasValBytes=true], hash=1847364021,
> cacheId=-998779923"
> dto:
> [Table("LiveChatConversation")]
> private class LiveChatConversation
> {
> [Column]
> [Key]
> public Guid Id \{ get; set; }
> [Column]
> [MaxLength(255)]
> public string HelpdeskSubject \{ get; set; }
> }
> HelpdeskSubject string value: "💋"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18347) .NET: B+Tree is corrupted when string value has emoticons
[
https://issues.apache.org/jira/browse/IGNITE-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danut Radoaica updated IGNITE-18347:
Description:
exception: "JVM will be halted immediately due to the failure:
[failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [groupId=-1229361758, pageIds=[1129924291198982],
groupName=Druid.DataAccess.DbEntities.LiveChatConversation, msg=Runtime failure
on search row: SearchRow [key=KeyCacheObjectImpl [part=937,
val=6194b7bf-64a0-4b00-87eb-2660ecc3536a, hasValBytes=true], hash=1847364021,
cacheId=-998779923"
dto:
[Table("LiveChatConversation")]
private class LiveChatConversation
{
[Column]
[Key]
public Guid Id \{ get; set; }
[Column]
[MaxLength(255)]
public string HelpdeskSubject \{ get; set; }
}
HelpdeskSubject string value: "💋"
was:
exception: "JVM will be halted immediately due to the failure:
[failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [groupId=-1229361758, pageIds=[1129924291198982],
groupName=Druid.DataAccess.DbEntities.LiveChatConversation, msg=Runtime failure
on search row: SearchRow [key=KeyCacheObjectImpl [part=937,
val=6194b7bf-64a0-4b00-87eb-2660ecc3536a, hasValBytes=true], hash=1847364021,
cacheId=-998779923"
test string value: "💋"
> .NET: B+Tree is corrupted when string value has emoticons
> -
>
> Key: IGNITE-18347
> URL: https://issues.apache.org/jira/browse/IGNITE-18347
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.14
> Environment: Apache Ignite: v2.14.0
> JDK: v1.11
> .NET Core: v6.0
>Reporter: Danut Radoaica
>Priority: Major
>
> exception: "JVM will be halted immediately due to the failure:
> [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1229361758, pageIds=[1129924291198982],
> groupName=Druid.DataAccess.DbEntities.LiveChatConversation, msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=937,
> val=6194b7bf-64a0-4b00-87eb-2660ecc3536a, hasValBytes=true], hash=1847364021,
> cacheId=-998779923"
> dto:
> [Table("LiveChatConversation")]
> private class LiveChatConversation
> {
> [Column]
> [Key]
> public Guid Id \{ get; set; }
> [Column]
> [MaxLength(255)]
> public string HelpdeskSubject \{ get; set; }
> }
> HelpdeskSubject string value: "💋"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18347) .NET: B+Tree is corrupted when string value has emoticons
[ https://issues.apache.org/jira/browse/IGNITE-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644909#comment-17644909 ] Danut Radoaica commented on IGNITE-18347: - This is from the thread dump: Thread [name="client-connector-#92%ignite-instance-354f2639-1ece-4faf-90a1-4b313d0a3088%", id=149, state=RUNNABLE, blockCnt=78, waitCnt=7893] at java.management@11.0.16/sun.management.ThreadImpl.dumpThreads0(Native Method) at java.management@11.0.16/sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:521) at java.management@11.0.16/sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:509) at app//o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1518) at app//o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:205) - locked o.a.i.i.processors.failure.FailureProcessor@1f1d9d60 at app//o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:156) at app//o.a.i.i.processors.cache.persistence.tree.BPlusTree.processFailure(BPlusTree.java:6449) at app//o.a.i.i.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6436) at app//o.a.i.i.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2149) at app//o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1698) at app//o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1681) at app//o.a.i.i.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:2762) at app//o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:425) at app//o.a.i.i.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1975) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2552) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:2012) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1831) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1704) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:481) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:441) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1149) at app//o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:617) at app//o.a.i.i.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2487) at app//o.a.i.i.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2466) at app//o.a.i.i.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1332) at app//o.a.i.i.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:867) at app//o.a.i.i.processors.platform.client.cache.ClientCachePutRequest.process(ClientCachePutRequest.java:40) at app//o.a.i.i.processors.platform.client.ClientRequestHandler.handle(ClientRequestHandler.java:101) at app//o.a.i.i.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:204) at app//o.a.i.i.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:55) at app//o.a.i.i.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279) at app//o.a.i.i.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109) at app//o.a.i.i.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97) at app//o.a.i.i.util.worker.GridWorker.run(GridWorker.java:125) at app//o.a.i.i.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70) at java.base@11.0.16/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base@11.0.16/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base@11.0.16/java.lang.Thread.run(Thread.java:829) >
[jira] [Commented] (IGNITE-18347) .NET: B+Tree is corrupted when string value has emoticons
[ https://issues.apache.org/jira/browse/IGNITE-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644895#comment-17644895 ] Anton Vinogradov commented on IGNITE-18347: --- [~dradoaica], Could you please attach the whole stacktrace including all "caused by"? > .NET: B+Tree is corrupted when string value has emoticons > - > > Key: IGNITE-18347 > URL: https://issues.apache.org/jira/browse/IGNITE-18347 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.14 > Environment: Apache Ignite: v2.14.0 > JDK: v1.11 > .NET Core: v6.0 >Reporter: Danut Radoaica >Priority: Major > > exception: "JVM will be halted immediately due to the failure: > [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class > o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is > corrupted [groupId=-1229361758, pageIds=[1129924291198982], > groupName=Druid.DataAccess.DbEntities.LiveChatConversation, msg=Runtime > failure on search row: SearchRow [key=KeyCacheObjectImpl [part=937, > val=6194b7bf-64a0-4b00-87eb-2660ecc3536a, hasValBytes=true], hash=1847364021, > cacheId=-998779923" > test string value: "💋" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17197) Change the default storage engine (for tables)
[ https://issues.apache.org/jira/browse/IGNITE-17197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev reassigned IGNITE-17197: Assignee: Aleksandr Polovtcev > Change the default storage engine (for tables) > -- > > Key: IGNITE-17197 > URL: https://issues.apache.org/jira/browse/IGNITE-17197 > Project: Ignite > Issue Type: Task >Reporter: Sergey Uttsel >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Currently the default pagememory storage doesn't support MVCC. So it doesn't > fit to the transaction protocol. Only RocksDbTableStorage supports now. So > after RocksDbTableStorage was integrated in > https://issues.apache.org/jira/browse/IGNITE-16881 the > TablesConfigurationSchema#defaultDataStorage was set to "rocksdb" and some > tests were disabled. > Need to: > # implement MvTableStorage and MvPartitionStorage by other storages. > # set TablesConfigurationSchema#defaultDataStorage to "pagememory" or other > storage. > # enable tests marked by "IGNITE-17197" > # check other places marked by IGNITE-17197" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18356) Remove already implemented issues from todo mentioning, IGNITE-17474 IGNITE-17986
Evgeny Stanilovsky created IGNITE-18356: --- Summary: Remove already implemented issues from todo mentioning, IGNITE-17474 IGNITE-17986 Key: IGNITE-18356 URL: https://issues.apache.org/jira/browse/IGNITE-18356 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 3.0.0-beta1 Reporter: Evgeny Stanilovsky Assignee: Evgeny Stanilovsky Fix For: 3.0.0-beta2 Some forgotten mentioning of already completed issues are still present in code. Need to remove them: IGNITE-17474, IGNITE-17986 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18355) [IEP-80] Remove DataRegionMetricsMXBean legacy JMX bean
Nikolay Izhikov created IGNITE-18355: Summary: [IEP-80] Remove DataRegionMetricsMXBean legacy JMX bean Key: IGNITE-18355 URL: https://issues.apache.org/jira/browse/IGNITE-18355 Project: Ignite Issue Type: Sub-task Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov Fix For: 2.15 Remove DataStorageMetricsMXBean legacy JMX bean -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18355) [IEP-80] Remove DataRegionMetricsMXBean legacy JMX bean
[ https://issues.apache.org/jira/browse/IGNITE-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-18355: - Description: Remove DataRegionMetricsMXBean legacy JMX bean (was: Remove DataStorageMetricsMXBean legacy JMX bean) > [IEP-80] Remove DataRegionMetricsMXBean legacy JMX bean > --- > > Key: IGNITE-18355 > URL: https://issues.apache.org/jira/browse/IGNITE-18355 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-80, ise > Fix For: 2.15 > > > Remove DataRegionMetricsMXBean legacy JMX bean -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18354) Update apache ignite docs to replace deprecated info from Ignite.active() to Ignite.cluster().state(ClusterState.ACTIVE)
Julia Bakulina created IGNITE-18354: --- Summary: Update apache ignite docs to replace deprecated info from Ignite.active() to Ignite.cluster().state(ClusterState.ACTIVE) Key: IGNITE-18354 URL: https://issues.apache.org/jira/browse/IGNITE-18354 Project: Ignite Issue Type: Improvement Reporter: Julia Bakulina Currently, some classes contain outdated ignite apache docs info re Ignite.active() and Ignite.active(boolean active). active() and active(boolean active) are deprecated since 2018 thus the docs throughout the project should be updated accordingly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18346) .NET return Ignite version with a wrong timestamp part
[
https://issues.apache.org/jira/browse/IGNITE-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-18346:
-
Fix Version/s: 2.15
> .NET return Ignite version with a wrong timestamp part
> --
>
> Key: IGNITE-18346
> URL: https://issues.apache.org/jira/browse/IGNITE-18346
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.14
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.15
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following code reproduces the issue:
> {code:c#}
> var node = Ignition.Start(cfg);
> Console.WriteLine("Version: " + node.GetVersion());
> {code}
> For version 2.14:
> {noformat}
> Expected: 2.14.0#20220929-sha1:951e8deb
> Actual: 2.14.0#19700102-sha1:951e8deb
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17920) Develop docker-compose file for Ignite cluster
[ https://issues.apache.org/jira/browse/IGNITE-17920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644752#comment-17644752 ] Mikhail Pochatkin commented on IGNITE-17920: LGTM > Develop docker-compose file for Ignite cluster > -- > > Key: IGNITE-17920 > URL: https://issues.apache.org/jira/browse/IGNITE-17920 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Aleksandr >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > > The simplest pattern for docker distribution is working: > - pull docker image > - run docker container > - connect to the node from the developer machine > But there is another case of usage: > - get the compose file that forms the cluster (3 nodes) > - adjust the compose file if needed: change the cluster name, number of > nodes, etc > - docker compose up > - connect to the formed cluster from the developer machine > The second case is more likely to be used by devs, we have to develop the > compose file that will be mentioned in examples/docs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18092) Fix zip distribution name providing to sign and checksum tasks
[ https://issues.apache.org/jira/browse/IGNITE-18092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644753#comment-17644753 ] Mikhail Pochatkin commented on IGNITE-18092: LGTM > Fix zip distribution name providing to sign and checksum tasks > -- > > Key: IGNITE-18092 > URL: https://issues.apache.org/jira/browse/IGNITE-18092 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Currently, createChecksums tasks in the packaging module have hard-coded zip > path and name of artifact. Need to remove hard-coded name of zip distribution. > Also, all other packaging-related tasks should be checked for distribution > name usage. Probably, it is a good idea to separate distribution name to some > global value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18353) Add specific version of tox in order to fix strange behaviour of new version
[ https://issues.apache.org/jira/browse/IGNITE-18353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644746#comment-17644746 ] Anton Vinogradov commented on IGNITE-18353: --- Merged to the master. > Add specific version of tox in order to fix strange behaviour of new version > > > Key: IGNITE-18353 > URL: https://issues.apache.org/jira/browse/IGNITE-18353 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.15 > > Time Spent: 20m > Remaining Estimate: 0h > > Unexpected fails on tox 4.0, need to fix at 3.27.1 for now -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-18353) Add specific version of tox in order to fix strange behaviour of new version
[ https://issues.apache.org/jira/browse/IGNITE-18353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-18353. --- Resolution: Fixed > Add specific version of tox in order to fix strange behaviour of new version > > > Key: IGNITE-18353 > URL: https://issues.apache.org/jira/browse/IGNITE-18353 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.15 > > Time Spent: 20m > Remaining Estimate: 0h > > Unexpected fails on tox 4.0, need to fix at 3.27.1 for now -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18353) Add specific version of tox in order to fix strange behaviour of new version
[ https://issues.apache.org/jira/browse/IGNITE-18353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-18353: -- Fix Version/s: 2.15 > Add specific version of tox in order to fix strange behaviour of new version > > > Key: IGNITE-18353 > URL: https://issues.apache.org/jira/browse/IGNITE-18353 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.15 > > Time Spent: 10m > Remaining Estimate: 0h > > Unexpected fails on tox 4.0, need to fix at 3.27.1 for now -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18353) Add specific version of tox in order to fix strange behaviour of new version
Anton Vinogradov created IGNITE-18353: - Summary: Add specific version of tox in order to fix strange behaviour of new version Key: IGNITE-18353 URL: https://issues.apache.org/jira/browse/IGNITE-18353 Project: Ignite Issue Type: Improvement Reporter: Anton Vinogradov Assignee: Anton Vinogradov Unexpected fails on tox 4.0, need to fix at 3.27.1 for now -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18304) [IEP-94] Remove daemon node
[ https://issues.apache.org/jira/browse/IGNITE-18304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-18304: - Fix Version/s: 2.15 > [IEP-94] Remove daemon node > --- > > Key: IGNITE-18304 > URL: https://issues.apache.org/jira/browse/IGNITE-18304 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-94 > Fix For: 2.15 > > Time Spent: 20m > Remaining Estimate: 0h > > We can remove daemon node and related code because they no longer used -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18304) [IEP-94] Remove daemon node
[ https://issues.apache.org/jira/browse/IGNITE-18304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-18304: - Labels: IEP-80 IEP-94 (was: IEP-94) > [IEP-94] Remove daemon node > --- > > Key: IGNITE-18304 > URL: https://issues.apache.org/jira/browse/IGNITE-18304 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-80, IEP-94 > Fix For: 2.15 > > Time Spent: 20m > Remaining Estimate: 0h > > We can remove daemon node and related code because they no longer used -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18147) CLI hangs on slow dns resolution
[ https://issues.apache.org/jira/browse/IGNITE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644731#comment-17644731 ] Roman Puchkovskiy commented on IGNITE-18147: The patch looks good to me > CLI hangs on slow dns resolution > > > Key: IGNITE-18147 > URL: https://issues.apache.org/jira/browse/IGNITE-18147 > Project: Ignite > Issue Type: Task > Components: cli, rest >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Time Spent: 10m > Remaining Estimate: 0h > > Micronaut goes to the Internet at the start. In case there is no internet on > the machine it uses some fall-back logic. We have to force micronaut to use > this logic by default because there is no reason to go to the Internet for > the CLI application. > The same should be done for REST Component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18147) CLI hangs on slow dns resolution
[ https://issues.apache.org/jira/browse/IGNITE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-18147: --- Reviewer: Roman Puchkovskiy > CLI hangs on slow dns resolution > > > Key: IGNITE-18147 > URL: https://issues.apache.org/jira/browse/IGNITE-18147 > Project: Ignite > Issue Type: Task > Components: cli, rest >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Time Spent: 10m > Remaining Estimate: 0h > > Micronaut goes to the Internet at the start. In case there is no internet on > the machine it uses some fall-back logic. We have to force micronaut to use > this logic by default because there is no reason to go to the Internet for > the CLI application. > The same should be done for REST Component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18340) Gradle build doesn't produce OpenAPI spec
[ https://issues.apache.org/jira/browse/IGNITE-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644722#comment-17644722 ] Mikhail Pochatkin commented on IGNITE-18340: LGTM > Gradle build doesn't produce OpenAPI spec > - > > Key: IGNITE-18340 > URL: https://issues.apache.org/jira/browse/IGNITE-18340 > Project: Ignite > Issue Type: Bug > Components: rest >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Building :ignite-rest:classes should produce openapi/openapi.yaml file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18101) Add help for SQL commands
[
https://issues.apache.org/jira/browse/IGNITE-18101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644709#comment-17644709
]
Vyacheslav Koptilin commented on IGNITE-18101:
--
Hello [~ivan.gagarkin],
In general, this patch looks good to me. However, I agree with
[~aleksandr.pakhomov]'s comment.
> Add help for SQL commands
> -
>
> Key: IGNITE-18101
> URL: https://issues.apache.org/jira/browse/IGNITE-18101
> Project: Ignite
> Issue Type: Improvement
> Components: cli
>Reporter: Yury Yudin
>Assignee: Ivan Gagarkin
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> help in SQL REPL should actually give details about the syntax of SQL
> commands.
> like:
> > help create table
> {color:#00}CREATE TABLE _table_name_ (
> \{_}column1 datatype{_},
> \{_}column2 datatype{_},
> \{_}column3 datatype{_},
>
> ); {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18303) Calcite engine. Fix nanoseconds flakyness in LocalDateTimeSupportTest
[ https://issues.apache.org/jira/browse/IGNITE-18303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-18303: --- Labels: calcite3-required (was: ) > Calcite engine. Fix nanoseconds flakyness in LocalDateTimeSupportTest > -- > > Key: IGNITE-18303 > URL: https://issues.apache.org/jira/browse/IGNITE-18303 > Project: Ignite > Issue Type: Test >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Minor > Labels: calcite3-required > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18282) Illegal use of dynamic parameter exception in SQL functions
[
https://issues.apache.org/jira/browse/IGNITE-18282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644689#comment-17644689
]
Konstantin Orlov commented on IGNITE-18282:
---
[~jooger], I left a comment. IMO, more research is need on this problem.
> Illegal use of dynamic parameter exception in SQL functions
> ---
>
> Key: IGNITE-18282
> URL: https://issues.apache.org/jira/browse/IGNITE-18282
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Tupitsyn
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *Query*
> {code}
> select Power(_T0.KEY, ?) from PUBLIC.TBL_DOUBLE as _T0
> {code}
> *Result*
> {code}
> org.apache.calcite.runtime.CalciteContextException: At line 1, column 27:
> Illegal use of dynamic parameter
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at
> org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:505)
> at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:932)
> at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:917)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError(SqlValidatorImpl.java:5362)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.inferUnknownTypes(SqlValidatorImpl.java:1982)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.inferUnknownTypes(SqlValidatorImpl.java:2064)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.inferUnknownTypes(SqlValidatorImpl.java:2064)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.expandSelectItem(SqlValidatorImpl.java:462)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelectList(SqlValidatorImpl.java:4505)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelect(SqlValidatorImpl.java:3710)
> at
> org.apache.ignite.internal.sql.engine.prepare.IgniteSqlValidator.validateSelect(IgniteSqlValidator.java:207)
> at
> org.apache.calcite.sql.validate.SelectNamespace.validateImpl(SelectNamespace.java:64)
> at
> org.apache.calcite.sql.validate.AbstractNamespace.validate(AbstractNamespace.java:89)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace(SqlValidatorImpl.java:1107)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery(SqlValidatorImpl.java:1078)
> at org.apache.calcite.sql.SqlSelect.validate(SqlSelect.java:248)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateScopedExpression(SqlValidatorImpl.java:1053)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validate(SqlValidatorImpl.java:759)
> at
> org.apache.ignite.internal.sql.engine.prepare.IgnitePlanner.validateAndGetTypeMetadata(IgnitePlanner.java:210)
> at
> org.apache.ignite.internal.sql.engine.prepare.PrepareServiceImpl.lambda$prepareQuery$1(PrepareServiceImpl.java:227)
> at
> java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Illegal use
> of dynamic parameter
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at
> org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:505)
> at org.apache.calcite.runtime.Resources$ExInst.ex(Resources.java:599)
> ... 23 more
> {code}
> * The same applies to all other functions, like *trim, instr, ln, concat*
> * This query works in Ignite 2.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18211) Sql. Adjust Affinity distribution to the new colocation rules
[
https://issues.apache.org/jira/browse/IGNITE-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18211:
---
Description:
Need to adjust affinity function to be prepared to upcoming concept of
Distribution Zones.
Following changes are required:
* AffinityFunction has to be updated with id (name) of the distribution zone
* (De-)Serialization of the DistributionFunction need to be adjusted as well
* Integration with table
Besides, it looks like the following condition is no more valid, thus should be
removed:
{code:java}
//
org.apache.ignite.internal.sql.engine.trait.TraitUtils#convertDistribution
if (toTrait.function().affinity() && toTrait.getKeys().size() > 1) {
return null;
}
{code}
see:
org.apache.ignite.internal.sql.engine.planner.JoinColocationPlannerTest
org.apache.ignite.internal.sql.engine.planner.SetOpPlannerTest
org.apache.ignite.internal.sqle.ngine.ItSetOpTest
was:
Need to adjust affinity function to be prepared to upcoming concept of
Distribution Zones.
Following changes are required:
* AffinityFunction has to be updated with id (name) of the distribution zone
* (De-)Serialization of the DistributionFunction need to be adjusted as well
* Integration with table
Besides, it looks like the following condition is no more valid, thus should be
removed:
{code:java}
//
org.apache.ignite.internal.sql.engine.trait.TraitUtils#convertDistribution
if (toTrait.function().affinity() && toTrait.getKeys().size() > 1) {
return null;
}
{code}
see: org.apache.ignite.internal.sql.engine.planner.JoinColocationPlannerTest
and org.apache.ignite.internal.sqle.ngine.ItSetOpTest
> Sql. Adjust Affinity distribution to the new colocation rules
> -
>
> Key: IGNITE-18211
> URL: https://issues.apache.org/jira/browse/IGNITE-18211
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> Need to adjust affinity function to be prepared to upcoming concept of
> Distribution Zones.
> Following changes are required:
> * AffinityFunction has to be updated with id (name) of the distribution zone
> * (De-)Serialization of the DistributionFunction need to be adjusted as well
> * Integration with table
> Besides, it looks like the following condition is no more valid, thus should
> be removed:
> {code:java}
> //
> org.apache.ignite.internal.sql.engine.trait.TraitUtils#convertDistribution
> if (toTrait.function().affinity() && toTrait.getKeys().size() > 1) {
> return null;
> }
> {code}
> see:
> org.apache.ignite.internal.sql.engine.planner.JoinColocationPlannerTest
> org.apache.ignite.internal.sql.engine.planner.SetOpPlannerTest
> org.apache.ignite.internal.sqle.ngine.ItSetOpTest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18211) Sql. Adjust Affinity distribution to the new colocation rules
[
https://issues.apache.org/jira/browse/IGNITE-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18211:
---
Description:
Need to adjust affinity function to be prepared to upcoming concept of
Distribution Zones.
Following changes are required:
* AffinityFunction has to be updated with id (name) of the distribution zone
* (De-)Serialization of the DistributionFunction need to be adjusted as well
* Integration with table
Besides, it looks like the following condition is no more valid, thus should be
removed:
{code:java}
//
org.apache.ignite.internal.sql.engine.trait.TraitUtils#convertDistribution
if (toTrait.function().affinity() && toTrait.getKeys().size() > 1) {
return null;
}
{code}
see: org.apache.ignite.internal.sql.engine.planner.JoinColocationPlannerTest
and org.apache.ignite.internal.sqle.ngine.ItSetOpTest
was:
Need to adjust affinity function to be prepared to upcoming concept of
[Distribution Zones|https://issues.apache.org/jira/browse/IGNITE-17924].
Following changes are required:
* AffinityFunction has to be updated with id (name) of the distribution zone
* (De-)Serialization of the DistributionFunction need to be adjusted as well
* Integration with table
Besides, it looks like the following condition is no more valid, thus should be
removed:
{code:java}
//
org.apache.ignite.internal.sql.engine.trait.TraitUtils#convertDistribution
if (toTrait.function().affinity() && toTrait.getKeys().size() > 1) {
return null;
}
{code}
see: org.apache.ignite.internal.sql.engine.planner.JoinColocationPlannerTest
> Sql. Adjust Affinity distribution to the new colocation rules
> -
>
> Key: IGNITE-18211
> URL: https://issues.apache.org/jira/browse/IGNITE-18211
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> Need to adjust affinity function to be prepared to upcoming concept of
> Distribution Zones.
> Following changes are required:
> * AffinityFunction has to be updated with id (name) of the distribution zone
> * (De-)Serialization of the DistributionFunction need to be adjusted as well
> * Integration with table
> Besides, it looks like the following condition is no more valid, thus should
> be removed:
> {code:java}
> //
> org.apache.ignite.internal.sql.engine.trait.TraitUtils#convertDistribution
> if (toTrait.function().affinity() && toTrait.getKeys().size() > 1) {
> return null;
> }
> {code}
> see: org.apache.ignite.internal.sql.engine.planner.JoinColocationPlannerTest
> and org.apache.ignite.internal.sqle.ngine.ItSetOpTest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-17902) Ignite 3. SQL. Dynamic parameter type can't be inferred for the most of built-in SQL functions
[
https://issues.apache.org/jira/browse/IGNITE-17902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich resolved IGNITE-17902.
Resolution: Duplicate
> Ignite 3. SQL. Dynamic parameter type can't be inferred for the most of
> built-in SQL functions
> --
>
> Key: IGNITE-17902
> URL: https://issues.apache.org/jira/browse/IGNITE-17902
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Yury Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> Queries like:
> {code:java}
> SELECT LOWER(?)
> {code}
> Fails with:
> {noformat}
> Caused by: org.apache.calcite.runtime.CalciteContextException: At line 1,
> column 14: Illegal use of dynamic parameter
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:505)
> at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:932)
> at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:917)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError(SqlValidatorImpl.java:5266)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.inferUnknownTypes(SqlValidatorImpl.java:1975)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.inferUnknownTypes(IgniteSqlValidator.java:534)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.inferUnknownTypes(SqlValidatorImpl.java:2057)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.inferUnknownTypes(IgniteSqlValidator.java:534)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.expandSelectItem(SqlValidatorImpl.java:461)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelectList(SqlValidatorImpl.java:4409)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelect(SqlValidatorImpl.java:3652){noformat}
> We can try to infer types by type checker for SQL functions with
> empty {{{}operandTypeInference{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18342) Use Auto Service library to generate SPI files
[ https://issues.apache.org/jira/browse/IGNITE-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644668#comment-17644668 ] Ivan Bessonov commented on IGNITE-18342: Looks good to me, thank you for the improvement! > Use Auto Service library to generate SPI files > -- > > Key: IGNITE-18342 > URL: https://issues.apache.org/jira/browse/IGNITE-18342 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > We have a lot of Java SPI providers which have to manually be added to the > META-INF folder. I think this is inconvenient and could be automated using > the [Auto Service|https://github.com/google/auto/tree/main/service] library. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18342) Use Auto Service library to generate SPI files
[ https://issues.apache.org/jira/browse/IGNITE-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-18342: --- Reviewer: Ivan Bessonov > Use Auto Service library to generate SPI files > -- > > Key: IGNITE-18342 > URL: https://issues.apache.org/jira/browse/IGNITE-18342 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > We have a lot of Java SPI providers which have to manually be added to the > META-INF folder. I think this is inconvenient and could be automated using > the [Auto Service|https://github.com/google/auto/tree/main/service] library. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18044) ItIgniteNodeRestartTest#testTwoNodesRestartDirect is failed after schema recovery fix.
[
https://issues.apache.org/jira/browse/IGNITE-18044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov reassigned IGNITE-18044:
--
Assignee: Vladislav Pyatkov
> ItIgniteNodeRestartTest#testTwoNodesRestartDirect is failed after schema
> recovery fix.
> --
>
> Key: IGNITE-18044
> URL: https://issues.apache.org/jira/browse/IGNITE-18044
> Project: Ignite
> Issue Type: Bug
>Reporter: Evgeny Stanilovsky
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> In [1] was introduced schema recovery fix, after the fix test [2] is failing
> with :
> {noformat}
> Caused by: java.lang.AssertionError: Mismatched transaction id,
> expectedTxId={000d780b-10c0--face-5ad039564953},
> actualTxId={000d780a-a0fd--face-5ad039564953}
> {noformat}
> [1] https://issues.apache.org/jira/browse/IGNITE-17986
> [2] ItIgniteNodeRestartTest#testTwoNodesRestartDirect
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
