April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-69) The example fails to deploy

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-69: ------------------------------------- Summary: The example fails to deploy Key: TEIIDSB-69 URL: https://issues.jboss.org/browse/TEIIDSB-69 Project: Teiid Spring Boot Issue Type: Bug Components: examples Reporter: Steven Hawkins Assignee: Steven Hawkins Starting with a fresh install of minishift using 3.10 or 3.11 and running the rdbms example, it won't come up and a manual deployment will show: Reason: cannot trigger a deployment for "rdbms-example" because it contains unresolved images This appears to be because the deployment config references teiid-dataservice/rdbms-example:1.1.0-SNAPSHOT, but only latest exists. This is due to the last commit that updated the versions. Apparently fabric8 will not create a label based upon a snapshot version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-65) OData include files are not being served correctly

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-65: --------------------------------------- [~rareddy] there's also the potential for conflict with the probes correct? /actuator/health > OData include files are not being served correctly > -------------------------------------------------- > > Key: TEIIDSB-65 > URL: https://issues.jboss.org/browse/TEIIDSB-65 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.1.0 > > > The include metadata files are not being served correctly through OData interface. > One of the reference is calculated as http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor... > The class tries to request from this include url and this is what causes the 406 error > see $metadata int he URL -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5720) PSQL client fails to report the metadata

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5720: ----------------------------------- Summary: PSQL client fails to report the metadata Key: TEIID-5720 URL: https://issues.jboss.org/browse/TEIID-5720 Project: Teiid Issue Type: Bug Components: ODBC Reporter: Ramesh Reddy Assignee: Steven Hawkins When using psql client and issuing the "\dt" command I see this exception instead of returning the table names. {code} WARN: TEIID30020 Processing exception for request grF9mx6fyMfD.1 'TEIID30082 Expected value of type 'char' but '''' is of type 'string' and no implicit conversion is available.'. Originally QueryResolverException ResolverUtil.java:230. org.teiid.api.exception.query.QueryResolverException: TEIID30082 Expected value of type 'char' but '''' is of type 'string' and no implicit conversion is available. at org.teiid.query.resolver.util.ResolverUtil.convertExpression(ResolverUtil.java:230) at org.teiid.query.resolver.util.ResolverVisitor.resolveSetCriteria(ResolverVisitor.java:1203) at org.teiid.query.resolver.util.ResolverVisitor.visit(ResolverVisitor.java:294) at org.teiid.query.sql.lang.SetCriteria.acceptVisitor(SetCriteria.java:96) at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:50) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:57) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.postVisitVisitor(SimpleQueryResolver.java:229) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:345) at org.teiid.query.sql.lang.SetCriteria.acceptVisitor(SetCriteria.java:96) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:59) at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:72) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:135) at org.teiid.query.sql.lang.CompoundCriteria.acceptVisitor(CompoundCriteria.java:231) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:59) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:244) at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:66) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:178) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:120) at org.teiid.dqp.internal.process.Request.resolveCommand(Request.java:282) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:418) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:486) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:672) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:351) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:285) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:124) at org.teiid.dqp.internal.process.ThreadReuseExecutor$2.run(ThreadReuseExecutor.java:212) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-64) Research HA

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-64?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-64: --------------------------------------- Testing with sessionAffinity: ClientIP on the service seems to work. I'll look at the route next. > Research HA > ----------- > > Key: TEIIDSB-64 > URL: https://issues.jboss.org/browse/TEIIDSB-64 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > Teiid's pg, and jdbc assume session affinity. Also OData pagination works best with session affinity. > For HA, and horizontal scaling, it would be good to have more than 1 pod alive and receiving traffic. It appears that there is a sessionAffinity setting at a service level https://kubernetes.io/docs/concepts/services-networking/service/ and some work that can be done to customize routes https://docs.openshift.com/container-platform/3.9/architecture/networking... - but that doesn't appear to work for just tcp traffic. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5718) Provide a flag to disable alter statements

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5718?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5718: --------------------------------------- There's TEIIDSB-47 for that. I'm thinking that the default should be to disable. > Provide a flag to disable alter statements > ------------------------------------------ > > Key: TEIID-5718 > URL: https://issues.jboss.org/browse/TEIID-5718 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > The engine allows alter statements to ephemerally (by default) change view definitions, turn on/off triggers, etc. For Spring Boot and OpenShift deployment in particular we should consider whether this should be allowable/optional behavior. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5718) Provide a flag to disable alter statements

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5718?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5718: ------------------------------------- should we add this to SB port to disable ALTER? > Provide a flag to disable alter statements > ------------------------------------------ > > Key: TEIID-5718 > URL: https://issues.jboss.org/browse/TEIID-5718 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > The engine allows alter statements to ephemerally (by default) change view definitions, turn on/off triggers, etc. For Spring Boot and OpenShift deployment in particular we should consider whether this should be allowable/optional behavior. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5719) Allow unqualified temporary table names to contain .

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5719?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5719. ----------------------------------- Resolution: Done Updated the logic to restrict parsing rather than having a hard coded check in the resolver logic. > Allow unqualified temporary table names to contain . > ---------------------------------------------------- > > Key: TEIID-5719 > URL: https://issues.jboss.org/browse/TEIID-5719 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > If you issue something like: > create local temporary table "some.table" ... > The resovler will not allow the table name. > That should be allowed, and instead the parser should reject unqualified names such as: > create local temporary table some.table ... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5718) Provide a flag to disable alter statements

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5718?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5718: ---------------------------------- Fix Version/s: 12.2 > Provide a flag to disable alter statements > ------------------------------------------ > > Key: TEIID-5718 > URL: https://issues.jboss.org/browse/TEIID-5718 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > The engine allows alter statements to ephemerally (by default) change view definitions, turn on/off triggers, etc. For Spring Boot and OpenShift deployment in particular we should consider whether this should be allowable/optional behavior. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5719) Allow unqualified temporary table names to contain .

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5719: ------------------------------------- Summary: Allow unqualified temporary table names to contain . Key: TEIID-5719 URL: https://issues.jboss.org/browse/TEIID-5719 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 If you issue something like: create local temporary table "some.table" ... The resovler will not allow the table name. That should be allowed, and instead the parser should reject unqualified names such as: create local temporary table some.table ... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5717) Timestamp fields fetch error with Cassandra

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5717?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5717. ----------------------------------- Fix Version/s: 12.2 11.2.3 12.1.1 Resolution: Done Updated the date, time, and timestamp handling. Time handling for now is mapped to timestamp to preserve the fractional seconds. > Timestamp fields fetch error with Cassandra > ------------------------------------------- > > Key: TEIID-5717 > URL: https://issues.jboss.org/browse/TEIID-5717 > Project: Teiid > Issue Type: Bug > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.1.1 > > > I am getting the below error when fetching a Cassandra table containing a column of type timestamp > ERROR TEIID_CONNECTOR_LOGGER:92 (Worker1_QueryProcessorQueue117) - - [Connector worker process failed for atomic-request=bioF/LJOq1Ih.5.0.84] - > com.datastax.driver.core.exceptions.CodecNotFoundException: Codec not found for requested operation: [timestamp <-> com.datastax.driver.core.LocalDate] > at com.datastax.driver.core.CodecRegistry.notFound(CodecRegistry.java:741) > at com.datastax.driver.core.CodecRegistry.createCodec(CodecRegistry.java:588) > at com.datastax.driver.core.CodecRegistry.access$500(CodecRegistry.java:137) > at com.datastax.driver.core.CodecRegistry$TypeCodecCacheLoader.load(CodecRegistry.java:246) > at com.datastax.driver.core.CodecRegistry$TypeCodecCacheLoader.load(CodecRegistry.java:232) > at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3529) > at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2278) > at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2156) > at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2046) > at com.google.common.cache.LocalCache.get(LocalCache.java:3948) > at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3972) > at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4957) > at com.datastax.driver.core.CodecRegistry.lookupCodec(CodecRegistry.java:522) > at com.datastax.driver.core.CodecRegistry.codecFor(CodecRegistry.java:485) > at com.datastax.driver.core.CodecRegistry.codecFor(CodecRegistry.java:467) > at com.datastax.driver.core.AbstractGettableByIndexData.codecFor(AbstractGettableByIndexData.java:69) > at com.datastax.driver.core.AbstractGettableByIndexData.getDate(AbstractGettableByIndexData.java:174) > at com.datastax.driver.core.AbstractGettableData.getDate(AbstractGettableData.java:26) > at org.teiid.translator.cassandra.CassandraQueryExecution.getRow(CassandraQueryExecution.java:161) > at org.teiid.translator.cassandra.CassandraQueryExecution.next(CassandraQueryExecution.java:100) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:428) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:231) > at sun.reflect.GeneratedMethodAccessor624.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:216) > at com.sun.proxy.$Proxy61.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:305) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:104) > at java.util.concurrent.FutureTask.run(Unknown Source) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:61) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > > The issue is solved in CassandraQueryExecution.java when replacing > case TIMESTAMP: > values.add(row.*getDate*(i)); > with > case TIMESTAMP: > values.add(row.*getTimestamp*(i)); -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019