March 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2794) ambiguous function calls are not properly handled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2794?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2794: ------------------------------------------------ Julian Coleman <jcoleman(a)redhat.com> changed the Status of [bug 1050001|https://bugzilla.redhat.com/show_bug.cgi?id=1050001] from MODIFIED to ON_QA > ambiguous function calls are not properly handled > ------------------------------------------------- > > Key: TEIID-2794 > URL: https://issues.jboss.org/browse/TEIID-2794 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7 > > > For user defined or possibly translator functions that are given the same name the first exact match to the function name and types will be used as the function rather than reporting an ambiguous match. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2814) HIVE: quote is removed for TIMESTAMP field in where clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2814?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2814: ------------------------------------------------ Julian Coleman <jcoleman(a)redhat.com> changed the Status of [bug 1058084|https://bugzilla.redhat.com/show_bug.cgi?id=1058084] from MODIFIED to ON_QA > HIVE: quote is removed for TIMESTAMP field in where clause > ----------------------------------------------------------- > > Key: TEIID-2814 > URL: https://issues.jboss.org/browse/TEIID-2814 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: HIVE and Teiid 8.6 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > Fix For: 8.4.2, 8.7 > > > I am running teiid 8.6 against HIVE. And I found out that quote was removed for TIMESTAMP field in where clause. And it caused java.sql.SQLException: Error while processing statement: FAILED: ParseException line 1:88 missing EOF > Original SQL: > select "the_date", > "store_sales" > from "hive2"."sales_seq" > where ("the_date" > '1970-05-16 00:10:04') > Teiid generated SQL: > SELECT g_0.the_date, g_0.store_sales FROM sales_seq g_0 WHERE g_0.the_date > 1970-05-16 00:10:04.0 > Exception: > Caused by: java.sql.SQLException: Error while processing statement: FAILED: > ParseException line 1:88 missing EOF at '00' near '16' -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2804) Aggregate empty filter too broad and may inappropriately filter results

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2804?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2804: ------------------------------------------------ Julian Coleman <jcoleman(a)redhat.com> changed the Status of [bug 1053786|https://bugzilla.redhat.com/show_bug.cgi?id=1053786] from MODIFIED to ON_QA > Aggregate empty filter too broad and may inappropriately filter results > ----------------------------------------------------------------------- > > Key: TEIID-2804 > URL: https://issues.jboss.org/browse/TEIID-2804 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.2, 8.7 > > > This is a regression from TEIID-2253 which consolidated logic in RulePushAggregates to handle multi-source planning. It also inappropriately expanded an empty test (which should only be applied to grouping without a group by) to some cases with group by clauses and in an attempt to broaden pushdown support utilized is not null tests. However the is not null tests are not generally valid as the aggregate could be computed against all null values for example. Depending upon this situations this could result in invalid filtering of results. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2796) An importing vdb does not properly handle imported multi-source

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2796?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2796: ------------------------------------------------ Julian Coleman <jcoleman(a)redhat.com> changed the Status of [bug 1050335|https://bugzilla.redhat.com/show_bug.cgi?id=1050335] from MODIFIED to ON_QA > An importing vdb does not properly handle imported multi-source > --------------------------------------------------------------- > > Key: TEIID-2796 > URL: https://issues.jboss.org/browse/TEIID-2796 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.2, 8.7 > > > When importing a vdb the imported multi-source models are not properly treated as multi-source. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2833) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2833?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2833: ------------------------------------------------ Julian Coleman <jcoleman(a)redhat.com> changed the Status of [bug 1060335|https://bugzilla.redhat.com/show_bug.cgi?id=1060335] from MODIFIED to ON_QA > While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary > --------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2833 > URL: https://issues.jboss.org/browse/TEIID-2833 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Reporter: Barry LaFond > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7 > > Attachments: TEIID_2829_project.zip > > > 1) Open attached project in Designer > 2) Deploy the BQT2.vdb > 3) Create another project > 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model) > 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null" > {code} > java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142) > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128) > at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477) > at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94) > at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450) > at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321) > {code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2897) texttable performance enhancements

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2897: ------------------------------------- Summary: texttable performance enhancements Key: TEIID-2897 URL: https://issues.jboss.org/browse/TEIID-2897 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7 texttable processing should be enhanced to be multi-threaded and should be able to determine if a limit is in effect. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2887) MongoDB: mongodb DBCollection aggregate error

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2887?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2887. --------------------------------- Labels: Beta3 teiid (was: teiid) Resolution: Done The issue was MongoDB does not like names with "." in the top level projections, which is done using $group phase. Since the names were derived from tables columns, in this case the name was from child table so name pattern is "name.childname" thus failing. Corrected the code such that it always builds an alias for all the column references. This also need to be pulled into 8.4.1 roll-up > MongoDB: mongodb DBCollection aggregate error > ---------------------------------------------- > > Key: TEIID-2887 > URL: https://issues.jboss.org/browse/TEIID-2887 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: Teiid 8.7 Beta1 with MongoDB > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: teiid, Beta3 > Fix For: 8.7 > > > Here is my simple JSON object: > "addresst" { "_id": 0, > "name": "Duke Grant", > "age": 38, > "gender": "male", > > "address": { "_id": 0, > "street": "345 Burnett Street", > "city": "Nash", > "state": "Rhode Island", > "zip": 7384 } > } > And I define a schema like following: > REATE FOREIGN TABLE addresst (custid integer PRIMARY KEY, name varchar(25), age integer, gender varchar(25)) OPTIONS(UPDATABLE 'TRUE'); > CREATE FOREIGN TABLE address (custid integer PRIMARY KEY, street varchar(50), city varchar(25), state varchar(25), zipcode varchar(6), FOREIGN KEY (custId) REFERENCES addresst (custid)) OPTIONS(UPDATABLE 'TRUE' , "teiid_mongo:MERGE" 'addresst'); > Got exception when trying to execute a query like following: > select "MongoDB_addresst"."gender" as "MongoDB_addresst_gender", > "MongoDB_address"."state" as "MongoDB_address_state" > from "MongoDB"."addresst" "MongoDB_addresst" > inner join "MongoDB"."address" "MongoDB_address" on ("MongoDB_addresst"."custid" = "MongoDB_address"."custid") > group by "MongoDB_addresst"."gender", "MongoDB_address"."state" > order by "MongoDB_addresst_gender", "MongoDB_address_state" > limit 1000 > Exception: > Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "qa-mongodb.jaspersoft.com/172.17.1.48:27017" , "errmsg" : "exception: dotted field names are only allowed at the top level" , "code" : > 16405 , "ok" : 0.0} > at com.mongodb.CommandResult.getException(CommandResult.java:71) > at com.mongodb.CommandResult.throwOnError(CommandResult.java:110) > at com.mongodb.DBCollection.aggregate(DBCollection.java:1308) > at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:99) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:317) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:273) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) > ... 3 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2896) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2896: ---------------------------------- Fix Version/s: 8.7 > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2896 > URL: https://issues.jboss.org/browse/TEIID-2896 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.7 > > > Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2896) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin... ] Steven Hawkins moved TEIIDDES-2076 to TEIID-2896: ------------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-2896 (was: TEIIDDES-2076) Affects Version/s: (was: 7.8) Component/s: Query Engine (was: Import/Export) > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2896 > URL: https://issues.jboss.org/browse/TEIID-2896 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Van Halbert > Assignee: Barry LaFond > > Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2880) Add login username to source query comment, also session and request Id

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2880?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2880: --------------------------------------- One possibility is to use stringtemplate https://theantlrguy.atlassian.net/wiki/display/ST4/StringTemplate+4+Wiki+... It's a bit of overkill, but it's perfectly capable of producing the expected output using bean properties. Another possibility is to evaluate in Javascript, or last would be to just roll our own substitution/evaluation syntax. > Add login username to source query comment, also session and request Id > ----------------------------------------------------------------------- > > Key: TEIID-2880 > URL: https://issues.jboss.org/browse/TEIID-2880 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Rick Wagner > Assignee: Steven Hawkins > Fix For: 8.7 > > > The user occasionally has problematic queries and while they can go through the command logs to find some details sometimes under heavy usage the logs are rotated at such a rate that they lose the information. > Please add the login id, session Id, and request Id to the source query comment. -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2014