[jira] [Commented] (IGNITE-14886) Binary metadata registration in EntryProcessor fails after CREATE TABLE with same type

["Veena Mithare (Jira)" <ji...@apache.org>]

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

Veena Mithare commented on IGNITE-14886:
----------------------------------------

 As per the definition of entry processor - it is used to execute updates on entries on
the nodes that store it - currently this is not the case. It runs on the client side as well. 

 

Will this issue not be resolved if the entry processor ran only on the server nodes.

 

> Binary metadata registration in EntryProcessor fails after CREATE TABLE with same type
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-14886
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14886
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Anton Kurbanov
>            Priority: Major
>         Attachments: BinaryObjectEntryProcessorTest.java
>
>
> https://ignite.apache.org/docs/latest/key-value-api/binary-objects#creating-and-modifying-binary-objects
> This part of documentation assumes that binary object can be processed/created/modified within the EntryProcessor, however in this case it is no longer working unless the type is manually registered before executing the invoke or create table is removed, which renders this documentation part incorrect.
> This situation happens since the attempt to fix metadata registration deadlock here: https://issues.apache.org/jira/browse/IGNITE-11313
> Failing test attached.



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