You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Belyak (Jira)" <ji...@apache.org> on 2021/11/16 07:38:00 UTC
[jira] [Commented] (IGNITE-15893) Extend table views test coverage.
[ https://issues.apache.org/jira/browse/IGNITE-15893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444324#comment-17444324 ]
Alexander Belyak commented on IGNITE-15893:
-------------------------------------------
[~amashenkov] please take a look at PR.
> Extend table views test coverage.
> ---------------------------------
>
> Key: IGNITE-15893
> URL: https://issues.apache.org/jira/browse/IGNITE-15893
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Andrey Mashenkov
> Assignee: Alexander Belyak
> Priority: Major
> Labels: iep-54, ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Motivation.
> As for now, there are separate test suites for KV view, Record view, and binary views test suites, but there are no interop tests.
> E.g. put row using KV API, and get row using record or binary.
> I've found, colums with the same name can exist in key and value parts, and this works fine with KV view.
> Obviously, this will not work with the RecordBinary view, and no workaround is possible.
> Description.
> Let's add interop tests to check the data added via some table view accessible via other views.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)