[teiid-issues] [JBoss JIRA] (TEIID-5144) Infinispan hotrod translator doesn't overcome error in unrelated proto-schema

Jan Stastny (JIRA) issues at jboss.org
Tue Nov 14 01:28:00 EST 2017


    [ https://issues.jboss.org/browse/TEIID-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489631#comment-13489631 ] 

Jan Stastny commented on TEIID-5144:
------------------------------------

[~rareddy] I am asking for such check, otherwise the usage is going to be painful.
What about actually checking the contents of the ".errors" string? Or isn't there such method in hotrod client?
As in jdg cli you can do sth like
{code}
/subsystem=datagrid-infinispan/cache-container=secured:get-proto-schemas-with-errors()
{code}
or
{code}
/subsystem=datagrid-infinispan/cache-container=secured:get-proto-schema-errors(file-name=/the/registered/file.proto)
{code}
and get the keys for the problematic proto-schemas or its contents.

> Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
> -----------------------------------------------------------------------------
>
>                 Key: TEIID-5144
>                 URL: https://issues.jboss.org/browse/TEIID-5144
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDG Connector, Misc. Connectors
>    Affects Versions: 8.12.x-6.4
>            Reporter: Jan Stastny
>            Assignee: Ramesh Reddy
>
> Infinispan Hotrod translator can't overcome an error in any proto-schema on the JDG server.
> It ends with a message, that there's an issue with a proto-schema. Doesn't say which.
> Note, that this can be completely unrelated proto-schema to Teiid. Then the only solution is to reload JDG, or possibly clear proto-schema cache.
> If Teiid is checking for errors in .errors cache, it should be selective and look only for the newly added proto-schema.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the teiid-issues mailing list