[JBoss JIRA] (TEIID-4573) Modeshape query
by Horia Chiorean (JIRA)
[ https://issues.jboss.org/browse/TEIID-4573?page=com.atlassian.jira.plugin... ]
Horia Chiorean edited comment on TEIID-4573 at 11/14/16 1:10 PM:
-----------------------------------------------------------------
[~van.halbert] the WHERE clause should not use {{"}} quotes when testing for JCR properties. It should either use {{\[jcr:path\]}} or simply nothing {{g_1.jcr:path = g_2.jcr:path}}
was (Author: hchiorean):
[~van.halbert] the WHERE clause should not use {\"} quotes when testing for JCR properties. It should either use {\\[jcr:path\\]} or simply nothing {{g_1.jcr:path = g_2.jcr:path}}
> Modeshape query
> ---------------
>
> Key: TEIID-4573
> URL: https://issues.jboss.org/browse/TEIID-4573
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.0
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
> Labels: modeshape
> Fix For: 9.2, 9.1.2
>
>
> The following modeshape vdb query fails.
> select a.jcr_path, a.table_name ,b.jcr_name
> from "Relational_Model_View"."Table_Columns" a, "ModeShape"."xmi_model" b
> where a.jcr_path = b.jcr_path
> the error is:
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 ModeShape: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_1."jcr:path", g_0."mode:localName", g_2."jcr:name" FROM "relational:table" AS g_0 INNER JOIN "relational:column" AS g_1 ON ISCHILDNODE(g_1, g_0) INNER JOIN "xmi:model" AS g_2 ON g_1."jcr:path" = g_2."jcr:path" AND ISCHILDNODE(g_2, g_0)]
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4565) Add objects table to system schema
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4565?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4565:
---------------------------------------
> The idea is similar to the dba/all_objects
So that would not include properties, but would include all object types not just table/column.
> The reason for this is that I can peruse this object when a search is triggered and know not only a match but also the object type.
Can you clarify what is driving this search? uid, object name/schema, etc.
> Additionally, there is object id found in the Oracle example I would presume this is the uid or oid moving forward, correct?
uid is our concept of a unique object id yes.
> Add objects table to system schema
> ----------------------------------
>
> Key: TEIID-4565
> URL: https://issues.jboss.org/browse/TEIID-4565
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
>
> The addition of a objects table would make it simpler to join to when extensions are implemented.
> An example might be something similar to this query:
> select sysObjects.*
> from (
> select t.schemaName as Parent,t.name, t.uid ,'Table' as ObjectType
> from sys.tables t
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select c.tableName as Parent,c.name, c.uid,'Column' as ObjectType
> from sys.columns c
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select null as Parent,e.Value as Name,e.uid,'Property' as ObjectType
> from sys.properties as e) as SysObjects
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4573) Modeshape query
by Horia Chiorean (JIRA)
[ https://issues.jboss.org/browse/TEIID-4573?page=com.atlassian.jira.plugin... ]
Horia Chiorean commented on TEIID-4573:
---------------------------------------
[~van.halbert] the WHERE clause should not use {\"} quotes when testing for JCR properties. It should either use {\\[jcr:path\\]} or simply nothing {{g_1.jcr:path = g_2.jcr:path}}
> Modeshape query
> ---------------
>
> Key: TEIID-4573
> URL: https://issues.jboss.org/browse/TEIID-4573
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.0
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
> Labels: modeshape
> Fix For: 9.2, 9.1.2
>
>
> The following modeshape vdb query fails.
> select a.jcr_path, a.table_name ,b.jcr_name
> from "Relational_Model_View"."Table_Columns" a, "ModeShape"."xmi_model" b
> where a.jcr_path = b.jcr_path
> the error is:
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 ModeShape: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_1."jcr:path", g_0."mode:localName", g_2."jcr:name" FROM "relational:table" AS g_0 INNER JOIN "relational:column" AS g_1 ON ISCHILDNODE(g_1, g_0) INNER JOIN "xmi:model" AS g_2 ON g_1."jcr:path" = g_2."jcr:path" AND ISCHILDNODE(g_2, g_0)]
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4570) RestWebservice war Generation failed due to split out rest related logic to rest-service
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4570?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4570.
---------------------------------
Resolution: Done
Moved the VDBLifecycleListener specific stuff inside the jboss-integration and provided the war generation as modular code that can be service load to keep the dependencies in check.
This also provides a way generate the WAR file explicitly that can be used with deployments like "embedded".
> RestWebservice war Generation failed due to split out rest related logic to rest-service
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-4570
> URL: https://issues.jboss.org/browse/TEIID-4570
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.2
> Reporter: Kylin Soong
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> The logic related with RestWebservice war Generation be removed from VDBService, we need roll back it now
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4573) Modeshape query
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4573?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4573:
---------------------------------------
That's not related to this fix directly as the new source query has the expected predicate placement. This is another issue with ModeShape/JCR SQL2 in that it allows only literal comparison predicates in the where clause. There is a Teiid capability that requires literal only comparisons - but only if the predicate is rejected as an allowed join criteria, which is not the case here. Expanding the notion of allowed join criteria to include functional expressions seems well beyond the norm of what we want to capture in capabilities, so I would suggest looking for a workaround by changing the user query.
> Modeshape query
> ---------------
>
> Key: TEIID-4573
> URL: https://issues.jboss.org/browse/TEIID-4573
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.0
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
> Labels: modeshape
> Fix For: 9.2, 9.1.2
>
>
> The following modeshape vdb query fails.
> select a.jcr_path, a.table_name ,b.jcr_name
> from "Relational_Model_View"."Table_Columns" a, "ModeShape"."xmi_model" b
> where a.jcr_path = b.jcr_path
> the error is:
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 ModeShape: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_1."jcr:path", g_0."mode:localName", g_2."jcr:name" FROM "relational:table" AS g_0 INNER JOIN "relational:column" AS g_1 ON ISCHILDNODE(g_1, g_0) INNER JOIN "xmi:model" AS g_2 ON g_1."jcr:path" = g_2."jcr:path" AND ISCHILDNODE(g_2, g_0)]
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4565) Add objects table to system schema
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIID-4565?page=com.atlassian.jira.plugin... ]
Tom Johnston commented on TEIID-4565:
-------------------------------------
Sorry for the delay...
The idea is similar to the dba/all_objects table in Oracle (ex. https://docs.oracle.com/cd/E18283_01/server.112/e17110/statviews_1155.htm...)
The reason for this is that I can peruse this object when a search is triggered and know not only a match but also the object type. Note that the Oracle example does not include descriptions/comments but I would like for to but am open to discuss that. Additionally, there is object id found in the Oracle example I would presume this is the uid or oid moving forward, correct?
> Add objects table to system schema
> ----------------------------------
>
> Key: TEIID-4565
> URL: https://issues.jboss.org/browse/TEIID-4565
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
>
> The addition of a objects table would make it simpler to join to when extensions are implemented.
> An example might be something similar to this query:
> select sysObjects.*
> from (
> select t.schemaName as Parent,t.name, t.uid ,'Table' as ObjectType
> from sys.tables t
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select c.tableName as Parent,c.name, c.uid,'Column' as ObjectType
> from sys.columns c
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select null as Parent,e.Value as Name,e.uid,'Property' as ObjectType
> from sys.properties as e) as SysObjects
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4573) Modeshape query
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4573?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4573:
------------------------------------
Created a jdbc patch and still getting:
Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_1."jcr:path", g_0."mode:localName", g_2."jcr:name" FROM "relational:table" AS g_0 INNER JOIN "relational:column" AS g_1 ON ISCHILDNODE(g_1, g_0) INNER JOIN "xmi:model" AS g_2 ON ISCHILDNODE(g_2, g_0) WHERE g_1."jcr:path" = g_2."jcr:path"" is not well-formed: Expecting literal and unable to parse 'g_2."jcr:path"' at line 1, column 233 as a double
> Modeshape query
> ---------------
>
> Key: TEIID-4573
> URL: https://issues.jboss.org/browse/TEIID-4573
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.0
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
> Labels: modeshape
> Fix For: 9.2, 9.1.2
>
>
> The following modeshape vdb query fails.
> select a.jcr_path, a.table_name ,b.jcr_name
> from "Relational_Model_View"."Table_Columns" a, "ModeShape"."xmi_model" b
> where a.jcr_path = b.jcr_path
> the error is:
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 ModeShape: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_1."jcr:path", g_0."mode:localName", g_2."jcr:name" FROM "relational:table" AS g_0 INNER JOIN "relational:column" AS g_1 ON ISCHILDNODE(g_1, g_0) INNER JOIN "xmi:model" AS g_2 ON g_1."jcr:path" = g_2."jcr:path" AND ISCHILDNODE(g_2, g_0)]
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4565) Add objects table to system schema
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4565?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4565:
---------------------------------------
Without additional information/corrections, I'll have to mark this as incomplete description.
> Add objects table to system schema
> ----------------------------------
>
> Key: TEIID-4565
> URL: https://issues.jboss.org/browse/TEIID-4565
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
>
> The addition of a objects table would make it simpler to join to when extensions are implemented.
> An example might be something similar to this query:
> select sysObjects.*
> from (
> select t.schemaName as Parent,t.name, t.uid ,'Table' as ObjectType
> from sys.tables t
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select c.tableName as Parent,c.name, c.uid,'Column' as ObjectType
> from sys.columns c
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select null as Parent,e.Value as Name,e.uid,'Property' as ObjectType
> from sys.properties as e) as SysObjects
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months