June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3583) Need documentation on possible property settings to use

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3583?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3583. --------------------------------- > Need documentation on possible property settings to use > ------------------------------------------------------- > > Key: TEIID-3583 > URL: https://issues.jboss.org/browse/TEIID-3583 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.0 > > > In the Administration and Configuration Guide there is some indication on how to perform active heap throttling. > "Memory Management Considerations " there is a reference to parameters like: > max-processing-kb and the max-reserve-kb. > Anyway there is no indication of the indicative values to associate to those parameters to obtain a certain result. > It would be good to get some examples to understand the cause and effect of the changes ( max-reserve-kb and related settings ). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3964) Cassandra does not account for null values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3964?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3964. --------------------------------- > Cassandra does not account for null values > ------------------------------------------ > > Key: TEIID-3964 > URL: https://issues.jboss.org/browse/TEIID-3964 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.6 > Reporter: Filip Elias > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.1 > > Attachments: cassandra-vdb.xml > > > primitive wrapper types (integer, long, float, double, etc.) do not account for null values from Cassandra, but instead return their default 0 value. Teiid also throws NPE when Blob column contains null. > Query (should return [14,null]): > {code}select intkey, objectvalue from smalla where intkey = 14 {code} > Stack Trace: > {code} > 12:14:58,599 ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue7) Connector worker process failed for atomic-request=afOb+DA5w6pF.5.0.5: java.lang.NullPointerException > at org.teiid.translator.cassandra.CassandraQueryExecution.getRow(CassandraQueryExecution.java:160) [translator-cassandra-8.12.3.redhat-1.jar:8.12.3.redhat-1] > at org.teiid.translator.cassandra.CassandraQueryExecution.next(CassandraQueryExecution.java:86) [translator-cassandra-8.12.3.redhat-1.jar:8.12.3.redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:419) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:220) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45] > at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy94.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:142) > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:374) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:470) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4212) Cassandra translator: pushing Date literal as # of milliseconds is timezone dependent

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4212?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4212. --------------------------------- > Cassandra translator: pushing Date literal as # of milliseconds is timezone dependent > ------------------------------------------------------------------------------------- > > Key: TEIID-4212 > URL: https://issues.jboss.org/browse/TEIID-4212 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x > Reporter: Jan Stastny > Assignee: Steven Hawkins > > Cassandra doesn't support Date datatype. To overcome this limitation Timestamp datatype can be used on Cassandra's side in such a way that timestamp contains only date-specific literals, others are zero, in Teiid's terms: \{ts '2000-02-02 00:00:00.0'\} for 2000-02-02. > In accordance with this workaround, it should be possible to query the tables in Cassandra in such way: > {code:sql} > SELECT BQT1.SmallA.DateValue FROM BQT1.SmallA WHERE BQT1.SmallA.DateValue = {d '2000-02-02'}; > {code} > The date literal is pushed as # of milliseconds. And this is timezone dependent. > The query that gets pushed (timezone GMT+2): > {code:sql} > SELECT datevalue FROM smalla WHERE timestampvalue = 949464000000 > {code} > And value 949446000000 is equivalent to 2000-02-02 in GMT+2 timezone. > Problem emerges, when the cassandra database is running in different timezone than teiid server. Then the pushed 'date' value would not match the 'date' value in cassandra (User can't specify TZ difference). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3967) Function class not found results in an uncaught exception

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3967?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3967. --------------------------------- > Function class not found results in an uncaught exception > --------------------------------------------------------- > > Key: TEIID-3967 > URL: https://issues.jboss.org/browse/TEIID-3967 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We throw a runtime MetadataException when a UDF fails to validate when the composite vdb is being built. This exception is not caught and ends up with default handling including sys.err printout. It would be better to catch this or even better to have the function validation performed by the metadata validator - as having these exceptions happen during VDBRepository.finishDeployment is unexpected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4160) Impala - result set is not sorted if ORDER BY is defined in query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4160?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4160. --------------------------------- > Impala - result set is not sorted if ORDER BY is defined in query > ----------------------------------------------------------------- > > Key: TEIID-4160 > URL: https://issues.jboss.org/browse/TEIID-4160 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.7.6.6_2, 8.13.4 > > > Query: > {code:sql} > SELECT g_1.StringNum AS c_0 FROM Source.SmallA AS g_1 WHERE g_1.IntKey <= 50 UNION ALL SELECT g_0.StringNum AS c_0 FROM Source.SmallB AS g_0 WHERE g_0.IntKey > 50 ORDER BY c_0 > {code} > Result: as you can see, nulls are not next to each other > |StringNum| > |-24| > |<null>| > |-14| > |-13| > |-12| > |-11| > |-10| > |-9| > |-8| > |<null>| > |-6 > |-5| > |...| > Expected result: this is result of simple query SELECT stringnum FROM source.smalla ORDER BY 1 > |StringNum| > |-1| > |-10| > |-11| > |-12| > |-13| > |-14| > |-15| > |...| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4124) add literal date format YYYY-MM-DD to the SQL Server translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4124?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4124. --------------------------------- > add literal date format YYYY-MM-DD to the SQL Server translator > --------------------------------------------------------------- > > Key: TEIID-4124 > URL: https://issues.jboss.org/browse/TEIID-4124 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.7.6.6_2 > > > We are missing literal data format YYYY-MM-DD, which is 23 in our mapping for the sqlserver translator: > http://stackoverflow.com/questions/15555275/undocumented-convert-styles-d... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4138) Move teiid embedded example doc to gitbook

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4138?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4138. ----------------------------------- Fix Version/s: 9.0 (was: 9.x) Resolution: Done > Move teiid embedded example doc to gitbook > ------------------------------------------ > > Key: TEIID-4138 > URL: https://issues.jboss.org/browse/TEIID-4138 > Project: Teiid > Issue Type: Sub-task > Components: Documentation > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.0 > > > Moving the doc from https://docs.jboss.org/author/display/teiidexamples/Teiid+Embedded+Examples to gitbook -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2132) Teiid 8.0 API does not expose boundport in Mbean attribute for Teiid-JDBC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2132?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2132. --------------------------------- > Teiid 8.0 API does not expose boundport in Mbean attribute for Teiid-JDBC > ------------------------------------------------------------------------- > > Key: TEIID-2132 > URL: https://issues.jboss.org/browse/TEIID-2132 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Environment: jboss 7, teiid 8, windows 7 > Reporter: Akshay Harale > Assignee: Ramesh Reddy > Priority: Minor > Labels: jboss, teiid > > When offset is set for jboss from standalone.xml or standalone.conf.bat file, the bound port is not displyed in MBean server. > > For example, > > <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:25}"> > > In above line if I set the value as 25 then that should be added to the default socket port values and exposed as bound port value in MBean server. But in case of teiid the "teiid-jdbc" 's boundPort value is not exposed by the jboss. > > All other boundPorts values are correctly shown in Mbean, except teiid-jdbc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3988) Narrow when serial source access is used

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3988?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3988. --------------------------------- > Narrow when serial source access is used > ---------------------------------------- > > Key: TEIID-3988 > URL: https://issues.jboss.org/browse/TEIID-3988 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Both when we determine a transaction is needed and how the processing is performed under a transaction can be improved. We we likely need to reintroduce a property on the translator to tell the engine when the source is XA, local transaction, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4122) Improve performance of odbc client column metadata query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4122?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4122. --------------------------------- > Improve performance of odbc client column metadata query > -------------------------------------------------------- > > Key: TEIID-4122 > URL: https://issues.jboss.org/browse/TEIID-4122 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > With cursoring, the client issues: > select n.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull, c.relhasrules, c.relkind, c.oid, pg_get_expr(d.adbin, d.adrelid), case t.typtype when 'd' then t.typbasetype else 0 end, t.typtypmod, c.relhasoids from (((pg_catalog.pg_class c inner join pg_catalog.pg_namespace n on n.oid = c.relnamespace and c.oid = <table oid>) inner join pg_catalog.pg_attribute a on (not a.attisdropped) and a.attnum > 0 and a.attrelid = c.oid) inner join pg_catalog.pg_type t on t.oid = a.atttypid) left outer join pg_attrdef d on a.atthasdef and d.adrelid = a.attrelid and d.adnum = a.attnum order by n.nspname, c.relname, attnum > We should ensure that this is being planned optimally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016