[
https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin...
]
Van Halbert edited comment on TEIID-5449 at 10/5/18 8:10 AM:
-------------------------------------------------------------
After looking deeper at the code, the doc filtering is done by the teiid query evaluator.
Which wouldn't it be better to apply the filter when the infinispan query is being
issued, and push the filtering to the source? Yes, the infinispan query language is
more limiting that what Teiid can evaluate, but I think that filtering (what infinispan
doesn't support) could then be done in the translator.
was (Author: van.halbert):
[~rareddy] Does the marshaller that is registered in the client, is that logic performed
on the client or pushed to the server? Reading the docs, its not clear, but seem to
imply its done on the client, so I wasnt' sure if you have already made that
determination.
Infinispan: Update Infinispan translator to 9.3 version
-------------------------------------------------------
Key: TEIID-5449
URL:
https://issues.jboss.org/browse/TEIID-5449
Project: Teiid
Issue Type: Bug
Components: Infinispan
Affects Versions: 11.0
Reporter: Ramesh Reddy
Assignee: Van Halbert
Priority: Major
Fix For: 11.2
Two changes observed
- The new cache create API changed, the old has been deprecated
- cache.get(key) now became Async operation, that means Thread Based serialization
context no longer works. This needs to be removed, but there seem to be no better
alternatives to support the Async threads.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)