April 2019 - teiid-issues - Jboss List Archives

[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 updated TEIID-5717: ---------------------------------- Component/s: Misc. Connectors > Timestamp fields fetch error with Cassandra > ------------------------------------------- > > Key: TEIID-5717 > URL: https://issues.jboss.org/browse/TEIID-5717 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > 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

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-28. --------------------------------- Resolution: Done Added the flag and defaulted to "false". > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-28: --------------------------------------- Should be good now. > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-61) Not able to delete/create entity in

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-61?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDSB-61. ----------------------------------- Fix Version/s: 1.1.0 Resolution: Done Updated the transaction logic to accommodate a teiid programatic management of a spring transaction. Another approach would be to refactor the LocalClient such that the SpringClient could use the Transactional annotation to make the transaction spring managed. Right now we have separate calls for start/commit/rollback, so we're in charge of associating the transaction with the thread. Also this does not address transaction handling with remote jdbc/pg. > Not able to delete/create entity in > ------------------------------------ > > Key: TEIIDSB-61 > URL: https://issues.jboss.org/browse/TEIIDSB-61 > Project: Teiid Spring Boot > Issue Type: Bug > Reporter: Jan Safarik > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > Trying to use the teiid-spring-boot/samples/odata project, I am not able to Create, Update or Delete an entity. Tried on Customer, with Delete I get back code: TEIID30504 with message: "TEIID30504 accounts: 23503 TEIID11013:TEIID11004 Error executing statement(s): [SQL: DELETE FROM "CUSTOMER" WHERE "CUSTOMER"."SSN" = 'CST01002']". With Create (Post) I get code: TEIID30528 with message: "TEIID30528 javax.transaction.SystemException". -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-28: --------------------------------------- I see a similar issue with the RuntimeMetadata at the translator layer. I'll address that as well. > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-28: --------------------------------------- It's an issue with the MetadataValidator - it's passing the default metadata object, when we are expecting the design time metadata. > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-28: --------------------------------------- [~rareddy] yes they can. There's a resolver test of that. I'll add a higher level test and see if can reproduce what you are seeing. > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-28: ------------------------------------- [~shawkins] When this property is flipped to "false", can hidden schema-based tables be accessed in the View layer? I am seeing an error where my VDB is erroring during deployment because the view can not use the hidden schema's tables in its transformation. > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-47) Determine behavior of alter statements

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-47?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIIDSB-47: ------------------------------------- Fix Version/s: 1.1.0 Assignee: Ramesh Reddy (was: Steven Hawkins) See TEIID-5718 for when/why org.teiid.allowAlter should be used. We can incorporate that if needed into our examples/UI. > Determine behavior of alter statements > -------------------------------------- > > Key: TEIIDSB-47 > URL: https://issues.jboss.org/browse/TEIIDSB-47 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > 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] (TEIIDSB-47) Determine behavior of alter statements

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-47?page=com.atlassian.jira.plugin... ] Work on TEIIDSB-47 stopped by Steven Hawkins. --------------------------------------------- > Determine behavior of alter statements > -------------------------------------- > > Key: TEIIDSB-47 > URL: https://issues.jboss.org/browse/TEIIDSB-47 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019