You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2022/12/23 08:11:00 UTC

[jira] [Comment Edited] (IGNITE-17467) Find out Row id is not possible for MvPartitionStorage

    [ https://issues.apache.org/jira/browse/IGNITE-17467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651538#comment-17651538 ] 

Roman Puchkovskiy edited comment on IGNITE-17467 at 12/23/22 8:10 AM:
----------------------------------------------------------------------

The API has changed since the issue was filed. Now we agreed upon the following: we just need to add {{RowId}} to {{{}ReadResult{}}}, so {{ReadResult}} will now have a method with the following signature:

{{RowId rowId();}}


was (Author: rpuch):
The API has changed since the issue was filed. Now we agreed upon the following: we just need to add `RowId` to `ReadResult`, so `ReadResult` will now have a method with the following signature:

{{RowId rowId();}}

> Find out Row id is not possible for MvPartitionStorage
> ------------------------------------------------------
>
>                 Key: IGNITE-17467
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17467
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> Row id is returned only for insert operation, but if you want to find a row id by Binary row is not possible.
> I sure, it has to be possible through scan operation. In that case, the scan operation can be used as a scan index.
> I would like to see API like:
> {code:java}
> Cursor<Tuple<RowId, BinaryRow>> scan(Predicate<BinaryRow> keyFilter, UUID txId) throws TxIdMismatchException, StorageException;
> Cursor<Tuple<RowId, BinaryRow>> scan(Predicate<BinaryRow> keyFilter, Timestamp timestamp) throws StorageException;
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)