[ https://issues.apache.org/jira/browse/IGNITE-17124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timur Magomedov updated IGNITE-17124: ------------------------------------- Fix Version/s: 3.0.0-alpha6 (was: 3.0) > 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 > > > 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)