You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2022/06/10 13:26:00 UTC
[jira] [Commented] (IGNITE-17124) Storage API tests can't be used for storages with specific binary format
[ https://issues.apache.org/jira/browse/IGNITE-17124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552752#comment-17552752 ]
Kirill Tkalenko commented on IGNITE-17124:
------------------------------------------
[~tmagomedov] Looks good to me!
> Storage API tests can't be used for storages with specific binary format
> ------------------------------------------------------------------------
>
> Key: IGNITE-17124
> URL: https://issues.apache.org/jira/browse/IGNITE-17124
> Project: Ignite
> Issue Type: Improvement
> Reporter: Timur Magomedov
> Assignee: Timur Magomedov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Storages that need to get table UUID or rely on some specific binary format of DataRow can't be tested using AbstractPartitionStorageTest. This works for key-value storages that don't decode key and value of DataRow/SearchRow and don't use table UUID but will fail once such storages are implemented or existing ones will decode data binaries.
> Two main issues here are the following:
> 1. searchRow() and dataRow() methods in AbstractPartitionStorageTest can't be overridden since they are static methods.
> 2. Table UUID is always null in Storage API tests.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)