[JBoss JIRA] (TEIID-5144) Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
by Jan Stastny (JIRA)
Jan Stastny created TEIID-5144:
----------------------------------
Summary: 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: Steven Hawkins
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)
7 years, 2 months
[JBoss JIRA] (TEIID-5143) Infinispan hotrod translator proto-schema registered as ProtoFilePath
by Jan Stastny (JIRA)
Jan Stastny created TEIID-5143:
----------------------------------
Summary: Infinispan hotrod translator proto-schema registered as ProtoFilePath
Key: TEIID-5143
URL: https://issues.jboss.org/browse/TEIID-5143
Project: Teiid
Issue Type: Bug
Components: JDG Connector, Misc. Connectors
Affects Versions: 8.12.x-6.4
Reporter: Jan Stastny
Assignee: Steven Hawkins
Priority: Critical
When using an existing protobuf file to configure source metadata and providing full path via ProtoFilePath, there are issues with how the proto-schema is being registered in JDG.
When using ProtoFilePath, the proto-schema is being registered under the exact value of this property. This is unexpected and source of many issues. Rather the proto-schema should be registered under the package context.
This leads to a situation, when using the same file on various machines, or when the file is moved, then the proto-schema is being registered twice with different keys in JDG proto-schema cache, this leads to an exception on JDG's side and non-deployed VDB.
I expect the ProtobufName to be a complementary to ProtoFilePath:
# I register a proto-schema using ProtoFilePath property
# I use that schema in different VDB using ProtobufName property
Then the ProtobufName used in second case needs to contain exactly the same value as ProtoFilePath in the first case. This is hard to understand.
Could the change be to:
# Set both ProtoFilePath and ProtobufName properties (ProtobufName is our logical descriptor) when a user want to register new protobuf file. This way the contents of a file denoted by ProtoFilePath is registered in JDG under ProtobufName key.
# Using only ProtobufName when an already registered proto-schema is to be used.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5057) Infinispan Hotrod error when '-' in Source model name
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5057?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5057:
------------------------------------------------
David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1489833|https://bugzilla.redhat.com/show_bug.cgi?id=1489833] from MODIFIED to ON_QA
> Infinispan Hotrod error when '-' in Source model name
> -----------------------------------------------------
>
> Key: TEIID-5057
> URL: https://issues.jboss.org/browse/TEIID-5057
> Project: Teiid
> Issue Type: Bug
> Components: Documentation, JDG Connector, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> There are different constraints on Source model name in Teiid and query passed through hotrod client.
> For a source model:
> {code:xml|title=Source model}
> <model name="Source-1" type="PHYSICAL" visible="true">
> <source name="jdg7-source-1" translator-name="infinispan-hotrod" connection-jndi-name="java:/jdg71HotrodDS" />
> <metadata type="DDL"><![CDATA[
> CREATE FOREIGN TABLE SmallA (
> StringKey string PRIMARY KEY,
> DoubleNum double
> ) OPTIONS(UPDATABLE true, "teiid_ispn:cache" 'cache_name');
> ]]>
> </metadata>
> <metadata type = "NATIVE"/>
> </model>
> {code}
> The vdb becomes active:
> {code:title=server.log}
> 14:29:40,953 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (teiid-async-threads - 3) TEIID40003 VDB jdg71_crud.1 is set to ACTIVE
> {code}
> Then on query:
> {code:sql|title=select query}
> SELECT * FROM SMallA
> {code}
> Following error occurs in Teiid:
> {code:title=server.log}
> 14:29:49,350 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker3_QueryProcessorQueue7) ISPN004005: Error received from the server: org.infinispan.objectfilter.ParsingException: ISPN028526: Invalid query: SELECT g_0.StringKey, g_0.DoubleNum FROM Source-1.SmallA g_0 ; Parser error messages: [[statement, selectStatement, querySpec, selectFrom, fromClause, persisterSpaces, persisterSpace, persisterSpaceRoot, mainEntityPersisterReference, aliasClause]: line 1:47 state 0 (decision=22) no viable alt; token=[@14,47:47='-',<84>,1:47], [statement]: line 1:50 mismatched token: [@16,50:55='SmallA',<59>,1:50]; expecting type EOF].
> 14:29:49,351 ERROR [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue7) Connector worker process failed for atomic-request=429MasxTtgFj.0.0.2: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=29 returned server error (status=0x85): org.infinispan.objectfilter.ParsingException: ISPN028526: Invalid query: SELECT g_0.StringKey, g_0.DoubleNum FROM Source-1.SmallA g_0 ; Parser error messages: [[statement, selectStatement, querySpec, selectFrom, fromClause, persisterSpaces, persisterSpace, persisterSpaceRoot, mainEntityPersisterReference, aliasClause]: line 1:47 state 0 (decision=22) no viable alt; token=[@14,47:47='-',<84>,1:47], [statement]: line 1:50 mismatched token: [@16,50:55='SmallA',<59>,1:50]; expecting type EOF].
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53) [infinispan-client-hotrod-8.4.0.Final-redhat-2.jar:8.4.0.Final-redhat-2]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.fetchNextBatch(InfinispanResponse.java:74) [translator-infinispan-hotrod-8.12.11.6_4-redhat-6.jar:8.12.11.6_4-redhat-6]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:90) [translator-infinispan-hotrod-8.12.11.6_4-redhat-6.jar:8.12.11.6_4-redhat-6]
> at org.teiid.translator.infinispan.hotrod.InfinispanQueryExecution.next(InfinispanQueryExecution.java:136) [translator-infinispan-hotrod-8.12.11.6_4-redhat-6.jar:8.12.11.6_4-redhat-6]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:433) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at com.sun.proxy.$Proxy79.more(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_121]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> 14:29:49,356 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue8) TEIID30020 Processing exception for request 429MasxTtgFj.0 'TEIID30504 jdg7-source-1: org.infinispan.objectfilter.ParsingException: ISPN028526: Invalid query: SELECT g_0.StringKey, g_0.DoubleNum FROM Source-1.SmallA g_0 ; Parser error messages: [[statement, selectStatement, querySpec, selectFrom, fromClause, persisterSpaces, persisterSpace, persisterSpaceRoot, mainEntityPersisterReference, aliasClause]: line 1:47 state 0 (decision=22) no viable alt; token=[@14,47:47='-',<84>,1:47], [statement]: line 1:50 mismatched token: [@16,50:55='SmallA',<59>,1:50]; expecting type EOF].'. Originally TeiidProcessingException Codec20.java:363. Enable more detailed logging to see the entire stacktrace.
> {code}
> And in JDG's log:
> {code:title=JDG log}
> 08:29:49,267 ERROR [stderr] (HotRod-hotrod-securedServerHandler-10-30) line 1:47 no viable alternative at input '-'
> {code}
> The issue is '-' in Source model's name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-3722) Add an option to not widen comparisons to string
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3722?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3722:
------------------------------------------------
David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1460324|https://bugzilla.redhat.com/show_bug.cgi?id=1460324] from ASSIGNED to ON_QA
> Add an option to not widen comparisons to string
> ------------------------------------------------
>
> Key: TEIID-3722
> URL: https://issues.jboss.org/browse/TEIID-3722
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example:
> int_col = '1a'
> will effectively become cast(int_col as string) = '1a'
> Or with timestamps:
> timestamp_col = '1970-01-01'
> becomes cast(timestamp_col as string) = '1970-01-01'
> In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion.
> This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5122) Osisoft Translator - Teiid pushes cast from Boolean to Single/Double
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-5122?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-5122:
-------------------------------
Fix Version/s: 8.12.x-6.4
> Osisoft Translator - Teiid pushes cast from Boolean to Single/Double
> --------------------------------------------------------------------
>
> Key: TEIID-5122
> URL: https://issues.jboss.org/browse/TEIID-5122
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Fix For: 8.12.x-6.4, 10.1
>
>
> Osisoft PI does not support conversion from Boolean to Single or Double, however, query such as
> {code:sql}
> select cast(booleanvalue as float) from Source.smalla
> {code}
> is pushed as
> {code:sql}
> SELECT cast(g_0.BooleanValue AS Single) AS c_0 FROM dvqe..SmallA AS g_0
> {code}
> which results in
> {noformat}
> com.osisoft.rdsa.RdsaException: [PIOLEDBENT] [SQL Analyzer] [Line 1:14] Cannot cast 'Boolean' to 'Single'.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5138) JGroups Channel creation in domain mode is invalid
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5138?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-5138:
--------------------------------
Fix Version/s: 10.1
> JGroups Channel creation in domain mode is invalid
> --------------------------------------------------
>
> Key: TEIID-5138
> URL: https://issues.jboss.org/browse/TEIID-5138
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 10.1
>
>
> In domain mode configuration where the JGroups channel is configured, it is configured to be used as a separate channel where it would require separate protocol stack, which is also discouraged form. The suggested configuration is to create a forked channel as
> {code}
> <channel name="ee" stack="udp" cluster="ejb">
> <fork name="teiid-cluster"/>
> </channel>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5138) JGroups Channel creation in domain mode is invalid
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5138?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-5138:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> JGroups Channel creation in domain mode is invalid
> --------------------------------------------------
>
> Key: TEIID-5138
> URL: https://issues.jboss.org/browse/TEIID-5138
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 10.1
>
>
> In domain mode configuration where the JGroups channel is configured, it is configured to be used as a separate channel where it would require separate protocol stack, which is also discouraged form. The suggested configuration is to create a forked channel as
> {code}
> <channel name="ee" stack="udp" cluster="ejb">
> <fork name="teiid-cluster"/>
> </channel>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5140) Teiid 10 postgres driver version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5140?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5140:
---------------------------------------
I'll update both the pg odbc and jdbc guidelines and investigate this specific message. It looks like we should may need to add more default exclusions.
> Teiid 10 postgres driver version
> --------------------------------
>
> Key: TEIID-5140
> URL: https://issues.jboss.org/browse/TEIID-5140
> Project: Teiid
> Issue Type: Bug
> Reporter: Lukáš Svačina
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.1
>
>
> I tried several drivers from https://jdbc.postgresql.org/download.html and figured out that 9.4-1203 JDBC 42 is the newest working driver for my application.
>
> Newer drivers cause Teiid to fail on datasource creation with error "Reason:TEIID60011 No column found on table xxxx.pg_toast.pg_toast_16446 with name chunk_id"
> Please update docs about what driver version is recommended (or tested) and if there is any reason to update to newer postgres drivers (what benefits it brings and how teiid uses it).
> Might be good idea to ship driver within teiid package or at least keep updated _docs\teiid\datasources\postgresql\readme.txt_ to contain recommended driver name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5140) Teiid 10 postgres driver version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5140?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5140:
----------------------------------
Fix Version/s: 10.1
10.0.1
> Teiid 10 postgres driver version
> --------------------------------
>
> Key: TEIID-5140
> URL: https://issues.jboss.org/browse/TEIID-5140
> Project: Teiid
> Issue Type: Bug
> Reporter: Lukáš Svačina
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.1
>
>
> I tried several drivers from https://jdbc.postgresql.org/download.html and figured out that 9.4-1203 JDBC 42 is the newest working driver for my application.
>
> Newer drivers cause Teiid to fail on datasource creation with error "Reason:TEIID60011 No column found on table xxxx.pg_toast.pg_toast_16446 with name chunk_id"
> Please update docs about what driver version is recommended (or tested) and if there is any reason to update to newer postgres drivers (what benefits it brings and how teiid uses it).
> Might be good idea to ship driver within teiid package or at least keep updated _docs\teiid\datasources\postgresql\readme.txt_ to contain recommended driver name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months