June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4267) Add units into the cli description of transport property "authentication-sessions-expiration-timelimit"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4267?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4267. ----------------------------------- Fix Version/s: 9.1 Resolution: Done Added milliseconds to the description > Add units into the cli description of transport property "authentication-sessions-expiration-timelimit" > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4267 > URL: https://issues.jboss.org/browse/TEIID-4267 > Project: Teiid > Issue Type: Quality Risk > Components: AdminApi > Affects Versions: 8.7.6.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.1 > > > Currently if you run a cli command on the transports, ie /subsystem=teiid/transport=JDBC:read-resource-description no unit value shows for the "authentication-sessions-expiration-timelimit" description, can (in milliseconds) be added to the description? > "authentication-sessions-expiration-timelimit" => { > "type" => INT, > "description" => "Max allowed time before the session is terminated by the system, 0 indicates unlimited (default 0)", > "expressions-allowed" => false, > "nillable" => true, > "default" => 0, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4276) Default for max sessions not consistently updated

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4276: ------------------------------------- Summary: Default for max sessions not consistently updated Key: TEIID-4276 URL: https://issues.jboss.org/browse/TEIID-4276 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 9.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 The session service change for 9.0 doubled the default to 10000, but it was not updated everywhere. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4187: ------------------------------------- Examples of executing the queries on PI through Teiid. See usage of LATERAL JOIN to execute TVF functions {code} SELECT eh.Path, eh.Name, ea.Name, a."Time", a."Value" FROM Sample.Asset.ElementHierarchy eh INNER JOIN Sample.Asset.ElementAttribute ea ON ea.ElementID = eh.ElementID INNER JOIN Sample.Data.Archive a ON a.ElementAttributeID = ea.ID WHERE eh.Path = '\Data Center\' AND a."Time" BETWEEN TIMESTAMPADD(SQL_TSI_HOUR, -1, now()) AND now() SELECT g_0."StartTime", g_1."Name", g_0."Time", g_0."Number of Computers", g_0."Temperature" FROM "Sample"."DataT"."ft_TransposeArchive_Building Template" AS g_0, "Sample"."Asset"."ElementHierarchy" AS g_1 WHERE g_1."ElementID" = g_0."ElementID" AND g_0."EndTime" = '2016-06-16 16:16:50.187' AND g_0."ElementID" IN (SELECT cast(g_2."ElementID" as String) FROM "Sample"."Asset"."ElementHierarchy" AS g_2 WHERE g_2."Path" = '\Data Center\') SELECT EH.Name, BT."Time", BT."Number of Computers", BT."Temperature" FROM Sample.Asset.ElementHierarchy EH LEFT JOIN LATERAL (exec "TransposeArchive_Building Template"(EH.ElementID, TIMESTAMPADD(SQL_TSI_HOUR, -1, now()), now())) BT on 1=1 WHERE EH.ElementID IN (SELECT ElementID FROM Sample.Asset.ElementHierarchy WHERE Path='\Data Center\') {code} > Extend support for PI OLEDB Enterprise Queries in OSI PI Translator > ------------------------------------------------------------------- > > Key: TEIID-4187 > URL: https://issues.jboss.org/browse/TEIID-4187 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Al S > Assignee: Ramesh Reddy > Priority: Minor > Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf > > > Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. > Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. > 1) Import table valued functions as Teiid procedures > 2) Allow the pushdown of nested table joins > 3) Update the PI translator to use the CROSS APPLY syntax. > 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this? > Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4275) No NIS is setup for the Procedure parameters during the JDBC metadata import

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4275?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4275. ----------------------------------- Resolution: Done Added the quoted column name as the name in source. > No NIS is setup for the Procedure parameters during the JDBC metadata import > ---------------------------------------------------------------------------- > > Key: TEIID-4275 > URL: https://issues.jboss.org/browse/TEIID-4275 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 9.1 > > > NameInSource property is not automatically set during the "NATIVE" matadata load of the metadata, and when a procedure's column is defined with spaces inside it, the SQLStringVisitor never quotes it, thus ends up parsing error when writing the queries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4267) Add units into the cli description of transport property "authentication-sessions-expiration-timelimit"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4267?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4267: ---------------------------------- Issue Type: Quality Risk (was: Feature Request) > Add units into the cli description of transport property "authentication-sessions-expiration-timelimit" > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4267 > URL: https://issues.jboss.org/browse/TEIID-4267 > Project: Teiid > Issue Type: Quality Risk > Components: AdminApi > Affects Versions: 8.7.6.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > Currently if you run a cli command on the transports, ie /subsystem=teiid/transport=JDBC:read-resource-description no unit value shows for the "authentication-sessions-expiration-timelimit" description, can (in milliseconds) be added to the description? > "authentication-sessions-expiration-timelimit" => { > "type" => INT, > "description" => "Max allowed time before the session is terminated by the system, 0 indicates unlimited (default 0)", > "expressions-allowed" => false, > "nillable" => true, > "default" => 0, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4275) No NIS is setup for the Procedure parameters during the JDBC metadata import

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4275: ----------------------------------- Summary: No NIS is setup for the Procedure parameters during the JDBC metadata import Key: TEIID-4275 URL: https://issues.jboss.org/browse/TEIID-4275 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 9.1 NameInSource property is not automatically set during the "NATIVE" matadata load of the metadata, and when a procedure's column is defined with spaces inside it, the SQLStringVisitor never quotes it, thus ends up parsing error when writing the queries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4266) Convert the Teiid examples to gitbook

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4266?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4266: --------------------------------------- Thanks Kylin. That looks like a good conversion. > Convert the Teiid examples to gitbook > ------------------------------------- > > Key: TEIID-4266 > URL: https://issues.jboss.org/browse/TEIID-4266 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.1 > > > https://docs.jboss.org/author/display/teiidexamples/Home should be added to our gitbook documentation set to complete the move out of Confluence. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4187: ------------------------------------- 1) Turned OFF capability for "FULL OUTER JOINS", as PI does not support this 2) Turned ON capability for "supportsInlineViews" for allowing the Nested tables. 3) Added following UDF {code} addPushDownFunction(PI, "ParentName", STRING, STRING, INTEGER); //$NON-NLS-1$ addPushDownFunction(PI, "VarType", STRING, STRING); //$NON-NLS-1$ addPushDownFunction(PI, "UOMID", STRING, STRING); //$NON-NLS-1$ addPushDownFunction(PI, "UOMName", STRING, STRING); //$NON-NLS-1$ addPushDownFunction(PI, "UOMAbbreviation", STRING, STRING); //$NON-NLS-1$ addPushDownFunction(PI, "UOMClassName", STRING, STRING); //$NON-NLS-1$ addPushDownFunction(PI, "UOMCanonicallD", STRING, STRING); //$NON-NLS-1$ addPushDownFunction(PI, "UOMConvert", DOUBLE, DOUBLE, STRING, STRING); //$NON-NLS-1$ {code} 4) During the metadata import converted all the artifacts with "guid" column type to "string" in Teiid, the translator also does the appropriate casting for value handling. 5) Added a "extension-metadata" property called "TVF", that can be used decorate tables and procedures as Table Valued functions, which can be used in lateral joins 6) Added support for push down of LATERAL JOINS, so that a LATERAL JOIN is converted to "CROSS APPLY" or "OUTER APPLY" commands in PI > Extend support for PI OLEDB Enterprise Queries in OSI PI Translator > ------------------------------------------------------------------- > > Key: TEIID-4187 > URL: https://issues.jboss.org/browse/TEIID-4187 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Al S > Assignee: Ramesh Reddy > Priority: Minor > Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf > > > Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. > Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. > 1) Import table valued functions as Teiid procedures > 2) Allow the pushdown of nested table joins > 3) Update the PI translator to use the CROSS APPLY syntax. > 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this? > Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3770) HBase - table's alias (... AS ...) is not "visible" in SELECT caluse in IN predicate

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3770?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3770: --------------------------------------- Ok to mark this as won't fix? If there are too many circumstances where there's issues with phoenix/HBase correlated subqueries, then we'll just shut off support. > HBase - table's alias (... AS ...) is not "visible" in SELECT caluse in IN predicate > ------------------------------------------------------------------------------------ > > Key: TEIID-3770 > URL: https://issues.jboss.org/browse/TEIID-3770 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Query: > SELECT INTKEY, BIGDECIMALVALUE FROM BQT1.SMALLA AS A WHERE BIGDECIMALVALUE *IN (SELECT MAX(BIGDECIMALVALUE) FROM BQT1.SMALLA AS B WHERE _A_.INTKEY = B.INTKEY)* ORDER BY INTKEY > It seems like bug in Phoenix driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3685) org.teiid.padSpace does not affect to the "IN" operator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3685?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3685: ---------------------------------- Fix Version/s: 8.12.5 > org.teiid.padSpace does not affect to the "IN" operator > ------------------------------------------------------- > > Key: TEIID-3685 > URL: https://issues.jboss.org/browse/TEIID-3685 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: JBoss DV 6.1.2 > Reporter: hisao furuichi > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0, 8.12.5, 8.7.7.6_2, 8.13.6, 9.0.1 > > Attachments: datasert.csv, INTERNAL_TEST.zip, test.vdb > > > org.teiid.padSpace does affect to "=" operator. But does not affect to "IN" operator. > [data for a column named "id"] > {noformat} > "test1 " > {noformat} > ["=" operator] I can get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id ='TEST1'; > {noformat} > ["IN" operator] I can not get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id IN ('TEST1', 'TEST2'); > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016