[
https://issues.jboss.org/browse/TEIID-5144?page=com.atlassian.jira.plugin...
]
Jan Stastny commented on TEIID-5144:
------------------------------------
[~rareddy]
Feel free to reduce the priority as you see fit. I wanted to stress the fact, that
Teiid's functionality may be adversely affected by another entity accessing shared JDG
instance.
what's the ".errors" cache
My mistake, it is not
a cache, but an entry suffix in a metadata cache. See [this
line|https://github.com/teiid/jdg/blob/4162be7b01cffc68db232b630a7195c73d...].
The metadata cache can contain ".errors" key suffix but for different
protoBufResource (talking about a variable in the code linked above).
So, how is a "bad" proto-stream file introduced? by User?
Yes, by a user. I could get there by trying register same protobuf file under two
different keys in JDG. Which is kinda invalid state, though in my view if there's a
way to help Teiid overcome this issue, it's worth pursuing.
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
Priority: Blocker
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)