[
https://issues.apache.org/jira/browse/IGNITE-24180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-24180:
---------------------------------------
Description:
Currently TX requests have dedicated timestamp field.
But the timestamp is already encoded in txId, so this field can be transient:
{code:java}
@Override
@Transient
default @Nullable HybridTimestamp timestamp() {
return TransactionIds.beginTimestamp(transactionId());
}{code}
was:
Currently TX messages have dedicated timestamp field.
But the timestamp is already encoded in txId, so this field can be transient:
{code:java}
@Override
@Transient
default @Nullable HybridTimestamp timestamp() {
return TransactionIds.beginTimestamp(transactionId());
}{code}
Summary: Remove timestamp physical field from TX requests. (was:
Remove timestamp physical field from TX messages.)
> Remove timestamp physical field from TX requests.
> -------------------------------------------------
>
> Key: IGNITE-24180
> URL: https://issues.apache.org/jira/browse/IGNITE-24180
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
>
> Currently TX requests have dedicated timestamp field.
> But the timestamp is already encoded in txId, so this field can be transient:
>
> {code:java}
> @Override
> @Transient
> default @Nullable HybridTimestamp timestamp() {
> return TransactionIds.beginTimestamp(transactionId());
> }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
