[JBoss JIRA] (TEIID-2112) consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2112?page=com.atlassian.jira.plugin... ]
Steven Hawkins reopened TEIID-2112:
-----------------------------------
> consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2112
> URL: https://issues.jboss.org/browse/TEIID-2112
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.1
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 7.4.4, 8.1, 8.2
>
>
> The server is taking the incoming ts string and converting it to a Z value via the server timezone (handled by STax). When the response document is delivered Saxon converts a non-timezoned value into an assumed Z value - which is not consistent with the STax handling. This is within the bounds of XML processing as the absence of timezone information leaves the timezone interpretation up to the implementation - "timezone of some unspecified locality as prescribed by the appropriate legal authority".
> However, these two paths should be consistent,so a patch would set the local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (TEIID-2309) Add support for "conformed" tables in Teiid
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2309?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2309.
-----------------------------------
Resolution: Done
Added and documented an initial conformed table feature with similar planning characteristics to the multi-source feature. If more advanced scenarios arise (needing source specific metadata, or capabilities conflicts) then we'll want to enhance this logic.
> Add support for "conformed" tables in Teiid
> -------------------------------------------
>
> Key: TEIID-2309
> URL: https://issues.jboss.org/browse/TEIID-2309
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> Teiid would support tables from different data sources being marked as "conformed", meaning they are the same (or perhaps a different name). When optimising a query, it would take the conformity into account and choose the appropriate copy of the table (presumably one in the same database as other tables in the query, if available). I would not regard it as a problem if Teiid *required* the dimensions to be strictly the same as opposed to permitting subsets, though as with so many areas, it would be up to the user to ensure this was really true: I would not expect the engine to do anything to verify that the tables really were conformed.
> Usecase:
> In Data Warehousing, it is relatively common to have multiple copies of the same dimensions spread over multiple Data Warehouses or Marts, or in the same Data Warehouse when associated with different Fact Tables. If these copies are either identical or strict subsets of an idealised dimension (and, by extension, share *exactly* the same naming and structure), then they may be said to be "conformed". It is expected that the dimension includes at least the values required to support the facts in the database in which it occurs or the Fact Table to which it is paired.
> Example:
>
> Source S1:
>
> BIGBIGBIG (millions of rows)
> bigkey
> ccy
> other_stuff
>
> CURRENCY (100s of rows) let's call it S1_CCY if we need to distinguish
> ccy
> ccy_name
>
>
> Source S2:
>
> BIGGER (millions of rows)
> biggerkey
> bigkey
> ccy
> more_stuff
>
> CURRENCY (100s of rows) similarly, S2_CCY
> ccy
> ccy_name
>
>
> When executing:
>
> SELECT B.*
> FROM BIGBIGBIG B,
> CURRENCY CCY
> WHERE B.ccy = CCY.ccy
> AND CCY.ccy_name LIKE "%DOLLAR%"
>
> Then it is clearly advantageous to use the copy of CURRENCY in S1 and re-write the query using S1_CCY. In this situation, federation is eliminated completely.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (TEIID-2736) MongoDB: failed to translate to mongo query with boolean value expression
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2736?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2736.
---------------------------------
Labels: Beta2 teiid (was: teiid)
Resolution: Done
Added support for "$cond" operator in the "$projection" pipeline statement, to handle expressions in the select statement. One issue I saw is MongoDB's $cond syntax was little different compared to $match for comparison operators. Now code will handle both.
> MongoDB: failed to translate to mongo query with boolean value expression
> --------------------------------------------------------------------------
>
> Key: TEIID-2736
> URL: https://issues.jboss.org/browse/TEIID-2736
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Teiid 8.6 beta with mongoDB
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid, Beta2
> Fix For: 8.6
>
>
> Fail to translate the following SQL to mongo query:
> select "grade",
> "name",
> "score",
> "state",
> "grade" as "test",
> ("name" = "state") as "name2"
> from "mongoDBDS"."grades"
> where "grade" = 'B'
> However, it works with the query contains group by and boolean value expression:
> elect "grade" as "test",
> "grade",
> ("name" = "state") as "name2",
> sum("score") as "sum_score"
> from "mongoDBDS"."grades"
> where "grade" = 'B'
> group by "grade", "grade", ("name" = "state")
> order by "grade", "test", "name2"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (TEIID-586) Like pushdown handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-586?page=com.atlassian.jira.plugin.... ]
Steven Hawkins resolved TEIID-586.
----------------------------------
Resolution: Partially Completed
Added a KI for salesforce like case insensitive behavior. Can revisit this if a situation where single character ldap like searching or salesforce case insensitive searching is an issue.
> Like pushdown handling
> ----------------------
>
> Key: TEIID-586
> URL: https://issues.jboss.org/browse/TEIID-586
> Project: Teiid
> Issue Type: Bug
> Components: LDAP Connector, Query Engine, Salesforce Connector
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.6
>
>
> Both salesforce and ldap like semantics are not the same as SQL. We could capture this with more capabilities supportsLikeCaseSensitive and supportsLikeWildcardSingleCharacter repectively, or another approach would be to allow the connector to generically indicate partial support and have the query engine both push down the conjunct and leave a copy to be applied after the query. With either explicit supports or generic partial support it would only applicable to top level where clause conjuncts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (TEIID-586) Like pushdown handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-586?page=com.atlassian.jira.plugin.... ]
Steven Hawkins commented on TEIID-586:
--------------------------------------
Corrected ldap like handling:
- throw an exception if the single match pattern character is pushed down (we can revisit later if we need to compensate)
- added handling for like escape so that % and _ can be matched as characters
> Like pushdown handling
> ----------------------
>
> Key: TEIID-586
> URL: https://issues.jboss.org/browse/TEIID-586
> Project: Teiid
> Issue Type: Bug
> Components: LDAP Connector, Query Engine, Salesforce Connector
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.6
>
>
> Both salesforce and ldap like semantics are not the same as SQL. We could capture this with more capabilities supportsLikeCaseSensitive and supportsLikeWildcardSingleCharacter repectively, or another approach would be to allow the connector to generically indicate partial support and have the query engine both push down the conjunct and leave a copy to be applied after the query. With either explicit supports or generic partial support it would only applicable to top level where clause conjuncts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (TEIID-2742) transaction rollback in EDS with SQLServer
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2742?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2742:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Priority: Minor (was: Major)
Given the case comments and resolution lessening to a minor quality risk. With the complexity of the plan (while the error only shows accessing a single table) we can infer that cursored access is being opened against quite a few tables and in particular causing a deadlock between processes.
If other workarounds like adjusting the isolation level as suggested in the case (and http://technet.microsoft.com/en-us/library/ms187373.aspx) do not work and this comes up as an issue then we'll need to look at it further.
> transaction rollback in EDS with SQLServer
> ------------------------------------------
>
> Key: TEIID-2742
> URL: https://issues.jboss.org/browse/TEIID-2742
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Connector
> Affects Versions: 7.7.8
> Environment: EDS 5.3.1
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
> Priority: Minor
>
> When using LoadTest within SoapUI, upon increase the number of threads to greater than 1, we encounter the ATOMIC transaction encountering roll back and the following error is found. However, when the threads only set to 1, everything works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (TEIID-2575) Hive's Binary Type Handling by Teiid
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2575?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2575:
------------------------------------------------
Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 984852|https://bugzilla.redhat.com/show_bug.cgi?id=984852] from ON_QA to VERIFIED
> Hive's Binary Type Handling by Teiid
> ------------------------------------
>
> Key: TEIID-2575
> URL: https://issues.jboss.org/browse/TEIID-2575
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.4.1
> Reporter: Filip Nguyen
> Assignee: Ramesh Reddy
> Fix For: 8.4.1, 8.5
>
>
> I have simple Hive table (column definition: "OBJECTVALUE BINARY" see [1]). When running a simple query "statement.executeQuery("select OBJECTVALUE from smalla;");" I am getting [2]. When I run it simply from Hive console it works ok.
> [1]
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Types
> [2]
> {noformat}
> org.teiid.jdbc.TeiidSQLException: TEIID10076 Invalid conversion from type class org.teiid.core.types.BinaryType with value 'EFBFBDEFBFBDEFBFBD' to type class java.lang.String
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:516)
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:130)
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:37)
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75)
> at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:235)
> at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:271)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:102)
> at $Proxy6.read(Unknown Source)
> at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:370)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:525)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> at org.jboss.qe.HiveTranslatorTest.simpleQueryTest(HiveTranslatorTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46)
> at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.teiid.core.types.TransformationException: TEIID10076 Invalid conversion from type class org.teiid.core.types.BinaryType with value 'EFBFBDEFBFBDEFBFBD' to type class java.lang.String
> at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:891)
> at org.teiid.dqp.internal.process.DataTierTupleSource.correctTypes(DataTierTupleSource.java:186)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:326)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:306)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:149)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:149)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:112)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (TEIID-2649) NoClassDefFoundError when trying to run adminshell
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2649?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2649:
------------------------------------------------
Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 1004770|https://bugzilla.redhat.com/show_bug.cgi?id=1004770] from ON_QA to VERIFIED
> NoClassDefFoundError when trying to run adminshell
> --------------------------------------------------
>
> Key: TEIID-2649
> URL: https://issues.jboss.org/browse/TEIID-2649
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
>
> adminshell is throwing the following exception when trying to be run:
> Exception in thread "main" java.lang.NoClassDefFoundError: jline/History
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> at java.lang.Class.getDeclaredMethods(Class.java:1845)
> at org.codehaus.groovy.reflection.CachedClass$3$1.run(CachedClass.java:83)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:80)
> at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:78)
> at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46)
> at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33)
> at org.codehaus.groovy.reflection.CachedClass.getMethods(CachedClass.java:249)
> at groovy.lang.MetaClassImpl.populateMethods(MetaClassImpl.java:341)
> at groovy.lang.MetaClassImpl.fillMethodIndeMetaClassImpl.java:291)
> at groovy.lang.MetaClassImpl.initialize(MetaClassImpl.java:2912)
> at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:166)
> at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:182)
> at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getMetaClass(MetaClassRegistryImpl.java:210)
> at org.codehaus.groovy.runtime.InvokerHelper.getMetaClass(InvokerHelper.java:701)
> at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallConstructorSite(CallSiteArray.java:69)
> at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:52)
> at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:192)
> at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:200)
> at org.codehaus.groovy.tools.shell.Main.main(Main.groovy:124)
> at org.teiid.adminshell.GroovyAdminShell.main(GroovyAdminShell.java:30)
> Caused by: java.lang.ClassNotFoundException: jline.History
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 23 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months