[jira] [Updated] (IGNITE-14488) Implement invoke operations for table views.

["Andrey Mashenkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-14488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Mashenkov updated IGNITE-14488:
--------------------------------------
    Description: 
Implement invoke operation for all Table views (Table/KV, binary/non-binary).

* Invoke processor input depends on a view the user calls an invoke() method on.
Thus, a view type should be a part of an atomic/tx protocol and 
* InvocationContext should convert a Row to expected types on server-side.
* Any exceptions related to InvokeProc and/or it's arguments deserialization failure or a Row deserialization failure MUST be described in the javadoc to invoke() methods and correctly handled.





  was:
Implement Table binary projection API.
Extend existed tests to all table operations 
Example class is a good start point.



> Implement invoke operations for table views.
> --------------------------------------------
>
>                 Key: IGNITE-14488
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14488
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Mashenkov
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: iep-54, ignite-3
>
> Implement invoke operation for all Table views (Table/KV, binary/non-binary).
> * Invoke processor input depends on a view the user calls an invoke() method on.
> Thus, a view type should be a part of an atomic/tx protocol and 
> * InvocationContext should convert a Row to expected types on server-side.
> * Any exceptions related to InvokeProc and/or it's arguments deserialization failure or a Row deserialization failure MUST be described in the javadoc to invoke() methods and correctly handled.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)