[JBoss JIRA] (TEIID-4450) Consolidate Version class
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4450:
-------------------------------------
Summary: Consolidate Version class
Key: TEIID-4450
URL: https://issues.jboss.org/browse/TEIID-4450
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1
We have the Version class replicated in several places, so we should consolidate.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-979) Add pushdown support for sql/xml functions
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-979?page=com.atlassian.jira.plugin.... ]
Tom Arnold commented on TEIID-979:
----------------------------------
To further explain my use-case, here's a query that does N-many queries (one per ITEM). I would instead want this whole thing to get pushed down.
I'm not sure if the reason it's not getting pushed down is because XML functions are not, or if it's something to do with the aggregate/subquery?
{code:sql}
select
"ITEMS"."ITEM_ID" "ITEM_ID",
(
select xmlelement (
name "attributes",
xmlagg(
xmlelement(
name "attribute",
xmlattributes(
"ITEM_ATTRIBUTES"."ATTR_NAME" as "name",
"ITEM_ATTRIBUTES"."ATTR_VALUE" as "value"
)
)
)
)
from "ITEM_ATTRIBUTES" "ITEM_ATTRIBUTES"
where (
"ITEMS"."ITEM_ID" = "ITEM_ATTRIBUTES"."ITEM_ID"
)
) "ITEM_ATTRIBUTES"
from "ITEMS" "ITEMS";
{code}
{code}
ITEM_ID ITEM_ATTRIBUTES
3 <attributes><attribute name="foo" value="bar"></attribute><attribute name="baz" value="blah"></attribute></attributes>
4 <attributes><attribute name="foo" value="123"></attribute><attribute name="baz" value="456"></attribute></attributes>
{code}
> Add pushdown support for sql/xml functions
> ------------------------------------------
>
> Key: TEIID-979
> URL: https://issues.jboss.org/browse/TEIID-979
> Project: Teiid
> Issue Type: Sub-task
> Components: JDBC Connector
> Affects Versions: 7.1
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
>
> We should have pushdown support for SQL/XML functionality. In particular Oracle and DB2 have support.
> see also case 5715
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-979) Add pushdown support for sql/xml functions
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-979?page=com.atlassian.jira.plugin.... ]
Tom Arnold commented on TEIID-979:
----------------------------------
Is there any reason this never got finished?
We have a macro that generates XMLAGG/XMLELEMENT/etc and uses it to pull back data in a structured format. This works great on Oracle/Postgres but on Teiid it does N-many queries.
> Add pushdown support for sql/xml functions
> ------------------------------------------
>
> Key: TEIID-979
> URL: https://issues.jboss.org/browse/TEIID-979
> Project: Teiid
> Issue Type: Sub-task
> Components: JDBC Connector
> Affects Versions: 7.1
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
>
> We should have pushdown support for SQL/XML functionality. In particular Oracle and DB2 have support.
> see also case 5715
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4447) database service logging for auditlog gives NPE when running a query
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4447?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4447:
---------------------------------------
The change here can be fairly straight-forward, just to map to the current set of fields using the LogonInfo instead of the CommandContext. Or we can add the additional fields from the LogonInfo to account for logon / off events - but that requires database changes as well.
[~rareddy] [~van.halbert] Any votes on what we should do?
> database service logging for auditlog gives NPE when running a query
> --------------------------------------------------------------------
>
> Key: TEIID-4447
> URL: https://issues.jboss.org/browse/TEIID-4447
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.5
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> When using the database logger (database-service.jar) running a query gives an NPE on the auditlog[1], the tables are in the database and the commandlog table is written to just not the auditlog table.
> [1]
> 12:18:57,297 ERROR [org.jboss.as.ejb3.invocation] (pool-2-thread-1) JBAS014134: EJB Invocation failed on component teiid-database-service for method public abstract void org.teiid.service.DatabaseServiceLocal.log(org.teiid.logging.AuditMessage): javax.ejb.EJBException: java.lang.NullPointerException
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:280) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:330) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:242) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:89) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:189)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
> at org.teiid.service.DatabaseServiceLocal$$$view1.log(Unknown Source) [database-service.jar:]
> at org.teiid.logger.DatabaseAppender.publish(DatabaseAppender.java:51) [database-logging-appender-1.2.0.redhat-10.jar:1.2.0.redhat-10]
> at org.jboss.logmanager.handlers.AsyncHandler$AsyncTask.run(AsyncHandler.java:196) [jboss-logmanager-1.5.4.Final-redhat-1.jar:1.5.4.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> Caused by: java.lang.NullPointerException
> at org.teiid.service.AuditEnitity.<init>(AuditEnitity.java:55) [database-service.jar:]
> at org.teiid.service.DatabaseServiceBean.log(DatabaseServiceBean.java:44) [database-service.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:374)
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:86) [jboss-as-weld-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:97) [jboss-as-weld-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:49) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:93) [jboss-as-weld-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:278) [jboss-as-ejb3-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> ... 31 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4449) Allow limited replanning of subplans that use only common tables
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4449:
-------------------------------------
Summary: Allow limited replanning of subplans that use only common tables
Key: TEIID-4449
URL: https://issues.jboss.org/browse/TEIID-4449
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1
If a common table is fully pushed and not marked as materialized, then it could be used in subplans in a trivial way:
with x as ... select col from x
It would be better to have that access reference a materialized common table, rather than pushed separately.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-3877) Sort result set before BQT comparison
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3877?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-3877.
--------------------------------
Resolution: Won't Fix
> Sort result set before BQT comparison
> -------------------------------------
>
> Key: TEIID-3877
> URL: https://issues.jboss.org/browse/TEIID-3877
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Environment: BQT 2.2.0
> JBoss DV 6.2
> Reporter: Jean-Pierre Matsumoto
> Assignee: Van Halbert
> Priority: Minor
>
> Currently it is not possible to ask to BQT to sort result set before it compares to reference. When an SQL query returns rows in a random order, the BQT test fails because of the different order of rows.
> I know I could use ORDER BY in the SQL but I don't like much this solution because it impacts the query plan.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4351) JDG: Does not support 1-to-1 relationship
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4351?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4351:
-------------------------------
Fix Version/s: 9.1
Git Pull Request: https://github.com/teiid/teiid/pull/798
Affects Version/s: 8.12.x
> JDG: Does not support 1-to-1 relationship
> -----------------------------------------
>
> Key: TEIID-4351
> URL: https://issues.jboss.org/browse/TEIID-4351
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.x, 8.7.6
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 9.1
>
>
> When the primary object has a defined 1-to-1 relationship, the internal relationship isn't generating a second table by the metadata processor, even though its defined in the protobuf definition file and the marshallers. And when the second table is manually built, and then tried to preview, the server is throwing a methodNotFound exception, because its looking back on the primary object for the method, not the internal object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4351) JDG: Does not support 1-to-1 relationship
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4351?page=com.atlassian.jira.plugin... ]
Work on TEIID-4351 stopped by Van Halbert.
------------------------------------------
> JDG: Does not support 1-to-1 relationship
> -----------------------------------------
>
> Key: TEIID-4351
> URL: https://issues.jboss.org/browse/TEIID-4351
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.6
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> When the primary object has a defined 1-to-1 relationship, the internal relationship isn't generating a second table by the metadata processor, even though its defined in the protobuf definition file and the marshallers. And when the second table is manually built, and then tried to preview, the server is throwing a methodNotFound exception, because its looking back on the primary object for the method, not the internal object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4448) Multi-way join predicate inappropriately removed
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4448?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4448.
-----------------------------------
Resolution: Done
Updated the logic to only set as optional in case where the reduction was down to a simple predicate.
> Multi-way join predicate inappropriately removed
> ------------------------------------------------
>
> Key: TEIID-4448
> URL: https://issues.jboss.org/browse/TEIID-4448
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 9.1, 8.13.7, 9.0.5
>
>
> In a situation where copy criteria can work against a multi-way join predicate, such that the predicate is not pushed:
> t1.a = coalesce(t2.b, t3.c, t4.d) ... t1.a = t4.d
> The multi-way predicate can be marked as optional and removed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months