February 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3354) AdminConsole fails getting mat view info with data roles

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3354: ------------------------------------- Summary: AdminConsole fails getting mat view info with data roles Key: TEIID-3354 URL: https://issues.jboss.org/browse/TEIID-3354 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 Once data roles are enable the web console fails to get the mat view info - unless the user allows access to systemadmin for the admin user. I'm logging this initially against the Teiid side as depending on the resolution we may want to change the admin code (for example using a SYS.table). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3353) In SQL Server INSERT ... VALUES clause UUID is not substituted

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3353?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3353: --------------------------------------- I can confirm that this is still an issue. I'll assess for getting into 8.10 Final. > In SQL Server INSERT ... VALUES clause UUID is not substituted > -------------------------------------------------------------- > > Key: TEIID-3353 > URL: https://issues.jboss.org/browse/TEIID-3353 > Project: Teiid > Issue Type: Bug > Reporter: Nicholas D > Assignee: Steven Hawkins > > Teiid 8.4, SQL Server 2012 Express > I'm inserting into table with uniqueidentifier field > {code:sql} > INSERT INTO SOME_TABLE(some_uuid, some_ts) > VALUES (uuid(), now()) > {code} > and get something like > bq. 195 Remote org.teiid.translator.jdbc.JDBCExecutionException: 195 TEIID11013:TEIID11004 Error executing statement(s): [Prepared Values: [{ts '2015-02-24 21:02:23.803'}] SQL: INSERT INTO "DS"."dbo"."SOME_TABLE" ("SOME_UUID", "SOME_TS") VALUES (uuid(), ?)] > However if i use INSERT ... SELECT clause it's substituted normally: > {code:sql} > INSERT INTO SOME_TABLE(some_uuid, some_ts) > SELECT uuid(), now() > FROM SOME_OTHER_TABLE > LIMIT 1 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3346) File Source | Dot in file column names causes VDB deployment errors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3346?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3346: --------------------------------------- > Model name, or any nameinsource string, I met this error several time. Actually it should be fine in a name in source. It's expected though that any necessary quoting will already be present on the name in source. > We may document that column name can not contain a Dot to solve this issue. We do cover that on https://docs.jboss.org/author/display/TEIID/Identifiers The issue here is more the interaction with text table in that we expect the source text header name to match the column name. It would be quite hard to address this issue in general, but we could add logic specific to TEXTTABLE - either another way to specify the header name or that if the column name contains a '.' that the projected column name will simply use a replacement character. > File Source | Dot in file column names causes VDB deployment errors > ------------------------------------------------------------------- > > Key: TEIID-3346 > URL: https://issues.jboss.org/browse/TEIID-3346 > Project: Teiid > Issue Type: Bug > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > > In case a Delimited Flat file , contains a "Dot" character in any of the column names, we get an issue during Virtual Data Base deployment - > Root cause - > org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'UTF-8') COLUMNS [*]\"name.full\"[*] STRING," at line 1, column 126. > Invalid simple identifier format: [name.full] > > The query is : SELECT A."name.full",A."surname" FROM (EXEC tabwithdot.getFiles('tab.csv')) AS F, TEXTTABLE(TO_CHARS(F.file,'UTF-8') COLUMNS "name.full" STRING,"surname" STRING delimiter ' ' quote ' ' HEADER) AS A > > Please note, that although the column name [name.full], is enclosed in Double Quotes, still this issue is observed. > If there was instead any other special character, that works successfully. > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3346) File Source | Dot in file column names causes VDB deployment errors

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3346?page=com.atlassian.jira.plugin... ] Kylin Soong edited comment on TEIID-3346 at 2/25/15 4:51 AM: ------------------------------------------------------------- This may not a bug, it seems it's default design behavior which can not use Dot as column name, Model name, or any nameinsource string, I met this error several time. [1] can quick reproduce, No Dot logic seems defined in javacc SQLParser.jj file. We may document that column name can not contain a Dot to solve this issue. [1] https://github.com/kylinsoong/teiid-samples/blob/master/teiid-test/src/ma... was (Author: kylin): This may not a bug, it seems it's default design behavior which can not use Dot as column name, Model name, or any nameinsource string, I met this error several time. > File Source | Dot in file column names causes VDB deployment errors > ------------------------------------------------------------------- > > Key: TEIID-3346 > URL: https://issues.jboss.org/browse/TEIID-3346 > Project: Teiid > Issue Type: Bug > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > > In case a Delimited Flat file , contains a "Dot" character in any of the column names, we get an issue during Virtual Data Base deployment - > Root cause - > org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'UTF-8') COLUMNS [*]\"name.full\"[*] STRING," at line 1, column 126. > Invalid simple identifier format: [name.full] > > The query is : SELECT A."name.full",A."surname" FROM (EXEC tabwithdot.getFiles('tab.csv')) AS F, TEXTTABLE(TO_CHARS(F.file,'UTF-8') COLUMNS "name.full" STRING,"surname" STRING delimiter ' ' quote ' ' HEADER) AS A > > Please note, that although the column name [name.full], is enclosed in Double Quotes, still this issue is observed. > If there was instead any other special character, that works successfully. > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3346) File Source | Dot in file column names causes VDB deployment errors

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3346?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3346: ------------------------------------ This may not a bug, it seems it's default design behavior which can not use Dot as column name, Model name, or any nameinsource string, I met this error several time. > File Source | Dot in file column names causes VDB deployment errors > ------------------------------------------------------------------- > > Key: TEIID-3346 > URL: https://issues.jboss.org/browse/TEIID-3346 > Project: Teiid > Issue Type: Bug > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > > In case a Delimited Flat file , contains a "Dot" character in any of the column names, we get an issue during Virtual Data Base deployment - > Root cause - > org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'UTF-8') COLUMNS [*]\"name.full\"[*] STRING," at line 1, column 126. > Invalid simple identifier format: [name.full] > > The query is : SELECT A."name.full",A."surname" FROM (EXEC tabwithdot.getFiles('tab.csv')) AS F, TEXTTABLE(TO_CHARS(F.file,'UTF-8') COLUMNS "name.full" STRING,"surname" STRING delimiter ' ' quote ' ' HEADER) AS A > > Please note, that although the column name [name.full], is enclosed in Double Quotes, still this issue is observed. > If there was instead any other special character, that works successfully. > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3260) Create custom metadata repository that uses Modeshape

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIID-3260?page=com.atlassian.jira.plugin... ] Paul Richardson commented on TEIID-3260: ---------------------------------------- [~blafond] is referring to the Teiid BNF of course. The Teiid BNF and the Teiid javacc template were the starting points for both the Modeshape TeiidSQL CND and Sequencer. * Steps taken in creation of Teiid SQL Sequencer ** The Teiid javacc template was copied and converted to a [jjt template|https://github.com/Teiid-Designer/komodo/blob/master/plugins/org...] ** Since the Teiid parser acts on language objects, those classes were migrated from Teiid. However, their inner state has been stripped out and their logic converted to extending AstNode (a convenient intermittent step between parser and MS node creation) ** The Teiid SQL Sequencing calls the Teiid SQL parser, which generates the tree of AstNodes, which queues up and stores them as JcrNodes in the MS repository. ** The class [TeiidCndGenerator|https://github.com/Teiid-Designer/komodo/blob/master/pl...] executes standalone, reading in the jjt template and converting it to an MS [CND|https://github.com/Teiid-Designer/komodo/blob/master/plugins/org.komo...] and a convenient TeiidSQL [Lexicon constants class|https://github.com/Teiid-Designer/komodo/blob/master/plugins/org.ko...]. The CND has to be plugged into the Sequencer so that it knows the correct NodeTypes from which to create the JcrNodes. ** The class [TeiidNodeFactoryGenerator|https://github.com/Teiid-Designer/komodo/blob/m...] executes standalone, reading in the generated Teiid SQL parser's TeiidSequencingParserTreeConstants class and converting it to a [factory class|https://github.com/Teiid-Designer/komodo/blob/master/plugins/org.ko...] for use in creating the AstNodes for the sequencing process Given the generator classes are standalone and executed manually, their generated classes are version-controlled (under the demi-gen folder), whilst the parser (like Teiid) is generated from the jjt template so never checked-in to git. Should a change to Teiid's BNF be required then the jjt template will be updated and the generator classes executed to update the MS-related components. > Create custom metadata repository that uses Modeshape > ----------------------------------------------------- > > Key: TEIID-3260 > URL: https://issues.jboss.org/browse/TEIID-3260 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Create a custom metadata repository implementation that uses ModeShape as the repository for obtaining the VDB metadata for deployment. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3353) In SQL Server INSERT ... VALUES clause UUID is not substituted

by Nicholas D (JIRA)

Nicholas D created TEIID-3353: --------------------------------- Summary: In SQL Server INSERT ... VALUES clause UUID is not substituted Key: TEIID-3353 URL: https://issues.jboss.org/browse/TEIID-3353 Project: Teiid Issue Type: Bug Reporter: Nicholas D Assignee: Steven Hawkins Teiid 8.4, SQL Server 2012 Express I'm inserting into table with uniqueidentifier field {code:sql} INSERT INTO SOME_TABLE(some_uuid, some_ts) VALUES (uuid(), now()) {code} and get something like bq. 195 Remote org.teiid.translator.jdbc.JDBCExecutionException: 195 TEIID11013:TEIID11004 Error executing statement(s): [Prepared Values: [{ts '2015-02-24 21:02:23.803'}] SQL: INSERT INTO "DS"."dbo"."SOME_TABLE" ("SOME_UUID", "SOME_TS") VALUES (uuid(), ?)] However if i use INSERT ... SELECT clause it's substituted normally: {code:sql} INSERT INTO SOME_TABLE(some_uuid, some_ts) SELECT uuid(), now() FROM SOME_OTHER_TABLE LIMIT 1 {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3260) Create custom metadata repository that uses Modeshape

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-3260?page=com.atlassian.jira.plugin... ] Barry LaFond edited comment on TEIID-3260 at 2/24/15 11:06 AM: --------------------------------------------------------------- Fundamentally, the node structure for the *VDB* metadata will be identical for both *library* or *workspace* modes. Only real difference will be in the lock/access restrictions. How the nodes and properties are actually accessesed and edited is an implementation layer. Designer is designing one version of it for "Design-time". No reason why Teiid Metadata Factory couldn't write their own layer based on your runtime behavior/characteristics. You'd have to look at our editing layer which involves relational-like objects (Table, Column, Procedure, etc...) that provide convenience methods for getting/setting/adding/removing that delegate to the JCR/MS layer without holding any state information other than the repository PATH string value. Keeps it light weight. (Interfaces and Impl's are here: https://github.com/Teiid-Designer/komodo/tree/master/plugins/org.komodo.r...) The CNDs and sequencers for the VDB, Teiid DDL and SQL components of the VDB artifacts, in theory, should be maintained and kept in sync with BNF and vdb-deployer.xsd schema. These CND's and corresponding sequencers are the bread and butter of what Modeshape provides. To date, this work has been by tooling. If you wish to take ownership of those components from a Teiid Project perspective, that'd be great as long as it's exposed, accessible and integratable from the Komodo Tooling perspective. Btw... the requirement for Komodo Engine to resolve DDL/SQL will inherently support dependency/impact analysis. was (Author: blafond): Fundamentally, the node structure for the *VDB* metadata will be identical for both *library* or *workspace* modes. Only real difference will be in the lock/access restrictions. How the nodes and properties are actually accessesed and edited is an implementation layer. Designer is designing one version of it for "Design-time". No reason why Teiid Metadata Factory couldn't write their own layer based on your runtime behavior/characteristics. You'd have to look at our editing layer which involves relational-like objects (Table, Column, Procedure, etc...) that provide convenience methods for getting/setting/adding/removing that delegate to the JCR/MS layer without holding any state information other than the repository PATH string value. Keeps it light weight. (Interfaces and Impl's are here: https://github.com/Teiid-Designer/komodo/tree/master/plugins/org.komodo.r...) The CNDs and sequencers for the VDB, Teiid DDL and SQL components of the VDB artifacts, in theory, should be maintained and kept in sync with BNF and vdb-deployer.xsd schema. These CND's and corresponding sequencers are the bread and butter of what Modeshape provides. To date, this work has been by tooling. If you wish to take ownership of those components from a Teiid Project perspective, that'd be great as long as it's exposed, accessible and integratable from the Komodo Tooling perspective. > Create custom metadata repository that uses Modeshape > ----------------------------------------------------- > > Key: TEIID-3260 > URL: https://issues.jboss.org/browse/TEIID-3260 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Create a custom metadata repository implementation that uses ModeShape as the repository for obtaining the VDB metadata for deployment. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Designer needs a way to utilize pushdown functions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2785: ------------------------------------------------ asmigala(a)redhat.com changed the Status of [bug 1045206|https://bugzilla.redhat.com/show_bug.cgi?id=1045206] from ON_QA to ASSIGNED > Designer needs a way to utilize pushdown functions > -------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7 > > > Pushdown functions, such as the ones exposed by the ModeShapeExecutionFactory, should be available at design time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2783) ModeShape query isn't retaining quotes defined for column in NIS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2783?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2783: ------------------------------------------------ asmigala(a)redhat.com changed the Status of [bug 1045206|https://bugzilla.redhat.com/show_bug.cgi?id=1045206] from ON_QA to ASSIGNED > ModeShape query isn't retaining quotes defined for column in NIS > ---------------------------------------------------------------- > > Key: TEIID-2783 > URL: https://issues.jboss.org/browse/TEIID-2783 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Attachments: ModeShape.vdb > > > Issuing query: > SELECT jcr_name FROM nt_base AS children WHERE JCR_ISCHILDNODE(children.jcr_path, '/pathtoparent') > produces exception: > Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_0.jcr:name FROM "nt:base" AS g_0 WHERE ISCHILDNODE(g_0.jcr:path, '/pathtoparent')" is not well-formed: Expecting "FROM" but found ":" at line 1, column 15: SELECT g_0.jcr ===>> :name FROM "nt:base" > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146) > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2015