[jira] [Commented] (IGNITE-19544) Thin 3.0: Data Streamer with Receiver
[ https://issues.apache.org/jira/browse/IGNITE-19544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849246#comment-17849246 ] Pavel Tupitsyn commented on IGNITE-19544: - Merged to main: [d3ab33124127dd18f36727148100d632fffbd02e|https://github.com/apache/ignite-3/commit/d3ab33124127dd18f36727148100d632fffbd02e] > Thin 3.0: Data Streamer with Receiver > - > > Key: IGNITE-19544 > URL: https://issues.apache.org/jira/browse/IGNITE-19544 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-102, iep-121, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Implement data streamer with receiver in Java client - see > [IEP-121|https://cwiki.apache.org/confluence/display/IGNITE/IEP-121%3A+Data+Streamer+with+Receiver] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19544) Thin 3.0: Data Streamer with Receiver
[ https://issues.apache.org/jira/browse/IGNITE-19544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-19544: Ignite Flags: Docs Required,Release Notes Required Release Note: Java thin: Added Data Streamer with Receiver > Thin 3.0: Data Streamer with Receiver > - > > Key: IGNITE-19544 > URL: https://issues.apache.org/jira/browse/IGNITE-19544 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-102, iep-121, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Implement data streamer with receiver in Java client - see > [IEP-121|https://cwiki.apache.org/confluence/display/IGNITE/IEP-121%3A+Data+Streamer+with+Receiver] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22318) Data Streamer: Optimize receiver task invocation
[ https://issues.apache.org/jira/browse/IGNITE-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22318: Description: *ClientStreamerWithReceiverBatchSendRequest.java* uses a Compute task to execute the receiver. This task is instantiated every time, which might be expensive. See if we can cache it somehow. > Data Streamer: Optimize receiver task invocation > > > Key: IGNITE-22318 > URL: https://issues.apache.org/jira/browse/IGNITE-22318 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > > *ClientStreamerWithReceiverBatchSendRequest.java* uses a Compute task to > execute the receiver. This task is instantiated every time, which might be > expensive. See if we can cache it somehow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22318) Data Streamer: Optimize receiver task invocation
[ https://issues.apache.org/jira/browse/IGNITE-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22318: Description: *ClientStreamerWithReceiverBatchSendRequest* uses a Compute task to execute the receiver. This task is instantiated every time, which might be expensive. See if we can cache it somehow. (was: *ClientStreamerWithReceiverBatchSendRequest.java* uses a Compute task to execute the receiver. This task is instantiated every time, which might be expensive. See if we can cache it somehow.) > Data Streamer: Optimize receiver task invocation > > > Key: IGNITE-22318 > URL: https://issues.apache.org/jira/browse/IGNITE-22318 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > > *ClientStreamerWithReceiverBatchSendRequest* uses a Compute task to execute > the receiver. This task is instantiated every time, which might be expensive. > See if we can cache it somehow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22318) Data Streamer: Optimize receiver task invocation
Pavel Tupitsyn created IGNITE-22318: --- Summary: Data Streamer: Optimize receiver task invocation Key: IGNITE-22318 URL: https://issues.apache.org/jira/browse/IGNITE-22318 Project: Ignite Issue Type: Improvement Components: streaming Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22308) .NET: Windows build fails due to vulnerable Newtonsoft.Json version
[
https://issues.apache.org/jira/browse/IGNITE-22308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848834#comment-17848834
]
Pavel Tupitsyn commented on IGNITE-22308:
-
Merged to master:
[a2cd44cd7873f5104253434f15eb740d98f20a51|https://github.com/apache/ignite/commit/a2cd44cd7873f5104253434f15eb740d98f20a51]
> .NET: Windows build fails due to vulnerable Newtonsoft.Json version
> ---
>
> Key: IGNITE-22308
> URL: https://issues.apache.org/jira/browse/IGNITE-22308
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> C:\opt\BuildAgent\work\cfbab08dcf053850\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj
> : error NU1903: Warning As Error: Package 'Newtonsoft.Json' 12.0.3 has a
> known high severity vulnerability,
> https://github.com/advisories/GHSA-5crp-9r3c-p9vr
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22308) .NET: Windows build fails due to vulnerable Newtonsoft.Json version
[
https://issues.apache.org/jira/browse/IGNITE-22308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22308:
Ignite Flags: (was: Docs Required,Release Notes Required)
> .NET: Windows build fails due to vulnerable Newtonsoft.Json version
> ---
>
> Key: IGNITE-22308
> URL: https://issues.apache.org/jira/browse/IGNITE-22308
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> C:\opt\BuildAgent\work\cfbab08dcf053850\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj
> : error NU1903: Warning As Error: Package 'Newtonsoft.Json' 12.0.3 has a
> known high severity vulnerability,
> https://github.com/advisories/GHSA-5crp-9r3c-p9vr
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22308) .NET: Windows build fails due to vulnerable Newtonsoft.Json version
[
https://issues.apache.org/jira/browse/IGNITE-22308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848830#comment-17848830
]
Pavel Tupitsyn commented on IGNITE-22308:
-
Build fixed:
*
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetWindows?branch=pull%2F11359%2Fhead=overview=builds
*
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetCoreLinux?branch=pull%2F11359%2Fhead=overview=builds
> .NET: Windows build fails due to vulnerable Newtonsoft.Json version
> ---
>
> Key: IGNITE-22308
> URL: https://issues.apache.org/jira/browse/IGNITE-22308
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> C:\opt\BuildAgent\work\cfbab08dcf053850\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj
> : error NU1903: Warning As Error: Package 'Newtonsoft.Json' 12.0.3 has a
> known high severity vulnerability,
> https://github.com/advisories/GHSA-5crp-9r3c-p9vr
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22308) .NET: Windows build fails due to vulnerable Newtonsoft.Json version
[
https://issues.apache.org/jira/browse/IGNITE-22308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22308:
Description:
{code}
C:\opt\BuildAgent\work\cfbab08dcf053850\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj
: error NU1903: Warning As Error: Package 'Newtonsoft.Json' 12.0.3 has a known
high severity vulnerability, https://github.com/advisories/GHSA-5crp-9r3c-p9vr
{code}
> .NET: Windows build fails due to vulnerable Newtonsoft.Json version
> ---
>
> Key: IGNITE-22308
> URL: https://issues.apache.org/jira/browse/IGNITE-22308
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.17
>
>
> {code}
> C:\opt\BuildAgent\work\cfbab08dcf053850\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj
> : error NU1903: Warning As Error: Package 'Newtonsoft.Json' 12.0.3 has a
> known high severity vulnerability,
> https://github.com/advisories/GHSA-5crp-9r3c-p9vr
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22308) .NET: Windows build fails due to vulnerable Newtonsoft.Json version
Pavel Tupitsyn created IGNITE-22308: --- Summary: .NET: Windows build fails due to vulnerable Newtonsoft.Json version Key: IGNITE-22308 URL: https://issues.apache.org/jira/browse/IGNITE-22308 Project: Ignite Issue Type: Bug Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22304) Compute queue executor does not catch Throwable from user code
[ https://issues.apache.org/jira/browse/IGNITE-22304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22304: Description: See https://github.com/apache/ignite-3/blob/560c6da4afb067abe628d5d58872d9111ba477e1/modules/compute/src/main/java/org/apache/ignite/internal/compute/queue/QueueEntry.java#L78 We catch *Exception* instead of *Throwable*, so a job that throws certain types of errors can break Compute. > Compute queue executor does not catch Throwable from user code > -- > > Key: IGNITE-22304 > URL: https://issues.apache.org/jira/browse/IGNITE-22304 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Pavel Tupitsyn >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See > https://github.com/apache/ignite-3/blob/560c6da4afb067abe628d5d58872d9111ba477e1/modules/compute/src/main/java/org/apache/ignite/internal/compute/queue/QueueEntry.java#L78 > We catch *Exception* instead of *Throwable*, so a job that throws certain > types of errors can break Compute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22304) Compute queue executor does not catch Throwable from user code
Pavel Tupitsyn created IGNITE-22304: --- Summary: Compute queue executor does not catch Throwable from user code Key: IGNITE-22304 URL: https://issues.apache.org/jira/browse/IGNITE-22304 Project: Ignite Issue Type: Bug Components: compute Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22302) Thin 3.0: Data Streamer with Receiver - add resultSubscriber support
[ https://issues.apache.org/jira/browse/IGNITE-22302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22302: Description: See TODOs with this ticket number. > Thin 3.0: Data Streamer with Receiver - add resultSubscriber support > > > Key: IGNITE-22302 > URL: https://issues.apache.org/jira/browse/IGNITE-22302 > Project: Ignite > Issue Type: Improvement > Components: streaming, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > See TODOs with this ticket number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22302) Thin 3.0: Data Streamer with Receiver - add resultSubscriber support
Pavel Tupitsyn created IGNITE-22302: --- Summary: Thin 3.0: Data Streamer with Receiver - add resultSubscriber support Key: IGNITE-22302 URL: https://issues.apache.org/jira/browse/IGNITE-22302 Project: Ignite Issue Type: Improvement Components: streaming, thin client Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22287) Remove decimal scale from packObjectAsBinaryTuple
[ https://issues.apache.org/jira/browse/IGNITE-22287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22287: Description: IGNITE-21745 adds decimal scale as part of the binary tuple payload. We no longed need to send it separately in *ClientBinaryTupleUtils#appendTypeAndScale*. > Remove decimal scale from packObjectAsBinaryTuple > - > > Key: IGNITE-22287 > URL: https://issues.apache.org/jira/browse/IGNITE-22287 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > IGNITE-21745 adds decimal scale as part of the binary tuple payload. We no > longed need to send it separately in > *ClientBinaryTupleUtils#appendTypeAndScale*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22287) Remove decimal scale from packObjectAsBinaryTuple
Pavel Tupitsyn created IGNITE-22287: --- Summary: Remove decimal scale from packObjectAsBinaryTuple Key: IGNITE-22287 URL: https://issues.apache.org/jira/browse/IGNITE-22287 Project: Ignite Issue Type: Improvement Components: thin client Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22124) Java Thin 3.0: Implement MapReduce API
[
https://issues.apache.org/jira/browse/IGNITE-22124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22124:
Affects Version/s: 3.0.0-beta1
> Java Thin 3.0: Implement MapReduce API
> --
>
> Key: IGNITE-22124
> URL: https://issues.apache.org/jira/browse/IGNITE-22124
> Project: Ignite
> Issue Type: Improvement
> Components: compute, thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Kolodin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Implement {{ClientTaskExecution}} in Java client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22124) Java Thin 3.0: Implement MapReduce API
[
https://issues.apache.org/jira/browse/IGNITE-22124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22124:
Fix Version/s: 3.0.0-beta2
> Java Thin 3.0: Implement MapReduce API
> --
>
> Key: IGNITE-22124
> URL: https://issues.apache.org/jira/browse/IGNITE-22124
> Project: Ignite
> Issue Type: Improvement
> Components: compute, thin client
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Kolodin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Implement {{ClientTaskExecution}} in Java client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22124) Java Thin 3.0: Implement MapReduce API
[
https://issues.apache.org/jira/browse/IGNITE-22124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847877#comment-17847877
]
Pavel Tupitsyn commented on IGNITE-22124:
-
Merged to main:
[c56f077040e736b087ad239c688f43897cc096f7|https://github.com/apache/ignite-3/commit/c56f077040e736b087ad239c688f43897cc096f7]
> Java Thin 3.0: Implement MapReduce API
> --
>
> Key: IGNITE-22124
> URL: https://issues.apache.org/jira/browse/IGNITE-22124
> Project: Ignite
> Issue Type: Improvement
> Components: compute, thin client
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Kolodin
>Priority: Major
> Labels: ignite-3
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Implement {{ClientTaskExecution}} in Java client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22274) Remove o.a.i.catalog.Options
[ https://issues.apache.org/jira/browse/IGNITE-22274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-22274: --- Assignee: (was: Pavel Tupitsyn) > Remove o.a.i.catalog.Options > > > Key: IGNITE-22274 > URL: https://issues.apache.org/jira/browse/IGNITE-22274 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *org.apache.ignite.catalog.Options* affects generated SQL, but it provides no > value to the user. SQL is an implementation detail of Catalog API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22272) Rework Catalog API
[ https://issues.apache.org/jira/browse/IGNITE-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-22272: --- Assignee: (was: Pavel Tupitsyn) > Rework Catalog API > -- > > Key: IGNITE-22272 > URL: https://issues.apache.org/jira/browse/IGNITE-22272 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Pavel Tupitsyn >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > * Do not return a Query that has to be executed, run it immediately. For > example: *Table table = catalog.createTable(Pojo.class)* > * All methods should be async-first > * Rename *create* to *createTable* (recordClass and KV methods) > * all *createTable* methods should return a *Table*. Especially important for > record and KV cases, where the resulting name is not obvious -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22285) Embedded Data Streamer with Receiver
[ https://issues.apache.org/jira/browse/IGNITE-22285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22285: Description: Implement data streamer with receiver in embedded Java API - see IEP-121 > Embedded Data Streamer with Receiver > > > Key: IGNITE-22285 > URL: https://issues.apache.org/jira/browse/IGNITE-22285 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-102, iep-121, ignite-3 > Fix For: 3.0.0-beta2 > > > Implement data streamer with receiver in embedded Java API - see IEP-121 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22285) Embedded Data Streamer with Receiver
[ https://issues.apache.org/jira/browse/IGNITE-22285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22285: Description: Implement data streamer with receiver in embedded Java API - see [IEP-121|https://cwiki.apache.org/confluence/display/IGNITE/IEP-121%3A+Data+Streamer+with+Receiver] (was: Implement data streamer with receiver in embedded Java API - see IEP-121) > Embedded Data Streamer with Receiver > > > Key: IGNITE-22285 > URL: https://issues.apache.org/jira/browse/IGNITE-22285 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-102, iep-121, ignite-3 > Fix For: 3.0.0-beta2 > > > Implement data streamer with receiver in embedded Java API - see > [IEP-121|https://cwiki.apache.org/confluence/display/IGNITE/IEP-121%3A+Data+Streamer+with+Receiver] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22285) Embedded Data Streamer with Receiver
Pavel Tupitsyn created IGNITE-22285: --- Summary: Embedded Data Streamer with Receiver Key: IGNITE-22285 URL: https://issues.apache.org/jira/browse/IGNITE-22285 Project: Ignite Issue Type: Improvement Components: streaming Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22284) .NET: Thin 3.0: Tests fail on macOS
[
https://issues.apache.org/jira/browse/IGNITE-22284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22284:
Description:
There are ~200 .NET test failures on macOS, mostly caused by *FakeServer*:
{code}
System.Net.Sockets.SocketException : Socket is not connected
at
System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError
error, String callerName)
at System.Net.Sockets.Socket.Shutdown(SocketShutdown how)
at System.Net.Sockets.Socket.Disconnect(Boolean reuseSocket)
at Apache.Ignite.Tests.IgniteServerBase.Dispose(Boolean disposing) in
/Users/ptupitsyn/w/ignite-3/modules/platforms/dotnet/Apache.Ignite.Tests/IgniteServerBase.cs:line
128
at Apache.Ignite.Tests.IgniteServerBase.Dispose()
{code}
Other failures are caused by SSL protocol names.
was:
There are ~200 .NET test failures on macOS, mostly caused by FakeServer:
{code}
System.Net.Sockets.SocketException : Socket is not connected
at
System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError
error, String callerName)
at System.Net.Sockets.Socket.Shutdown(SocketShutdown how)
at System.Net.Sockets.Socket.Disconnect(Boolean reuseSocket)
at Apache.Ignite.Tests.IgniteServerBase.Dispose(Boolean disposing) in
/Users/ptupitsyn/w/ignite-3/modules/platforms/dotnet/Apache.Ignite.Tests/IgniteServerBase.cs:line
128
at Apache.Ignite.Tests.IgniteServerBase.Dispose()
{code}
> .NET: Thin 3.0: Tests fail on macOS
> ---
>
> Key: IGNITE-22284
> URL: https://issues.apache.org/jira/browse/IGNITE-22284
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: ignite-3
>
> There are ~200 .NET test failures on macOS, mostly caused by *FakeServer*:
> {code}
> System.Net.Sockets.SocketException : Socket is not connected
>at
> System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError
> error, String callerName)
>at System.Net.Sockets.Socket.Shutdown(SocketShutdown how)
>at System.Net.Sockets.Socket.Disconnect(Boolean reuseSocket)
>at Apache.Ignite.Tests.IgniteServerBase.Dispose(Boolean disposing) in
> /Users/ptupitsyn/w/ignite-3/modules/platforms/dotnet/Apache.Ignite.Tests/IgniteServerBase.cs:line
> 128
>at Apache.Ignite.Tests.IgniteServerBase.Dispose()
> {code}
> Other failures are caused by SSL protocol names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22284) .NET: Thin 3.0: Tests fail on macOS
[
https://issues.apache.org/jira/browse/IGNITE-22284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22284:
Ignite Flags: (was: Docs Required,Release Notes Required)
> .NET: Thin 3.0: Tests fail on macOS
> ---
>
> Key: IGNITE-22284
> URL: https://issues.apache.org/jira/browse/IGNITE-22284
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: ignite-3
>
> There are ~200 .NET test failures on macOS, mostly caused by FakeServer:
> {code}
> System.Net.Sockets.SocketException : Socket is not connected
>at
> System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError
> error, String callerName)
>at System.Net.Sockets.Socket.Shutdown(SocketShutdown how)
>at System.Net.Sockets.Socket.Disconnect(Boolean reuseSocket)
>at Apache.Ignite.Tests.IgniteServerBase.Dispose(Boolean disposing) in
> /Users/ptupitsyn/w/ignite-3/modules/platforms/dotnet/Apache.Ignite.Tests/IgniteServerBase.cs:line
> 128
>at Apache.Ignite.Tests.IgniteServerBase.Dispose()
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22284) .NET: Thin 3.0: Tests fail on macOS
Pavel Tupitsyn created IGNITE-22284:
---
Summary: .NET: Thin 3.0: Tests fail on macOS
Key: IGNITE-22284
URL: https://issues.apache.org/jira/browse/IGNITE-22284
Project: Ignite
Issue Type: Bug
Components: platforms, thin client
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
There are ~200 .NET test failures on macOS, mostly caused by FakeServer:
{code}
System.Net.Sockets.SocketException : Socket is not connected
at
System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError
error, String callerName)
at System.Net.Sockets.Socket.Shutdown(SocketShutdown how)
at System.Net.Sockets.Socket.Disconnect(Boolean reuseSocket)
at Apache.Ignite.Tests.IgniteServerBase.Dispose(Boolean disposing) in
/Users/ptupitsyn/w/ignite-3/modules/platforms/dotnet/Apache.Ignite.Tests/IgniteServerBase.cs:line
128
at Apache.Ignite.Tests.IgniteServerBase.Dispose()
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19544) Thin 3.0: Data Streamer with Receiver
[ https://issues.apache.org/jira/browse/IGNITE-19544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-19544: Description: Implement data streamer with receiver in Java client - see [IEP-121|https://cwiki.apache.org/confluence/display/IGNITE/IEP-121%3A+Data+Streamer+with+Receiver] (was: Implement data streamer with receiver in Java client - see Use Case 2 in the [IEP-102|https://cwiki.apache.org/confluence/display/IGNITE/IEP-102%3A+Data+Streamer].) > Thin 3.0: Data Streamer with Receiver > - > > Key: IGNITE-19544 > URL: https://issues.apache.org/jira/browse/IGNITE-19544 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-102, iep-121, ignite-3 > Fix For: 3.0.0-beta2 > > > Implement data streamer with receiver in Java client - see > [IEP-121|https://cwiki.apache.org/confluence/display/IGNITE/IEP-121%3A+Data+Streamer+with+Receiver] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22277) Remove Zone annotation from Catalog API
Pavel Tupitsyn created IGNITE-22277: --- Summary: Remove Zone annotation from Catalog API Key: IGNITE-22277 URL: https://issues.apache.org/jira/browse/IGNITE-22277 Project: Ignite Issue Type: Improvement Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 Zone annotation does not make much sense - it goes on an empty class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22276) Catalog API allows an index without columns
Pavel Tupitsyn created IGNITE-22276: --- Summary: Catalog API allows an index without columns Key: IGNITE-22276 URL: https://issues.apache.org/jira/browse/IGNITE-22276 Project: Ignite Issue Type: Bug Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22276) Catalog API allows an index without columns
[
https://issues.apache.org/jira/browse/IGNITE-22276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22276:
Description:
This code produces a SQL parse error:
{code:java}
var person2Table = ignite.catalog().createTable(
TableDefinition.builder("Person2")
.key(PersonKey.class)
.value(PersonValue.class)
.index("height", IndexType.DEFAULT)
.zone("Zone2")
.build()
).execute();
{code}
> Catalog API allows an index without columns
> ---
>
> Key: IGNITE-22276
> URL: https://issues.apache.org/jira/browse/IGNITE-22276
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> This code produces a SQL parse error:
> {code:java}
>var person2Table = ignite.catalog().createTable(
>TableDefinition.builder("Person2")
>.key(PersonKey.class)
>.value(PersonValue.class)
>.index("height", IndexType.DEFAULT)
>.zone("Zone2")
>.build()
>).execute();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22274) Remove o.a.i.catalog.Options
[ https://issues.apache.org/jira/browse/IGNITE-22274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22274: Description: *org.apache.ignite.catalog.Options* affects generated SQL, but it provides no value to the user. SQL is an implementation detail of Catalog API. > Remove o.a.i.catalog.Options > > > Key: IGNITE-22274 > URL: https://issues.apache.org/jira/browse/IGNITE-22274 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *org.apache.ignite.catalog.Options* affects generated SQL, but it provides no > value to the user. SQL is an implementation detail of Catalog API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22274) Remove o.a.i.catalog.Options
Pavel Tupitsyn created IGNITE-22274: --- Summary: Remove o.a.i.catalog.Options Key: IGNITE-22274 URL: https://issues.apache.org/jira/browse/IGNITE-22274 Project: Ignite Issue Type: Improvement Components: sql Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22273) Use PUBLIC as default schema in catalog API
Pavel Tupitsyn created IGNITE-22273: --- Summary: Use PUBLIC as default schema in catalog API Key: IGNITE-22273 URL: https://issues.apache.org/jira/browse/IGNITE-22273 Project: Ignite Issue Type: Improvement Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22272) Rework Catalog API
[ https://issues.apache.org/jira/browse/IGNITE-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22272: Description: * Do not return a Query that has to be executed, run it immediately. For example: *Table table = catalog.createTable(Pojo.class)* * All methods should be async-first * Rename *create* to *createTable* (recordClass and KV methods) * all *createTable* methods should return a *Table*. Especially important for record and KV cases, where the resulting name is not obvious was: * All methods should be async-first * Rename *create* to *createTable* (recordClass and KV methods) * all *createTable* methods should return a *Table*. Especially important for record and KV cases, where the resulting name is not obvious > Rework Catalog API > -- > > Key: IGNITE-22272 > URL: https://issues.apache.org/jira/browse/IGNITE-22272 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > * Do not return a Query that has to be executed, run it immediately. For > example: *Table table = catalog.createTable(Pojo.class)* > * All methods should be async-first > * Rename *create* to *createTable* (recordClass and KV methods) > * all *createTable* methods should return a *Table*. Especially important for > record and KV cases, where the resulting name is not obvious -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22272) Rework Catalog API
[ https://issues.apache.org/jira/browse/IGNITE-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22272: Description: * All methods should be async-first * Rename *create* to *createTable* (recordClass and KV methods) * all *createTable* methods should return a *Table*. Especially important for record and KV cases, where the resulting name is not obvious > Rework Catalog API > -- > > Key: IGNITE-22272 > URL: https://issues.apache.org/jira/browse/IGNITE-22272 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > * All methods should be async-first > * Rename *create* to *createTable* (recordClass and KV methods) > * all *createTable* methods should return a *Table*. Especially important for > record and KV cases, where the resulting name is not obvious -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22272) Rework Catalog API
Pavel Tupitsyn created IGNITE-22272: --- Summary: Rework Catalog API Key: IGNITE-22272 URL: https://issues.apache.org/jira/browse/IGNITE-22272 Project: Ignite Issue Type: Improvement Components: sql Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22271) Rename copying overload of Tuple.create to copy
[ https://issues.apache.org/jira/browse/IGNITE-22271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22271: Description: *copy* is a more suitable name for *static Tuple create(Tuple tuple)* https://github.com/apache/ignite-3/blob/f6ce1ac450f5597582697adbcd967a7f702252ea/modules/api/src/main/java/org/apache/ignite/table/Tuple.java#L82 > Rename copying overload of Tuple.create to copy > --- > > Key: IGNITE-22271 > URL: https://issues.apache.org/jira/browse/IGNITE-22271 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *copy* is a more suitable name for *static Tuple create(Tuple tuple)* > https://github.com/apache/ignite-3/blob/f6ce1ac450f5597582697adbcd967a7f702252ea/modules/api/src/main/java/org/apache/ignite/table/Tuple.java#L82 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22271) Rename copying overload of Tuple.create to copy
Pavel Tupitsyn created IGNITE-22271: --- Summary: Rename copying overload of Tuple.create to copy Key: IGNITE-22271 URL: https://issues.apache.org/jira/browse/IGNITE-22271 Project: Ignite Issue Type: Improvement Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22269) UnexpectedNullValueException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22269: Description: *INTERNAL_ERR* does not make sense for *UnexpectedNullValueException* (was: INTERNAL_ERR does not make sense for UnexpectedNullValueException) > UnexpectedNullValueException uses INTERNAL_ERR code > --- > > Key: IGNITE-22269 > URL: https://issues.apache.org/jira/browse/IGNITE-22269 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *INTERNAL_ERR* does not make sense for *UnexpectedNullValueException* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22270) MarshallerException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22270: Description: *INTERNAL_ERR* does not make sense for *MarshallerException* (was: INTERNAL_ERR does not make sense for MarshallerException) > MarshallerException uses INTERNAL_ERR code > -- > > Key: IGNITE-22270 > URL: https://issues.apache.org/jira/browse/IGNITE-22270 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *INTERNAL_ERR* does not make sense for *MarshallerException* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22269) UnexpectedNullValueException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22269: Ignite Flags: (was: Docs Required,Release Notes Required) > UnexpectedNullValueException uses INTERNAL_ERR code > --- > > Key: IGNITE-22269 > URL: https://issues.apache.org/jira/browse/IGNITE-22269 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *INTERNAL_ERR* does not make sense for *UnexpectedNullValueException* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22270) MarshallerException uses INTERNAL_ERR code
Pavel Tupitsyn created IGNITE-22270: --- Summary: MarshallerException uses INTERNAL_ERR code Key: IGNITE-22270 URL: https://issues.apache.org/jira/browse/IGNITE-22270 Project: Ignite Issue Type: Bug Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 INTERNAL_ERR does not make sense for UnexpectedNullValueException -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22269) UnexpectedNullValueException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22269: Description: INTERNAL_ERR does not make sense for > UnexpectedNullValueException uses INTERNAL_ERR code > --- > > Key: IGNITE-22269 > URL: https://issues.apache.org/jira/browse/IGNITE-22269 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > INTERNAL_ERR does not make sense for -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22270) MarshallerException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22270: Description: INTERNAL_ERR does not make sense for MarshallerException (was: INTERNAL_ERR does not make sense for UnexpectedNullValueException) > MarshallerException uses INTERNAL_ERR code > -- > > Key: IGNITE-22270 > URL: https://issues.apache.org/jira/browse/IGNITE-22270 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > INTERNAL_ERR does not make sense for MarshallerException -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22270) MarshallerException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22270: Ignite Flags: (was: Docs Required,Release Notes Required) > MarshallerException uses INTERNAL_ERR code > -- > > Key: IGNITE-22270 > URL: https://issues.apache.org/jira/browse/IGNITE-22270 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > INTERNAL_ERR does not make sense for UnexpectedNullValueException -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22269) UnexpectedNullValueException uses INTERNAL_ERR code
Pavel Tupitsyn created IGNITE-22269: --- Summary: UnexpectedNullValueException uses INTERNAL_ERR code Key: IGNITE-22269 URL: https://issues.apache.org/jira/browse/IGNITE-22269 Project: Ignite Issue Type: Bug Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22269) UnexpectedNullValueException uses INTERNAL_ERR code
[ https://issues.apache.org/jira/browse/IGNITE-22269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22269: Description: INTERNAL_ERR does not make sense for UnexpectedNullValueException (was: INTERNAL_ERR does not make sense for ) > UnexpectedNullValueException uses INTERNAL_ERR code > --- > > Key: IGNITE-22269 > URL: https://issues.apache.org/jira/browse/IGNITE-22269 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > INTERNAL_ERR does not make sense for UnexpectedNullValueException -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22267) Improve Table API javadocs
[ https://issues.apache.org/jira/browse/IGNITE-22267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22267: Description: 1. Remove "started table" term, "table" is enough 2. Remove "binary object" mentions 3. Explain how KV view "splits" row data in two parts. It does not actually operate on separate keys and values. 4. Replace "Transaction or null to auto-commit" with "Transaction or null for implicit transaction" 5. Remove "@throws IgniteException If an unspecified platform exception has occurred internally", it is not useful was: 1. Remove "started table" term, "table" is enough 2. Remove "binary object" mentions 3. Explain how KV view "splits" row data in two parts. It does not actually operate on separate keys and values. 4. Replace "Transaction or null to auto-commit" with "Transaction or null for implicit transaction" > Improve Table API javadocs > -- > > Key: IGNITE-22267 > URL: https://issues.apache.org/jira/browse/IGNITE-22267 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. Remove "started table" term, "table" is enough > 2. Remove "binary object" mentions > 3. Explain how KV view "splits" row data in two parts. It does not actually > operate on separate keys and values. > 4. Replace "Transaction or null to auto-commit" with "Transaction or null for > implicit transaction" > 5. Remove "@throws IgniteException If an unspecified platform exception has > occurred internally", it is not useful -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22267) Improve Table API javadocs
[ https://issues.apache.org/jira/browse/IGNITE-22267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22267: Description: 1. Remove "started table" term, "table" is enough 2. Remove "binary object" mentions 3. Explain how KV view "splits" row data in two parts. It does not actually operate on separate keys and values. 4. Replace "Transaction or null to auto-commit" with "Transaction or null for implicit transaction" 5. Remove "@throws IgniteException If an unspecified platform exception has occurred internally", it is not useful 6. Declare order of tables in *tables()* and *tablesAsync()* was: 1. Remove "started table" term, "table" is enough 2. Remove "binary object" mentions 3. Explain how KV view "splits" row data in two parts. It does not actually operate on separate keys and values. 4. Replace "Transaction or null to auto-commit" with "Transaction or null for implicit transaction" 5. Remove "@throws IgniteException If an unspecified platform exception has occurred internally", it is not useful > Improve Table API javadocs > -- > > Key: IGNITE-22267 > URL: https://issues.apache.org/jira/browse/IGNITE-22267 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. Remove "started table" term, "table" is enough > 2. Remove "binary object" mentions > 3. Explain how KV view "splits" row data in two parts. It does not actually > operate on separate keys and values. > 4. Replace "Transaction or null to auto-commit" with "Transaction or null for > implicit transaction" > 5. Remove "@throws IgniteException If an unspecified platform exception has > occurred internally", it is not useful > 6. Declare order of tables in *tables()* and *tablesAsync()* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22267) Improve Table API javadocs
[
https://issues.apache.org/jira/browse/IGNITE-22267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22267:
Description:
1. Remove "started table" term, "table" is enough
2. Remove "binary object" mentions
3. Explain how KV view "splits" row data in two parts. It does not actually
operate on separate keys and values.
4. Replace "Transaction or null to auto-commit" with "Transaction or null for
implicit transaction"
was:
1. Remove "started table" term, "table" is enough
2. Remove "binary object" mentions
3. Explain how KV view "splits" row data in two parts. It does not actually
operate on separate keys and values.
4. Replace "Transaction or {@code null} to auto-commit" with "Transaction or
{@code null} for implicit transaction"
> Improve Table API javadocs
> --
>
> Key: IGNITE-22267
> URL: https://issues.apache.org/jira/browse/IGNITE-22267
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 1. Remove "started table" term, "table" is enough
> 2. Remove "binary object" mentions
> 3. Explain how KV view "splits" row data in two parts. It does not actually
> operate on separate keys and values.
> 4. Replace "Transaction or null to auto-commit" with "Transaction or null for
> implicit transaction"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22267) Improve Table API javadocs
[
https://issues.apache.org/jira/browse/IGNITE-22267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22267:
Description:
1. Remove "started table" term, "table" is enough
2. Remove "binary object" mentions
3. Explain how KV view "splits" row data in two parts. It does not actually
operate on separate keys and values.
4. Replace "Transaction or {@code null} to auto-commit" with "Transaction or
{@code null} for implicit transaction"
was:
1. Remove "started table" term, "table" is enough
2. Remove "binary object" mentions
3. Explain how KV view "splits" row data in two parts. It does not actually
operate on separate keys and values.
> Improve Table API javadocs
> --
>
> Key: IGNITE-22267
> URL: https://issues.apache.org/jira/browse/IGNITE-22267
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 1. Remove "started table" term, "table" is enough
> 2. Remove "binary object" mentions
> 3. Explain how KV view "splits" row data in two parts. It does not actually
> operate on separate keys and values.
> 4. Replace "Transaction or {@code null} to auto-commit" with "Transaction or
> {@code null} for implicit transaction"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22267) Improve Table API javadocs
[ https://issues.apache.org/jira/browse/IGNITE-22267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22267: Description: 1. Remove "started table" term, "table" is enough 2. Remove "binary object" mentions 3. Explain how KV view "splits" row data in two parts. It does not actually operate on separate keys and values. > Improve Table API javadocs > -- > > Key: IGNITE-22267 > URL: https://issues.apache.org/jira/browse/IGNITE-22267 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. Remove "started table" term, "table" is enough > 2. Remove "binary object" mentions > 3. Explain how KV view "splits" row data in two parts. It does not actually > operate on separate keys and values. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22267) Improve Table API javadocs
Pavel Tupitsyn created IGNITE-22267: --- Summary: Improve Table API javadocs Key: IGNITE-22267 URL: https://issues.apache.org/jira/browse/IGNITE-22267 Project: Ignite Issue Type: Improvement Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22266) Move IgniteTables to org.apache.ignite.table package
[ https://issues.apache.org/jira/browse/IGNITE-22266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22266: Description: IgniteTables is in it's own *manager* package which is weird and inconsistent with other top-level APIs (compute, sql, tx, ...). Move it up to *o.a.i.table*. (was: IgniteTables is in it's own *manager* package which is weird and inconsistent with other top-level APIs (compute, tx, etc)) > Move IgniteTables to org.apache.ignite.table package > > > Key: IGNITE-22266 > URL: https://issues.apache.org/jira/browse/IGNITE-22266 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > IgniteTables is in it's own *manager* package which is weird and inconsistent > with other top-level APIs (compute, sql, tx, ...). Move it up to > *o.a.i.table*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22266) Move IgniteTables to org.apache.ignite.table package
[ https://issues.apache.org/jira/browse/IGNITE-22266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22266: Description: IgniteTables is in it's own *manager* package which is weird and inconsistent with other top-level APIs (compute, tx, etc) > Move IgniteTables to org.apache.ignite.table package > > > Key: IGNITE-22266 > URL: https://issues.apache.org/jira/browse/IGNITE-22266 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > IgniteTables is in it's own *manager* package which is weird and inconsistent > with other top-level APIs (compute, tx, etc) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22266) Move IgniteTables to org.apache.ignite.table package
Pavel Tupitsyn created IGNITE-22266: --- Summary: Move IgniteTables to org.apache.ignite.table package Key: IGNITE-22266 URL: https://issues.apache.org/jira/browse/IGNITE-22266 Project: Ignite Issue Type: Improvement Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22265) Improve IgniteTransactions javadoc
[
https://issues.apache.org/jira/browse/IGNITE-22265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22265:
Description:
1. "Begins an asynchronous transaction." -> "Begins a transaction
asynchronously"
2. "Take care then using the asynchronous operations inside the closure..."
uses an incorrect example first.
* Show the correct one first
* Make it very clear that the incorrect one is not to be used
3. Document isolation level and behavior
4. Document optimistic/pessimistic behavior, deadlocks, conflicts
5. javadoc for {{ T runInTransaction}} is copypasted
was:
1. "Begins an asynchronous transaction." -> "Begins a transaction
asynchronously"
2. "Take care then using the asynchronous operations inside the closure..."
uses an incorrect example first.
* Show the correct one first
* Make it very clear that the incorrect one is not to be used
3. Document isolation level and behavior
4. Document optimistic/pessimistic behavior
5. javadoc for {{ T runInTransaction}} is copypasted
> Improve IgniteTransactions javadoc
> --
>
> Key: IGNITE-22265
> URL: https://issues.apache.org/jira/browse/IGNITE-22265
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 1. "Begins an asynchronous transaction." -> "Begins a transaction
> asynchronously"
> 2. "Take care then using the asynchronous operations inside the closure..."
> uses an incorrect example first.
> * Show the correct one first
> * Make it very clear that the incorrect one is not to be used
> 3. Document isolation level and behavior
> 4. Document optimistic/pessimistic behavior, deadlocks, conflicts
> 5. javadoc for {{ T runInTransaction}} is copypasted
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22265) Improve IgniteTransactions javadoc
[
https://issues.apache.org/jira/browse/IGNITE-22265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22265:
Description:
1. "Begins an asynchronous transaction." -> "Begins a transaction
asynchronously"
2. "Take care then using the asynchronous operations inside the closure..."
uses an incorrect example first.
* Show the correct one first
* Make it very clear that the incorrect one is not to be used
3. Document isolation level and behavior
4. Document optimistic/pessimistic behavior, deadlocks, conflicts
5. javadoc for * T runInTransaction* is copypasted
was:
1. "Begins an asynchronous transaction." -> "Begins a transaction
asynchronously"
2. "Take care then using the asynchronous operations inside the closure..."
uses an incorrect example first.
* Show the correct one first
* Make it very clear that the incorrect one is not to be used
3. Document isolation level and behavior
4. Document optimistic/pessimistic behavior, deadlocks, conflicts
5. javadoc for {{ T runInTransaction}} is copypasted
> Improve IgniteTransactions javadoc
> --
>
> Key: IGNITE-22265
> URL: https://issues.apache.org/jira/browse/IGNITE-22265
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 1. "Begins an asynchronous transaction." -> "Begins a transaction
> asynchronously"
> 2. "Take care then using the asynchronous operations inside the closure..."
> uses an incorrect example first.
> * Show the correct one first
> * Make it very clear that the incorrect one is not to be used
> 3. Document isolation level and behavior
> 4. Document optimistic/pessimistic behavior, deadlocks, conflicts
> 5. javadoc for * T runInTransaction* is copypasted
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22265) Improve IgniteTransactions javadoc
[
https://issues.apache.org/jira/browse/IGNITE-22265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22265:
Description:
1. "Begins an asynchronous transaction." -> "Begins a transaction
asynchronously"
2. "Take care then using the asynchronous operations inside the closure..."
uses an incorrect example first.
* Show the correct one first
* Make it very clear that the incorrect one is not to be used
3. Document isolation level and behavior
4. Document optimistic/pessimistic behavior
5. javadoc for {{ T runInTransaction}} is copypasted
was:
1. "Begins an asynchronous transaction." -> "Begins a transaction
asynchronously"
2. "Take care then using the asynchronous operations inside the closure..."
uses an incorrect example first.
* Show the correct one first
* Make it very clear that the incorrect one is not to be used
3. Document isolation level and behavior
4. Document optimistic/pessimistic behavior
> Improve IgniteTransactions javadoc
> --
>
> Key: IGNITE-22265
> URL: https://issues.apache.org/jira/browse/IGNITE-22265
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 1. "Begins an asynchronous transaction." -> "Begins a transaction
> asynchronously"
> 2. "Take care then using the asynchronous operations inside the closure..."
> uses an incorrect example first.
> * Show the correct one first
> * Make it very clear that the incorrect one is not to be used
> 3. Document isolation level and behavior
> 4. Document optimistic/pessimistic behavior
> 5. javadoc for {{ T runInTransaction}} is copypasted
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22265) Improve IgniteTransactions javadoc
[ https://issues.apache.org/jira/browse/IGNITE-22265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22265: Description: 1. "Begins an asynchronous transaction." -> "Begins a transaction asynchronously" 2. "Take care then using the asynchronous operations inside the closure..." uses an incorrect example first. * Show the correct one first * Make it very clear that the incorrect one is not to be used 3. Document isolation level and behavior 4. Document optimistic/pessimistic behavior was: 1. "Begins an asynchronous transaction." -> "Begins a transaction asynchronously" 2. "Take care then using the asynchronous operations inside the closure..." uses an incorrect example first. * Show the correct one first * Make it very clear that the incorrect one is not to be used 3. tbd > Improve IgniteTransactions javadoc > -- > > Key: IGNITE-22265 > URL: https://issues.apache.org/jira/browse/IGNITE-22265 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. "Begins an asynchronous transaction." -> "Begins a transaction > asynchronously" > 2. "Take care then using the asynchronous operations inside the closure..." > uses an incorrect example first. > * Show the correct one first > * Make it very clear that the incorrect one is not to be used > 3. Document isolation level and behavior > 4. Document optimistic/pessimistic behavior -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22265) Improve IgniteTransactions javadoc
[ https://issues.apache.org/jira/browse/IGNITE-22265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22265: Description: 1. "Begins an asynchronous transaction." -> "Begins a transaction asynchronously" 2. "Take care then using the asynchronous operations inside the closure..." uses an incorrect example first. * Show the correct one first * Make it very clear that the incorrect one is not to be used 3. tbd was: 1. "Begins an asynchronous transaction." -> "Begins a transaction asynchronously" 2. "Take care then using the asynchronous operations inside the closure..." uses an incorrect example first. * Show the correct one first * Make it very clear that the incorrect one is not to be used > Improve IgniteTransactions javadoc > -- > > Key: IGNITE-22265 > URL: https://issues.apache.org/jira/browse/IGNITE-22265 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. "Begins an asynchronous transaction." -> "Begins a transaction > asynchronously" > 2. "Take care then using the asynchronous operations inside the closure..." > uses an incorrect example first. > * Show the correct one first > * Make it very clear that the incorrect one is not to be used > 3. tbd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22265) Improve IgniteTransactions javadoc
[ https://issues.apache.org/jira/browse/IGNITE-22265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22265: Description: 1. "Begins an asynchronous transaction." -> "Begins a transaction asynchronously" 2. "Take care then using the asynchronous operations inside the closure..." uses an incorrect example first. * Show the correct one first * Make it very clear that the incorrect one is not to be used 3. tbd was: 1. "Begins an asynchronous transaction." -> "Begins a transaction asynchronously" 2. "Take care then using the asynchronous operations inside the closure..." uses an incorrect example first. * Show the correct one first * Make it very clear that the incorrect one is not to be used 3. tbd > Improve IgniteTransactions javadoc > -- > > Key: IGNITE-22265 > URL: https://issues.apache.org/jira/browse/IGNITE-22265 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. "Begins an asynchronous transaction." -> "Begins a transaction > asynchronously" > 2. "Take care then using the asynchronous operations inside the closure..." > uses an incorrect example first. > * Show the correct one first > * Make it very clear that the incorrect one is not to be used > 3. tbd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22265) Improve IgniteTransactions javadoc
[ https://issues.apache.org/jira/browse/IGNITE-22265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22265: Description: 1. "Begins an asynchronous transaction." -> "Begins a transaction asynchronously" 2. "Take care then using the asynchronous operations inside the closure..." uses an incorrect example first. * Show the correct one first * Make it very clear that the incorrect one is not to be used > Improve IgniteTransactions javadoc > -- > > Key: IGNITE-22265 > URL: https://issues.apache.org/jira/browse/IGNITE-22265 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. "Begins an asynchronous transaction." -> "Begins a transaction > asynchronously" > 2. "Take care then using the asynchronous operations inside the closure..." > uses an incorrect example first. > * Show the correct one first > * Make it very clear that the incorrect one is not to be used -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22265) Improve IgniteTransactions javadoc
Pavel Tupitsyn created IGNITE-22265: --- Summary: Improve IgniteTransactions javadoc Key: IGNITE-22265 URL: https://issues.apache.org/jira/browse/IGNITE-22265 Project: Ignite Issue Type: Improvement Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22264) Startup instructions in examples are outdated
[ https://issues.apache.org/jira/browse/IGNITE-22264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22264: Description: Verify startup instructions (at the top of every example), make sure they work with upcoming Ignite beta2. https://github.com/apache/ignite-3/tree/main/examples/src/main/java/org/apache/ignite/example was:Verify startup instructions (at the top of every example), make sure they work with upcoming Ignite beta2. > Startup instructions in examples are outdated > - > > Key: IGNITE-22264 > URL: https://issues.apache.org/jira/browse/IGNITE-22264 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Verify startup instructions (at the top of every example), make sure they > work with upcoming Ignite beta2. > https://github.com/apache/ignite-3/tree/main/examples/src/main/java/org/apache/ignite/example -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22264) Startup instructions in examples are outdated
Pavel Tupitsyn created IGNITE-22264: --- Summary: Startup instructions in examples are outdated Key: IGNITE-22264 URL: https://issues.apache.org/jira/browse/IGNITE-22264 Project: Ignite Issue Type: Bug Components: examples Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 Verify startup instructions (at the top of every example), make sure they work with upcoming Ignite beta2. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22262) Startup instructions missing in SqlApiExample
Pavel Tupitsyn created IGNITE-22262: --- Summary: Startup instructions missing in SqlApiExample Key: IGNITE-22262 URL: https://issues.apache.org/jira/browse/IGNITE-22262 Project: Ignite Issue Type: Bug Components: examples Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22262) Startup instructions missing in SqlApiExample
[ https://issues.apache.org/jira/browse/IGNITE-22262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22262: Ignite Flags: (was: Docs Required,Release Notes Required) > Startup instructions missing in SqlApiExample > - > > Key: IGNITE-22262 > URL: https://issues.apache.org/jira/browse/IGNITE-22262 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Pavel Tupitsyn >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22262) Startup instructions missing in SqlApiExample
[ https://issues.apache.org/jira/browse/IGNITE-22262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22262: Priority: Minor (was: Major) > Startup instructions missing in SqlApiExample > - > > Key: IGNITE-22262 > URL: https://issues.apache.org/jira/browse/IGNITE-22262 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Pavel Tupitsyn >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22262) Startup instructions missing in SqlApiExample
[ https://issues.apache.org/jira/browse/IGNITE-22262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22262: Description: * Standard header with node start instructions is missing. * The example fails if you run it as is (without starting a properly configured node) > Startup instructions missing in SqlApiExample > - > > Key: IGNITE-22262 > URL: https://issues.apache.org/jira/browse/IGNITE-22262 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Pavel Tupitsyn >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > * Standard header with node start instructions is missing. > * The example fails if you run it as is (without starting a properly > configured node) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16116) Support user mapping functions
[
https://issues.apache.org/jira/browse/IGNITE-16116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-16116:
Summary: Support user mapping functions (was: Support user mapping
functions.)
> Support user mapping functions
> --
>
> Key: IGNITE-16116
> URL: https://issues.apache.org/jira/browse/IGNITE-16116
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
>
> Let's allow users to implement their own strategy of marshaling objects.
> The {{Tuple}} interface looks good candidate for representing a row, rather
> than exposing any internals to the user.
> Start point is {{Mapper.of(Function objectToRow, Function
> rowToObject)}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19544) Thin 3.0: Data Streamer with Receiver
[ https://issues.apache.org/jira/browse/IGNITE-19544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-19544: Labels: iep-102 iep-121 ignite-3 (was: iep-102 ignite-3) > Thin 3.0: Data Streamer with Receiver > - > > Key: IGNITE-19544 > URL: https://issues.apache.org/jira/browse/IGNITE-19544 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-102, iep-121, ignite-3 > Fix For: 3.0.0-beta2 > > > Implement data streamer with receiver in Java client - see Use Case 2 in the > [IEP-102|https://cwiki.apache.org/confluence/display/IGNITE/IEP-102%3A+Data+Streamer]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21410) Ignite 3.0: Create tables from Java classes
[ https://issues.apache.org/jira/browse/IGNITE-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21410: Labels: iep-123 ignite-3 (was: ignite-3) > Ignite 3.0: Create tables from Java classes > --- > > Key: IGNITE-21410 > URL: https://issues.apache.org/jira/browse/IGNITE-21410 > Project: Ignite > Issue Type: Epic >Reporter: Vadim Kolodin >Priority: Major > Labels: iep-123, ignite-3 > > In addition to SQL DDL commands, provide a simple Java API for initial tables > generation from POJO. Support custom annotations and simple builders. This > feature should work seamlessly with existing Mapper interface (keyValueView > and recordView). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19546) .NET: Thin 3.0: Data Streamer with Receiver
[ https://issues.apache.org/jira/browse/IGNITE-19546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-19546: Labels: .NET iep-102 iep-121 ignite-3 (was: .NET iep-102 ignite-3) > .NET: Thin 3.0: Data Streamer with Receiver > --- > > Key: IGNITE-19546 > URL: https://issues.apache.org/jira/browse/IGNITE-19546 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, iep-102, iep-121, ignite-3 > Fix For: 3.0.0-beta2 > > > Implement data streamer with receiver in .NET client - see Use Case 2 in the > [IEP-102|https://cwiki.apache.org/confluence/display/IGNITE/IEP-102%3A+Data+Streamer]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22058) Use paranoid leak detection in tests
[ https://issues.apache.org/jira/browse/IGNITE-22058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846868#comment-17846868 ] Pavel Tupitsyn commented on IGNITE-22058: - Let's enable leak detection for CLI and JDBC tests as well, those use thin client internally. > Use paranoid leak detection in tests > > > Key: IGNITE-22058 > URL: https://issues.apache.org/jira/browse/IGNITE-22058 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > We should set `io.netty.leakDetection.level=paranoid` in integration tests > and network tests, in order to detect possible leaks. > https://netty.io/wiki/reference-counted-objects.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22058) Use paranoid leak detection in tests
[ https://issues.apache.org/jira/browse/IGNITE-22058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22058: Description: We should set `io.netty.leakDetection.level=paranoid` in integration tests and network tests, in order to detect possible leaks. https://netty.io/wiki/reference-counted-objects.html was:We should set `io.netty.leakDetection.level=paranoid` in integration tests and network tests, in order to detect possible leaks > Use paranoid leak detection in tests > > > Key: IGNITE-22058 > URL: https://issues.apache.org/jira/browse/IGNITE-22058 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > We should set `io.netty.leakDetection.level=paranoid` in integration tests > and network tests, in order to detect possible leaks. > https://netty.io/wiki/reference-counted-objects.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22250) Java thin: ItSqlClientSynchronousApiTest.testTimeZoneId is flaky
[
https://issues.apache.org/jira/browse/IGNITE-22250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22250:
Ignite Flags: (was: Docs Required,Release Notes Required)
> Java thin: ItSqlClientSynchronousApiTest.testTimeZoneId is flaky
>
>
> Key: IGNITE-22250
> URL: https://issues.apache.org/jira/browse/IGNITE-22250
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> org.opentest4j.AssertionFailedError: expected: <1.71580418E12> but was:
> <1.71580405E12>
> at
> app//org.apache.ignite.internal.sql.api.ItSqlApiBaseTest.testTimeZoneId(ItSqlApiBaseTest.java:866)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22250) Java thin: ItSqlClientSynchronousApiTest.testTimeZoneId is flaky
[
https://issues.apache.org/jira/browse/IGNITE-22250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-22250:
Description:
{code:java}
org.opentest4j.AssertionFailedError: expected: <1.71580418E12> but was:
<1.71580405E12>
at
app//org.apache.ignite.internal.sql.api.ItSqlApiBaseTest.testTimeZoneId(ItSqlApiBaseTest.java:866)
{code}
> Java thin: ItSqlClientSynchronousApiTest.testTimeZoneId is flaky
>
>
> Key: IGNITE-22250
> URL: https://issues.apache.org/jira/browse/IGNITE-22250
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> org.opentest4j.AssertionFailedError: expected: <1.71580418E12> but was:
> <1.71580405E12>
> at
> app//org.apache.ignite.internal.sql.api.ItSqlApiBaseTest.testTimeZoneId(ItSqlApiBaseTest.java:866)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22250) Java thin: ItSqlClientSynchronousApiTest.testTimeZoneId is flaky
Pavel Tupitsyn created IGNITE-22250: --- Summary: Java thin: ItSqlClientSynchronousApiTest.testTimeZoneId is flaky Key: IGNITE-22250 URL: https://issues.apache.org/jira/browse/IGNITE-22250 Project: Ignite Issue Type: Bug Components: thin client Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22208) Deduplicate DEFAULT_SCHEMA_NAME
[
https://issues.apache.org/jira/browse/IGNITE-22208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846616#comment-17846616
]
Pavel Tupitsyn commented on IGNITE-22208:
-
Merged to main:
[bd4574da15154fb17c258c42f479b7ec1bc154a6|https://github.com/apache/ignite-3/commit/bd4574da15154fb17c258c42f479b7ec1bc154a6]
> Deduplicate DEFAULT_SCHEMA_NAME
> ---
>
> Key: IGNITE-22208
> URL: https://issues.apache.org/jira/browse/IGNITE-22208
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following constant is duplicated 6 times currently:
> {code:java}
> DEFAULT_SCHEMA_NAME = "PUBLIC"
> {code}
> * Let's put it somewhere in the core module and reuse.
> * It should *not* be a part of the public API. For internal use only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22235) Remove eviction-related leftovers of AI2
[ https://issues.apache.org/jira/browse/IGNITE-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22235: Fix Version/s: 3.0.0-beta2 > Remove eviction-related leftovers of AI2 > > > Key: IGNITE-22235 > URL: https://issues.apache.org/jira/browse/IGNITE-22235 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Myskov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > There is some code ported from AI2 but dead at the moment. The following > pieces are related to eviction and can be safely removed: > * org.apache.ignite.internal.pagememory.evict.PageEvictionTracker > * eviction-related configs in VolatilePageMemoryDataRegionConfigurationSchema -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21605) C++ 3.0: Pass client time zone to server
[ https://issues.apache.org/jira/browse/IGNITE-21605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846297#comment-17846297 ] Pavel Tupitsyn commented on IGNITE-21605: - [~isapego] looks good to me. > C++ 3.0: Pass client time zone to server > > > Key: IGNITE-21605 > URL: https://issues.apache.org/jira/browse/IGNITE-21605 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Pereslegin >Assignee: Igor Sapego >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Once IGNITE-21551 is implemented, it will be possible to set the time zone in > a user session. > The session time zone is taken into account when calling functions for > obtaining the current time (CURRENT_TIMESTAMP, etc), as well as when > processing a string literal for the 'TIMESTAMP WITH LOCAL TIME ZONE' type. > For this to work correctly, you need to transfer the client's time zone > through the thin client. > p.s. check the TODOs that point to this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22031) .NET: Thin 3.0: Remove DataStreamer.PartitionAssignmentUpdateFrequency
[ https://issues.apache.org/jira/browse/IGNITE-22031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846288#comment-17846288 ] Pavel Tupitsyn commented on IGNITE-22031: - Merged to main: [185e568d4536b686794dc1011d3f9ba561e91d7b|https://github.com/apache/ignite-3/commit/185e568d4536b686794dc1011d3f9ba561e91d7b] > .NET: Thin 3.0: Remove DataStreamer.PartitionAssignmentUpdateFrequency > -- > > Key: IGNITE-22031 > URL: https://issues.apache.org/jira/browse/IGNITE-22031 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Timer-based partition assignment check is not necessary. > *Table.GetPartitionAssignmentAsync* is backed by a cache with a > double-checked locking, and uses a *ValueTask*, so there is no overhead in > case of unchanged assignment - we can call it as often as needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22205) Java thin 3.0: Reuse SQL API implementations from embedded
[ https://issues.apache.org/jira/browse/IGNITE-22205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846253#comment-17846253 ] Pavel Tupitsyn commented on IGNITE-22205: - Merged to main: [6dc1021e3ee00b8f599a1742bda0456c45f30710|https://github.com/apache/ignite-3/commit/6dc1021e3ee00b8f599a1742bda0456c45f30710] > Java thin 3.0: Reuse SQL API implementations from embedded > -- > > Key: IGNITE-22205 > URL: https://issues.apache.org/jira/browse/IGNITE-22205 > Project: Ignite > Issue Type: Improvement > Components: sql, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > The following classes can be moved to *core* module and reused across client > and embedded APIs: > * StatementImpl > * StatementBuilderImpl > * ResultSetMetadataImpl > * ColumnMetadataImpl > * ColumnOriginImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21542) Documentation for Ignite security model
[ https://issues.apache.org/jira/browse/IGNITE-21542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846172#comment-17846172 ] Pavel Tupitsyn commented on IGNITE-21542: - Merged to master: [7b8b4bae386be9396182d367a30e0387642e032f|https://github.com/apache/ignite/commit/7b8b4bae386be9396182d367a30e0387642e032f] > Documentation for Ignite security model > --- > > Key: IGNITE-21542 > URL: https://issues.apache.org/jira/browse/IGNITE-21542 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 40m > Remaining Estimate: 0h > > It might be helpful to introduce documentation regarding what could be > expected from Ignite installations in terms of security. More specifically, > what Ignite users can expect when it comes to Discovery and Communication > ports inside and outside of the Ignite DMZ. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21604) .NET: Thin 3.0: Pass client time zone to server
[ https://issues.apache.org/jira/browse/IGNITE-21604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845923#comment-17845923 ] Pavel Tupitsyn commented on IGNITE-21604: - Merged to main: [7028e1ed7b4be67a423bec6b7b93e6764e6e645b|https://github.com/apache/ignite-3/commit/7028e1ed7b4be67a423bec6b7b93e6764e6e645b] > .NET: Thin 3.0: Pass client time zone to server > --- > > Key: IGNITE-21604 > URL: https://issues.apache.org/jira/browse/IGNITE-21604 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Pereslegin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Once IGNITE-21551 is implemented, it will be possible to set the time zone in > a user session. > The session time zone is taken into account when calling functions for > obtaining the current time (CURRENT_TIMESTAMP, etc), as well as when > processing a string literal for the 'TIMESTAMP WITH LOCAL TIME ZONE' type. > For this to work correctly, you need to transfer the client's time zone > through the thin client. > p.s. check the TODOs that point to this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21568) Java thin 3.0: Pass client time zone to server
[ https://issues.apache.org/jira/browse/IGNITE-21568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845830#comment-17845830 ] Pavel Tupitsyn commented on IGNITE-21568: - Merged to main: [6871bba01b3643cf6e0b45cde7d2f69151b6a835|https://github.com/apache/ignite-3/commit/6871bba01b3643cf6e0b45cde7d2f69151b6a835] > Java thin 3.0: Pass client time zone to server > -- > > Key: IGNITE-21568 > URL: https://issues.apache.org/jira/browse/IGNITE-21568 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Pereslegin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Time Spent: 1h > Remaining Estimate: 0h > > Once IGNITE-21551 is implemented, it will be possible to set the time zone in > a user session. > The session time zone is taken into account when calling functions for > obtaining the current time (CURRENT_TIMESTAMP, etc), as well as when > processing a string literal for the 'TIMESTAMP WITH LOCAL TIME ZONE' type. > For this to work correctly, you need to transfer the client's time zone > through the thin client. > p.s. check the TODOs that point to this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22208) Deduplicate DEFAULT_SCHEMA_NAME
Pavel Tupitsyn created IGNITE-22208:
---
Summary: Deduplicate DEFAULT_SCHEMA_NAME
Key: IGNITE-22208
URL: https://issues.apache.org/jira/browse/IGNITE-22208
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 3.0.0-beta2
The following constant is duplicated 6 times currently:
{code:java}
DEFAULT_SCHEMA_NAME = "PUBLIC"
{code}
* Let's put it somewhere in the core module and reuse.
* It should *not* be a part of the public API. For internal use only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-21604) .NET: Thin 3.0: Pass client time zone to server
[ https://issues.apache.org/jira/browse/IGNITE-21604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845192#comment-17845192 ] Pavel Tupitsyn edited comment on IGNITE-21604 at 5/13/24 5:11 AM: -- See: * https://stackoverflow.com/questions/62854935/is-there-a-way-to-convert-from-net-timezoneinfo-to-java-zoneddatetime * https://codeblog.jonskeet.uk/2022/02/05/whats-up-with-timezoneinfo-on-net-6-part-1/ was (Author: ptupitsyn): See https://stackoverflow.com/questions/62854935/is-there-a-way-to-convert-from-net-timezoneinfo-to-java-zoneddatetime > .NET: Thin 3.0: Pass client time zone to server > --- > > Key: IGNITE-21604 > URL: https://issues.apache.org/jira/browse/IGNITE-21604 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Pereslegin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > > Once IGNITE-21551 is implemented, it will be possible to set the time zone in > a user session. > The session time zone is taken into account when calling functions for > obtaining the current time (CURRENT_TIMESTAMP, etc), as well as when > processing a string literal for the 'TIMESTAMP WITH LOCAL TIME ZONE' type. > For this to work correctly, you need to transfer the client's time zone > through the thin client. > p.s. check the TODOs that point to this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22205) Java thin 3.0: Reuse SQL API implementations from embedded
[ https://issues.apache.org/jira/browse/IGNITE-22205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22205: Description: The following classes can be moved to *core* module and reused across client and embedded APIs: * StatementImpl * StatementBuilderImpl * ResultSetMetadataImpl * ColumnMetadataImpl * ColumnOriginImpl > Java thin 3.0: Reuse SQL API implementations from embedded > -- > > Key: IGNITE-22205 > URL: https://issues.apache.org/jira/browse/IGNITE-22205 > Project: Ignite > Issue Type: Improvement > Components: sql, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > The following classes can be moved to *core* module and reused across client > and embedded APIs: > * StatementImpl > * StatementBuilderImpl > * ResultSetMetadataImpl > * ColumnMetadataImpl > * ColumnOriginImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22205) Java thin 3.0: Reuse SQL API implementations from embedded
Pavel Tupitsyn created IGNITE-22205: --- Summary: Java thin 3.0: Reuse SQL API implementations from embedded Key: IGNITE-22205 URL: https://issues.apache.org/jira/browse/IGNITE-22205 Project: Ignite Issue Type: Improvement Components: sql, thin client Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21604) .NET: Thin 3.0: Pass client time zone to server
[ https://issues.apache.org/jira/browse/IGNITE-21604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845192#comment-17845192 ] Pavel Tupitsyn commented on IGNITE-21604: - See https://stackoverflow.com/questions/62854935/is-there-a-way-to-convert-from-net-timezoneinfo-to-java-zoneddatetime > .NET: Thin 3.0: Pass client time zone to server > --- > > Key: IGNITE-21604 > URL: https://issues.apache.org/jira/browse/IGNITE-21604 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Pereslegin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > > Once IGNITE-21551 is implemented, it will be possible to set the time zone in > a user session. > The session time zone is taken into account when calling functions for > obtaining the current time (CURRENT_TIMESTAMP, etc), as well as when > processing a string literal for the 'TIMESTAMP WITH LOCAL TIME ZONE' type. > For this to work correctly, you need to transfer the client's time zone > through the thin client. > p.s. check the TODOs that point to this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19682) .NET: Thin 3.0: Tx partition awareness
[ https://issues.apache.org/jira/browse/IGNITE-19682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845191#comment-17845191 ] Pavel Tupitsyn commented on IGNITE-19682: - Merged to main: [1c0ee275624f07b1dab1a2c0a0307ae74ab0a579|https://github.com/apache/ignite-3/commit/1c0ee275624f07b1dab1a2c0a0307ae74ab0a579] > .NET: Thin 3.0: Tx partition awareness > -- > > Key: IGNITE-19682 > URL: https://issues.apache.org/jira/browse/IGNITE-19682 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3, performance > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, client sends a separate *TX_BEGIN* request when the user invokes > *ITransactions.BeginAsync* API: > * Extra network request. > * Chosen tx coordinator (server node that handles TX_BEGIN request) is random > and in most cases won't be the primary node for enlisted keys. > Solution: > * On the client, do not send *TX_BEGIN* request when the user invokes > *ITransactions.BeginAsync*. Instead, start the tx "on demand" when it is > first used in some API. > * Send two requests at once to the same node where the first enlisted > operation goes (according to partition awareness, if applicable). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22201) .NET: Use NetArchTest instead of manual parsing
[ https://issues.apache.org/jira/browse/IGNITE-22201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22201: Description: [ProjectFilesTests|https://github.com/apache/ignite-3/blob/main/modules/platforms/dotnet/Apache.Ignite.Tests/ProjectFilesTests.cs] uses primitive parsing to enforce architectural rules. This is fiddly and not reliable. We can use [NetArchTest|https://github.com/BenMorris/NetArchTest] instead (inspired by Java ArchUnit) > .NET: Use NetArchTest instead of manual parsing > --- > > Key: IGNITE-22201 > URL: https://issues.apache.org/jira/browse/IGNITE-22201 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Minor > Fix For: 3.0.0-beta2 > > > [ProjectFilesTests|https://github.com/apache/ignite-3/blob/main/modules/platforms/dotnet/Apache.Ignite.Tests/ProjectFilesTests.cs] > uses primitive parsing to enforce architectural rules. This is fiddly and > not reliable. > We can use [NetArchTest|https://github.com/BenMorris/NetArchTest] instead > (inspired by Java ArchUnit) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22201) .NET: Use NetArchTest instead of manual parsing
[ https://issues.apache.org/jira/browse/IGNITE-22201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-22201: Ignite Flags: (was: Docs Required,Release Notes Required) > .NET: Use NetArchTest instead of manual parsing > --- > > Key: IGNITE-22201 > URL: https://issues.apache.org/jira/browse/IGNITE-22201 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Minor > Fix For: 3.0.0-beta2 > > > [ProjectFilesTests|https://github.com/apache/ignite-3/blob/main/modules/platforms/dotnet/Apache.Ignite.Tests/ProjectFilesTests.cs] > uses primitive parsing to enforce architectural rules. This is fiddly and > not reliable. > We can use [NetArchTest|https://github.com/BenMorris/NetArchTest] instead > (inspired by Java ArchUnit) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22201) .NET: Use NetArchTest instead of manual parsing
Pavel Tupitsyn created IGNITE-22201: --- Summary: .NET: Use NetArchTest instead of manual parsing Key: IGNITE-22201 URL: https://issues.apache.org/jira/browse/IGNITE-22201 Project: Ignite Issue Type: Improvement Components: platforms, thin client Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22194) PlatformBenchmarkNodeRunner fails to start because it uses configuration property that no longer exists
[ https://issues.apache.org/jira/browse/IGNITE-22194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-22194. - Resolution: Fixed > PlatformBenchmarkNodeRunner fails to start because it uses configuration > property that no longer exists > --- > > Key: IGNITE-22194 > URL: https://issues.apache.org/jira/browse/IGNITE-22194 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Zhuravkov >Assignee: Maksim Zhuravkov >Priority: Trivial > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > PlatformBenchmarkNodeRunner uses portRange property that no longer exist and > fails start because of that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22194) PlatformBenchmarkNodeRunner fails to start because it uses configuration property that no longer exists
[ https://issues.apache.org/jira/browse/IGNITE-22194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844692#comment-17844692 ] Pavel Tupitsyn commented on IGNITE-22194: - Merged to main: 86bbb4322770b367ca380542b42ed0ea0a7db2f9 > PlatformBenchmarkNodeRunner fails to start because it uses configuration > property that no longer exists > --- > > Key: IGNITE-22194 > URL: https://issues.apache.org/jira/browse/IGNITE-22194 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Zhuravkov >Assignee: Maksim Zhuravkov >Priority: Trivial > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > PlatformBenchmarkNodeRunner uses portRange property that no longer exist and > fails start because of that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21992) Data Streamer removal does not work for a new key in the same batch
[
https://issues.apache.org/jira/browse/IGNITE-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-21992:
Ignite Flags: (was: Docs Required,Release Notes Required)
> Data Streamer removal does not work for a new key in the same batch
> ---
>
> Key: IGNITE-21992
> URL: https://issues.apache.org/jira/browse/IGNITE-21992
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When remove operation follows insert in the same batch, remove is ignored.
> See *ItAbstractDataStreamerTest#testSameItemInsertUpdateRemove*
> {code:java}
> @ParameterizedTest
> @ValueSource(ints = {1, 2, 3})
> public void testSameItemInsertUpdateRemove(int pageSize) {
> RecordView view = defaultTable().recordView();
> CompletableFuture streamerFut;
> int key = 333000;
> try (var publisher = new
> SubmissionPublisher>()) {
> streamerFut = view.streamData(publisher,
> DataStreamerOptions.builder().pageSize(pageSize).build());
> publisher.submit(DataStreamerItem.of(tuple(key, "foo")));
> publisher.submit(DataStreamerItem.removed(tupleKey(key)));
> }
> streamerFut.orTimeout(1, TimeUnit.SECONDS).join();
> assertNull(view.get(null, tupleKey(key)));
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
