June 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2527) Dynamically change the sources in a multi-source model

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2527?page=com.atlassian.jira.plugin... ] Mark Addleman updated TEIID-2527: --------------------------------- Description: As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, seehttps://community.jboss.org/message/821113 > Dynamically change the sources in a multi-source model > ------------------------------------------------------ > > Key: TEIID-2527 > URL: https://issues.jboss.org/browse/TEIID-2527 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Addleman > Assignee: Steven Hawkins > > As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, seehttps://community.jboss.org/message/821113 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2527) Dynamically change the sources in a multi-source model

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2527?page=com.atlassian.jira.plugin... ] Mark Addleman updated TEIID-2527: --------------------------------- Description: As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, see https://community.jboss.org/message/821113 was: As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, seehttps://community.jboss.org/message/821113 > Dynamically change the sources in a multi-source model > ------------------------------------------------------ > > Key: TEIID-2527 > URL: https://issues.jboss.org/browse/TEIID-2527 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Addleman > Assignee: Steven Hawkins > > As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, see https://community.jboss.org/message/821113 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2527) Dynamically change the sources in a multi-source model

by Mark Addleman (JIRA)

Mark Addleman created TEIID-2527: ------------------------------------ Summary: Dynamically change the sources in a multi-source model Key: TEIID-2527 URL: https://issues.jboss.org/browse/TEIID-2527 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2522) Let Extract(<Oracle Date field>) extract time components

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2522?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2522: ---------------------------------- You should be able to work around this with: SELECT EXTRACT(HOUR FROM cast(cast(a.modifieddate as string) as timestamp)) ... > Let Extract(<Oracle Date field>) extract time components > -------------------------------------------------------- > > Key: TEIID-2522 > URL: https://issues.jboss.org/browse/TEIID-2522 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Alex K. > Assignee: Steven Hawkins > Priority: Minor > > According to the Oracle's docs: > > "The DATE datatype stores point-in-time values (dates and times) in a table. The DATE datatype stores the year (including the century), the month, the day, the hours, the minutes, and the seconds (after midnight)." > > I expect to be able to extract the time parts from a date field, but when I am trying to extract the hour from an oracle's date field like: > > {code:sql} > SELECT EXTRACT(HOUR FROM a.modifieddate) > FROM oracle_db.salestaxrate a > WHERE a.salestaxrateid = 1 > {code} > > and get a TEIID30504 exception. When I look deeper in Teiid's log, i see the following Oracle's exception: > > Caused by: java.sql.SQLException: Remote java.sql.SQLException: ORA-30076: invalid extract field for extract source > That is an odd Oracle limitation - http://docs.oracle.com/cd/B28359_01/server.111/b28286/functions052.htm > > "If HOUR, MINUTE, or SECOND is requested, then expr must evaluate to an expression of datatype TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITH LOCAL TIME ZONE, or INTERVAL DAY TO SECOND. DATE is not valid here, because Oracle Database treats it as ANSI DATE datatype, which has no time fields." > *please enable extracting of time components from oracle's Date Fields* despite the Oracle's limitation -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2524) Hive metadata import leaves whitespace characters in column names

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2524?page=com.atlassian.jira.plugin... ] Filip Nguyen commented on TEIID-2524: ------------------------------------- I am using the 0.11. I will try to go through the JIRAs you have collected and find out whether the issue is going to be addressed, if not I will probably log JIRA for Hive as this is not a bug in Teiid. > Hive metadata import leaves whitespace characters in column names > ----------------------------------------------------------------- > > Key: TEIID-2524 > URL: https://issues.jboss.org/browse/TEIID-2524 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > When hive translator starts with the newest Hive it runs "describe" command which returns Hive column names with white spaces. > Maybe just use trim() in HiveMetadataProcessor.java? > String name = rs.getString(1).trim(); -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2524) Hive metadata import leaves whitespace characters in column names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2524?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2524: --------------------------------------- So this is due 0.10.0 specific: https://issues.apache.org/jira/browse/HIVE-3140 which appears to be addressed by: https://issues.apache.org/jira/browse/HIVE-4191 or possibly (which has yet to be committed) https://issues.apache.org/jira/browse/HIVE-4545 The workaround is only generally safe as long as their column names cannot contain trailing/leading spaces. If they can, then we'd have to add an option for this trim behavior otherwise it looks like it is not an issue for 0.09.0 or 0.11.0. > Hive metadata import leaves whitespace characters in column names > ----------------------------------------------------------------- > > Key: TEIID-2524 > URL: https://issues.jboss.org/browse/TEIID-2524 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > When hive translator starts with the newest Hive it runs "describe" command which returns Hive column names with white spaces. > Maybe just use trim() in HiveMetadataProcessor.java? > String name = rs.getString(1).trim(); -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2524) Hive metadata import leaves white characters in table name

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2524?page=com.atlassian.jira.plugin... ] Filip Nguyen commented on TEIID-2524: ------------------------------------- Sorry for bad report. The problem are in fact column names. Mixed up in my mind. Below is my DDL and the query that I have to write to select from the INTKEY column. From hive console I can simply write "select intkey from smalla" and it works. {code} CREATE EXTERNAL TABLE smalla(INTKEY INT, STRINGKEY STRING, INTNUM INT, STRINGNUM STRING, FLOATNUM FLOAT, LONGNUM BIGINT, DOUBLENUM DOUBLE, BYTENUM DECIMAL, DATEVALUE TIMESTAMP, TIMEVALUE TIMESTAMP, TIMESTAMPVALUE TIMESTAMP, BOOLEANVALUE BOOLEAN, CHARVALUE STRING, SHORTVALUE SMALLINT, BIGINTEGERVALUE DECIMAL, BIGDECIMALVALUE DECIMAL, OBJECTVALUE BINARY) ROW FORMAT DELIMITED FIELDS TERMINATED BY '44' LINES TERMINATED BY '\n' STORED AS TEXTFILE LOCATION '/data/bqt/smalla'; {code} {code} ./run.sh QT_Hive_Push "select \"intkey \" from smalla" {code} > Hive metadata import leaves white characters in table name > ---------------------------------------------------------- > > Key: TEIID-2524 > URL: https://issues.jboss.org/browse/TEIID-2524 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > When hive translator starts with the newest Hive it runs "describe" command which returns Hive table names with white spaces. > Maybe just use trim() in HiveMetadataProcessor.java? > String name = rs.getString(1).trim(); -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2524) Hive metadata import leaves whitespace characters in column names

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2524?page=com.atlassian.jira.plugin... ] Filip Nguyen updated TEIID-2524: -------------------------------- Description: When hive translator starts with the newest Hive it runs "describe" command which returns Hive column names with white spaces. Maybe just use trim() in HiveMetadataProcessor.java? String name = rs.getString(1).trim(); was: When hive translator starts with the newest Hive it runs "describe" command which returns Hive table names with white spaces. Maybe just use trim() in HiveMetadataProcessor.java? String name = rs.getString(1).trim(); > Hive metadata import leaves whitespace characters in column names > ----------------------------------------------------------------- > > Key: TEIID-2524 > URL: https://issues.jboss.org/browse/TEIID-2524 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > When hive translator starts with the newest Hive it runs "describe" command which returns Hive column names with white spaces. > Maybe just use trim() in HiveMetadataProcessor.java? > String name = rs.getString(1).trim(); -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2524) Hive metadata import leaves whitespace characters in column names

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2524?page=com.atlassian.jira.plugin... ] Filip Nguyen updated TEIID-2524: -------------------------------- Summary: Hive metadata import leaves whitespace characters in column names (was: Hive metadata import leaves white characters in table name) > Hive metadata import leaves whitespace characters in column names > ----------------------------------------------------------------- > > Key: TEIID-2524 > URL: https://issues.jboss.org/browse/TEIID-2524 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > When hive translator starts with the newest Hive it runs "describe" command which returns Hive table names with white spaces. > Maybe just use trim() in HiveMetadataProcessor.java? > String name = rs.getString(1).trim(); -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2524) Hive metadata import leaves white characters in table name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2524?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2524: --------------------------------------- It seems quite odd for something like this to be random... Is that a known issue with Hive (similar to https://issues.apache.org/jira/browse/HIVE-3243) and can you provide your Hive DDL? > Hive metadata import leaves white characters in table name > ---------------------------------------------------------- > > Key: TEIID-2524 > URL: https://issues.jboss.org/browse/TEIID-2524 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > When hive translator starts with the newest Hive it runs "describe" command which returns Hive table names with white spaces. > Maybe just use trim() in HiveMetadataProcessor.java? > String name = rs.getString(1).trim(); -- 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, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2013