[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Release Note:
Generally speaking, added an ability to run read-only transactions using KV API.
Particularly following methods were added to IgniteTransactions and
Transaction interfaces:
- IgniteTransactoins#readOnly method is added to IgniteTransactoins. This one
returns a decorated {@code IgniteTransactions} instance that will start
read-only transactions.
- Transaction#isReadOnly in order to check whether given transaction is
read-only.
- Transaction#readTimestamp - returns read timestamp for the given transaction
if it is a read-only one or {code null} otherwise.
was:
- readOnly() method is added to IgniteTransactoins. This one returns a
decorated {@code IgniteTransactions} instance that will start read-only
transactions.
- Following methods are added to Transaction interface
/**
* Returns {code true} if given transaction is a read-only, {@code false
otherwise}.
*
* @return {code true} if given transaction is a read-only, {@code false
otherwise}.
*/
boolean isReadOnly();
/**
* Returns read timestamp for the given transaction if it is a read-only
one or {code null} otherwise.
*
* @return Read timestamp for the given transaction if it is a read-only
one or {code null} otherwise.
*/
HybridTimestamp readTimestamp();
Generally speaking, added an ability to run read-only transactions using kv API.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
> Fix For: 3.0.0-beta1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp readTimestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
> {code:java}
> CompletableFuture get(
> BinaryRowEx keyRow,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
> {code}
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Release Note:
Generally speaking, added an ability to run read-only transactions using KV API.
Particularly following methods were added to IgniteTransactions and
Transaction interfaces:
- IgniteTransactoins#readOnly method is added to IgniteTransactoins. This one
returns a decorated {@code IgniteTransactions} instance that will start
read-only transactions.
- Transaction#isReadOnly in order to check whether given transaction is
read-only.
- Transaction#readTimestamp - returns read timestamp for the given transaction
if it is a read-only one or {code null} otherwise.
was:
Generally speaking, added an ability to run read-only transactions using KV API.
Particularly following methods were added to IgniteTransactions and
Transaction interfaces:
- IgniteTransactoins#readOnly method is added to IgniteTransactoins. This one
returns a decorated {@code IgniteTransactions} instance that will start
read-only transactions.
- Transaction#isReadOnly in order to check whether given transaction is
read-only.
- Transaction#readTimestamp - returns read timestamp for the given transaction
if it is a read-only one or {code null} otherwise.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
> Fix For: 3.0.0-beta1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp readTimestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
> {code:java}
> CompletableFuture get(
> BinaryRowEx keyRow,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
> {code}
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Release Note:
- readOnly() method is added to IgniteTransactoins. This one returns a
decorated {@code IgniteTransactions} instance that will start read-only
transactions.
- Following methods are added to Transaction interface
/**
* Returns {code true} if given transaction is a read-only, {@code false
otherwise}.
*
* @return {code true} if given transaction is a read-only, {@code false
otherwise}.
*/
boolean isReadOnly();
/**
* Returns read timestamp for the given transaction if it is a read-only
one or {code null} otherwise.
*
* @return Read timestamp for the given transaction if it is a read-only
one or {code null} otherwise.
*/
HybridTimestamp readTimestamp();
Generally speaking, added an ability to run read-only transactions using kv API.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
> Fix For: 3.0.0-beta1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp readTimestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
> {code:java}
> CompletableFuture get(
> BinaryRowEx keyRow,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
> {code}
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp readTimestamp();{code}
methods.
And finally three more overloaded methods will be added to the InternalTable
{code:java}
CompletableFuture get(
BinaryRowEx keyRow,
@NotNull HybridTimestamp readTimestamp,
@NotNull ClusterNode recipientNode
);
CompletableFuture> getAll(
Collection keyRows,
@NotNull HybridTimestamp readTimestamp,
@NotNull ClusterNode recipientNode
);
Publisher scan(
int p,
@NotNull HybridTimestamp readTimestamp,
@NotNull ClusterNode recipientNode
);
{code}
Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
is added.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
And finally three more overloaded methods will be added to the InternalTable
{code:java}
CompletableFuture get(
BinaryRowEx keyRow,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
CompletableFuture> getAll(
Collection keyRows,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
Publisher scan(
int p,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
{code}
Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
is added.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
> Fix For: 3.0.0-beta1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp readTimestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
> {code:java}
> CompletableFuture get(
> BinaryRowEx keyRow,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @NotNull HybridTimestamp readTimestamp,
> @NotNull ClusterNode recipientNode
> );
> {code}
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Fix Version/s: 3.0.0-beta1
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
> Fix For: 3.0.0-beta1
>
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp timestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
> {code:java}
> CompletableFuture get(
> BinaryRowEx keyRow,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
> {code}
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
And finally three more overloaded methods will be added to the InternalTable
{code:java}
CompletableFuture get(
BinaryRowEx keyRow,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
CompletableFuture> getAll(
Collection keyRows,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
Publisher scan(
int p,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
{code}
Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
is added.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
And finally three more overloaded methods will be added to the InternalTable
{code:java}
CompletableFuture get(
BinaryRowEx keyRow,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
CompletableFuture> getAll(
Collection keyRows,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
Publisher scan(
int p,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
{code}
Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
is added.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp timestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
> {code:java}
> CompletableFuture get(
> BinaryRowEx keyRow,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
> {code}
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
And finally three more overloaded methods will be added to the InternalTable
{code:java}
CompletableFuture get(
BinaryRowEx keyRow,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
CompletableFuture> getAll(
Collection keyRows,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
Publisher scan(
int p,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
{code}
Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
is added.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
And finally three more overloaded methods will be added to the InternalTable
```
CompletableFuture get(
BinaryRowEx keyRow,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
CompletableFuture> getAll(
Collection keyRows,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
Publisher scan(
int p,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
```
Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
is added.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp timestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
>
> {code:java}
> CompletableFuture get(
> BinaryRowEx keyRow,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
> {code}
>
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
And finally three more overloaded methods will be added to the InternalTable
```
CompletableFuture get(
BinaryRowEx keyRow,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
CompletableFuture> getAll(
Collection keyRows,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
Publisher scan(
int p,
@Nullable InternalTransaction tx,
@NotNull ClusterNode recipientNode
);
```
Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
is added.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp timestamp();{code}
> methods.
> And finally three more overloaded methods will be added to the InternalTable
> ```
> CompletableFuture get(
> BinaryRowEx keyRow,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> CompletableFuture> getAll(
> Collection keyRows,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
>
> Publisher scan(
> int p,
> @Nullable InternalTransaction tx,
> @NotNull ClusterNode recipientNode
> );
> ```
> Please, pay attention, that new parameter @NotNull ClusterNode recipientNode
> is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so following decorator producer is expected in IgniteTransactions
{code:java}
/**
* Decorated {@code IgniteTransactions} instance that will start read-only
transactions.
*
* @return Decorated {@code IgniteTransactions} instance that will start
read-only transactions.
*/
IgniteTransactions readOnly(); {code}
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so that new methods similar to
{code:java}
Transaction begin(boolean readOnly){code}
and
{code:java}
CompletableFuture beginAsync(boolean readOnly){code}
should be added to IgniteTransactions together with corresponding
implementation.
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so following decorator producer is expected in IgniteTransactions
> {code:java}
> /**
> * Decorated {@code IgniteTransactions} instance that will start read-only
> transactions.
> *
> * @return Decorated {@code IgniteTransactions} instance that will start
> read-only transactions.
> */
> IgniteTransactions readOnly(); {code}
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp timestamp();{code}
> methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so that new methods similar to
{code:java}
Transaction begin(boolean readOnly){code}
and
{code:java}
CompletableFuture beginAsync(boolean readOnly){code}
should be added to IgniteTransactions together with corresponding
implementation.
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so that overloaded versions
{code:java}
Transaction begin(HybridTimestamp timestamp){code}
and
{code:java}
CompletableFuture beginAsync(HybridTimestamp timestamp){code}
should be added to IgniteTransactions together with corresponding
implementation.
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so that new methods similar to
> {code:java}
> Transaction begin(boolean readOnly){code}
> and
> {code:java}
> CompletableFuture beginAsync(boolean readOnly){code}
> should be added to IgniteTransactions together with corresponding
> implementation.
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp timestamp();{code}
> methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so that overloaded versions
{code:java}
Transaction begin(HybridTimestamp timestamp){code}
and
{code:java}
CompletableFuture beginAsync(HybridTimestamp timestamp){code}
should be added to IgniteTransactions together with corresponding
implementation.
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
HybridTimestamp timestamp();{code}
methods.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so that overloaded versions
{code:java}
Transaction begin(HybridTimestamp timestamp){code}
and
{code:java}
CompletableFuture beginAsync(HybridTimestamp timestamp){code}
should be added to IgniteTransactions together with corresponding
implementation.
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
long timestamp();{code}
methods.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so that overloaded versions
> {code:java}
> Transaction begin(HybridTimestamp timestamp){code}
> and
> {code:java}
> CompletableFuture beginAsync(HybridTimestamp timestamp){code}
> should be added to IgniteTransactions together with corresponding
> implementation.
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> HybridTimestamp timestamp();{code}
> methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
[
https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17260:
-
Description:
It's required to explicitly register an intent of starting readOnly
transaction, so that overloaded versions
{code:java}
Transaction begin(HybridTimestamp timestamp){code}
and
{code:java}
CompletableFuture beginAsync(HybridTimestamp timestamp){code}
should be added to IgniteTransactions together with corresponding
implementation.
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
long timestamp();{code}
methods.
was:
It's required to explicitly register an intent of starting readOnly
transaction, so that overloaded versions
{code:java}
Transaction begin(long timestamp){code}
and
{code:java}
CompletableFuture beginAsync(long timestamp){code}
should be added to IgniteTransactions together with corresponding
implementation.
Besides that Transaction interface should be extended with
{code:java}
boolean isReadOnly();{code}
and
{code:java}
long timestamp();{code}
methods.
> Enrich IgniteTransactions and Transaction interfaces with RO related methods
>
>
> Key: IGNITE-17260
> URL: https://issues.apache.org/jira/browse/IGNITE-17260
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3, transaction3_ro
>
> It's required to explicitly register an intent of starting readOnly
> transaction, so that overloaded versions
> {code:java}
> Transaction begin(HybridTimestamp timestamp){code}
> and
> {code:java}
> CompletableFuture beginAsync(HybridTimestamp timestamp){code}
> should be added to IgniteTransactions together with corresponding
> implementation.
> Besides that Transaction interface should be extended with
> {code:java}
> boolean isReadOnly();{code}
> and
> {code:java}
> long timestamp();{code}
> methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
Title: Message Title
Alexander Lapin updated an issue
Ignite / IGNITE-17260
Enrich IgniteTransactions and Transaction interfaces with RO related methods
Change By:
Alexander Lapin
It's required to explicitly register an intent of starting readOnly transaction, so that overloaded versions {code:java}Transaction begin( boolean readOnly long timestamp ){code} and{code:java}CompletableFuture beginAsync( boolean readOnly long timestamp ){code}should be added to IgniteTransactions together with corresponding implementation.Besides that Transaction interface should be extended with{code:java}boolean isReadOnly();{code} method. and {code:java}long timestamp();{code} methods.
Add Comment
This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Updated] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods
Title: Message Title
Alexander Lapin updated an issue
Ignite / IGNITE-17260
Enrich IgniteTransactions and Transaction interfaces with RO related methods
Change By:
Alexander Lapin
It's required to explicitly register an intent of starting readOnly transaction, so that overloaded versions {code:java}Transaction begin(boolean readOnly){code} and{code:java}CompletableFuture beginAsync(boolean readOnly){code}should be added to IgniteTransactions together with corresponding implementation.Besides that Transaction interface should be extended with{code:java}boolean isReadOnly();{code}method.
Add Comment
This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
