[JBoss JIRA] (TEIID-2292) Add "SOURCE_NAME" column automatically for Multi-Source models
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2292?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2292.
---------------------------------
> Add "SOURCE_NAME" column automatically for Multi-Source models
> --------------------------------------------------------------
>
> Key: TEIID-2292
> URL: https://issues.jboss.org/browse/TEIID-2292
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> Currently Teiid adds SOURCE_NAME pseudo column when the model defines as multi-source to all the tables. This is not reflected in the metadata. However based on the community requests it looks like providing a way to automatically adding this to the tables and procedures is useful in dynamic vdb scenarios.
> This can be added when a property like
> <property name="multi-source-column" value="{name-of-column}"/>
--
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
11 years, 10 months
[JBoss JIRA] (TEIID-2219) NullPointer Exception when doing count aggregations on two individual columns from separate databases
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2219?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2219.
---------------------------------
> NullPointer Exception when doing count aggregations on two individual columns from separate databases
> -----------------------------------------------------------------------------------------------------
>
> Key: TEIID-2219
> URL: https://issues.jboss.org/browse/TEIID-2219
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Environment: Running embedded mode
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Fix For: 8.2
>
> Attachments: EmbeddedServer.java.patch, Schema Dump.txt, SQL and Exception.txt
>
>
> I have issues doing Count aggregations in 2 different databases. 2 out of 3 following cases fail... (But distinct count seems ok)
>
> <----------- CASE 1 ----------> SUM first, then COUNT => OK
>
> SUM(DB_2.field_1), COUNT(DB_1.field_1)
>
> select sum("FoodmartDataSourceJNDI_public_expense_fact"."amount") as "FoodmartDataSourceJNDI_public_expense_fact_amount_Sum",
> count("FoodmartDataSource_public_employee"."full_name") as "FoodmartDataSource_public_employee_full_name_Count"
> from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee"
> inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id")
>
>
> SELECT g_0."store_id" AS c_0, g_0."full_name" AS c_1 FROM "public"."employee" AS g_0 ORDER BY c_0
>
>
> SELECT g_0."store_id" AS c_0, SUM(g_0."amount") AS c_1 FROM "public"."expense_fact" AS g_0 GROUP BY g_0."store_id" ORDER BY c_0
>
> <-----------CASE 2 ---------------> COUNT first, then SUM => ERROR
>
> COUNT(DB_1.field_1), SUM(DB_2.field_1)
>
>
> select count("FoodmartDataSourceJNDI_public_expense_fact"."category_id") as "FoodmartDataSourceJNDI_public_expense_fact_category_id_Count",
> sum("FoodmartDataSource_public_employee"."salary") as "FoodmartDataSource_public_employee_salary_Sum"
> from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee"
> inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id")
>
> Caused by: java.lang.NullPointerException
> at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:184)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:108)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:113)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:103)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:194)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:130)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:109)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
> ... 123 more
>
> <-----------CASE 3 ---------------> COUNT on DB1.COL1 and COUNT on DB2.COL2 => ERROR
>
> COUNT(DB_1.field_1), COUNT(DB_2.field_1)
>
> select count("FoodmartDataSourceJNDI_public_expense_fact"."category_id") as "FoodmartDataSourceJNDI_public_expense_fact_category_id_Count",
> count("FoodmartDataSource_public_employee"."first_name") as "FoodmartDataSource_public_employee_first_name_Count"
> from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee"
> inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id")
>
> Caused by: java.lang.NullPointerException
> at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:184)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:108)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:113)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:103)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:194)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:130)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:109)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
> ... 123 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
11 years, 10 months
[JBoss JIRA] (TEIID-2069) Optimze add LIMIT clause to SELECT within a Virtual Procedure using Oracle
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2069?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2069.
---------------------------------
> Optimze add LIMIT clause to SELECT within a Virtual Procedure using Oracle
> --------------------------------------------------------------------------
>
> Key: TEIID-2069
> URL: https://issues.jboss.org/browse/TEIID-2069
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.4.1, 7.7
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 8.1, 7.7.2
>
>
> LIMIT clause is added to Statement being optimized which fails the operation on Oracle
> OPTIMIZE:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> DECLARE biginteger VARIABLES.t_pk;
> VARIABLES.t_pk = (SELECT <table>.seq_gen.cpe_seq FROM <table>.seq_gen);
> SELECT VARIABLES.t_pk AS result;
> END
> ####################################################
> PROCEDURE COMMAND: CREATE VIRTUAL PROCEDURE
> BEGIN
> DECLARE biginteger VARIABLES.t_pk;
> VARIABLES.t_pk = (SELECT <table>.seq_gen.cpe_seq FROM <table>.seq_gen LIMIT 2);
> SELECT VARIABLES.t_pk AS result;
> END
>
--
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
11 years, 10 months
[JBoss JIRA] (TEIID-2218) Exception Executing WS Query via View
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2218?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2218.
---------------------------------
> Exception Executing WS Query via View
> -------------------------------------
>
> Key: TEIID-2218
> URL: https://issues.jboss.org/browse/TEIID-2218
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Ted Jones
> Assignee: Steven Hawkins
> Fix For: 8.2
>
> Attachments: Info to reproduce.txt
>
>
> Using Teiid 8.2 Alpha1 on Openshift, I encounter the following exception querying a view with a web service as a source:
>
> 2012/09/17 11:41:09,541 ERROR [org.teiid.PROCESSOR] (http-127.8.133.129/127.8.133.129:8080-2) TEIID30019 Unexpected exception for request mRknOBSXBt1k.10: org.teiid.core.TeiidRuntimeException: Alread closed
> at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:233)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05-icedtea]
> Caused by: java.lang.IllegalStateException: Alread closed
> at org.teiid.common.buffer.FileStore$FileStoreOutputStream.checkOpen(FileStore.java:129)
> at org.teiid.common.buffer.FileStore$FileStoreOutputStream.flushBuffer(FileStore.java:84)
> at org.teiid.common.buffer.FileStore$FileStoreOutputStream.flush(FileStore.java:111)
> at org.teiid.common.buffer.FileStore$FileStoreOutputStream.close(FileStore.java:117)
> at org.teiid.dqp.internal.process.SaveOnReadInputStream.close(SaveOnReadInputStream.java:132)
> at java.io.FilterInputStream.close(FilterInputStream.java:181) [rt.jar:1.7.0_05-icedtea]
> at org.teiid.translator.WSConnection$Util.closeSource(WSConnection.java:64) [teiid-api-8.2.0.Alpha1-SNAPSHOT.jar:8.2.0.Alpha1-SNAPSHOT]
> at org.teiid.query.xquery.saxon.SaxonXQueryExpression$Result.close(SaxonXQueryExpression.java:119)
> at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:166)
> at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:225)
> ... 6 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
11 years, 10 months
[JBoss JIRA] (TEIID-2013) Teiid with GSSAPI/kerberos authentication, remove need for jdbc clients to specify -Djava.security.krb5.realm and -Djava.security.krb5.kdc
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2013?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2013.
---------------------------------
> Teiid with GSSAPI/kerberos authentication, remove need for jdbc clients to specify -Djava.security.krb5.realm and -Djava.security.krb5.kdc
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2013
> URL: https://issues.jboss.org/browse/TEIID-2013
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver
> Affects Versions: 7.6
> Environment: Teiid 7.6 and above
> Reporter: Graeme Gillies
> Assignee: Ramesh Reddy
> Fix For: 8.1
>
>
> Currently any clients connecting to teiid with GSSAPI authentication need to specify the following JVM properties
> -Djava.security.krb5.realm
> -Djava.security.krb5.kdc
> Not specifying them causes errors saying to specify these properties. Other Java GSSAPI/kerberos projects (for example, jboss negotiation, [1]) don't need these properties to be set, instead seem to pull the values from /etc/krb5.conf (normal system kerberos configuration file) as needed. This is extremely ideal, as it allows sysadmins to change kerberos configuration for an entire system easily at once (for example, to use a new kdc) without having to then also manually reconfigure java clients.
> I've done some digging and it looks like a property exists called java.security.krb5.conf [2] which can take a String pointing to a krb5.conf file, in order to get the information needed for for kerberos auth. Is it possible to modify teiid jdbc driver so that if the realm/kdc properties aren't set, then it will automatically look for the system default krb5.conf (/etc/krb5.conf in linux, not sure what it is in windows) and set java.security.krb5.conf (unless it's already set to the OS default?) to that value and then get the client to work with that?
> [1] https://community.jboss.org/wiki/JBossNegotiation
> [2] http://stackoverflow.com/questions/1431999/java-and-kerberos-authenticati...
> This would greatly streamline the configuration needed for teiid JDBC clients with GSSAPI.
> Thanks in advance,
> Graeme
--
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
11 years, 10 months
[JBoss JIRA] (TEIID-2423) add xml deployment for Teiid Embedded
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2423?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2423.
-----------------------------------
Resolution: Done
Added deployVDB(InputStream) for xml deployment with option 2 - that is any override translators are not allowed.
Also added addConnectionFactory to simply add a connection factory without the need to wrap it with a ConnectionFactoryProvider.
> add xml deployment for Teiid Embedded
> -------------------------------------
>
> Key: TEIID-2423
> URL: https://issues.jboss.org/browse/TEIID-2423
> Project: Teiid
> Issue Type: Enhancement
> Components: Embedded
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> We can accept a Reader for the VDBMetadataParser to turn into a VDBMetadata object for deployment (there is already a protected deplyVDB that takes VDBMetadata). There are some additional considerations here, such as allowing for vdb specific connector repositories and the setting of classloaders and other logic typically handled by a server deployment.
--
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
11 years, 10 months
[JBoss JIRA] (TEIID-2423) add xml deployment for Teiid Embedded
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2423?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2423:
---------------------------------------
As for translators the options are:
1. ignore the declarations in the xml
2. throw an exception if they are declared in the xml
3. add the notion of a class based translator repository so that we can instantiate and configure new instances from there. However even then the translator type inheritance system doesn't work very well as any intermediate types that are defined via just configuration (not from just a class) can not be referenced.
I would lean toward 2 at this point just for simplicity.
> add xml deployment for Teiid Embedded
> -------------------------------------
>
> Key: TEIID-2423
> URL: https://issues.jboss.org/browse/TEIID-2423
> Project: Teiid
> Issue Type: Enhancement
> Components: Embedded
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> We can accept a Reader for the VDBMetadataParser to turn into a VDBMetadata object for deployment (there is already a protected deplyVDB that takes VDBMetadata). There are some additional considerations here, such as allowing for vdb specific connector repositories and the setting of classloaders and other logic typically handled by a server deployment.
--
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
11 years, 10 months