[JBoss JIRA] Created: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
1:38 p.m.
API request: rewrite query/command before it reaches the teiid planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:44 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://jira.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins commented on TEIID-1326:
---------------------------------------
Is this only for view definitions? Are the view definitions changing at runtime, possibly
depending upon the user/role?
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:04 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://jira.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin.s...
]
Mark Addleman commented on TEIID-1326:
--------------------------------------
Our primary use case is for view definitions although I imagine altering the SQL based on
user/role. Here are two use cases:
1) We have a dynamic set of datasources that we access through Teiid. As the list of
data sources changes, the list of UNIONed SELECTs would change.
2) To provide row-level security, we would re-write the query to include appopriate WHERE
clause and/or joins based on the user's user id and/or role.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://jira.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins commented on TEIID-1326:
---------------------------------------
1) it seems like we would traditionally define this as some combination of multi-source /
partial results support. are your sources heterogeneous database types and/or do they
have different tables/column that you are integrating?
2) could changing the SELECT or the WHERE based upon the user / role allow this to be done
with a single view definition: select case when hasRole... end from ... where col = case
user() ... end?
To state this slightly differently, if you just had a way to statically define views (with
SQL that enforces the security) and then utilized multi-source support to dynamically add
or remove homogeneous sources, would that meet your needs?
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:33 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://jira.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin.s...
]
Mark Addleman commented on TEIID-1326:
--------------------------------------
I've never gotten multi-source models to work using dynamic VDBs but assuming it does,
I still see a problem. Our data sources fall into two categories: a set of app specific
metadata tables and then data tables.
The app specific metadata tables have a homogeneous structure although we currently allow
the names of the tables to vary across data source. These app specific metadata tables
are then unioned together in a corresponding set of app specific metadata views from which
the application reads its metadata. We currently implement this as a recursive translator
which dynamically rewrites queries (similar to the example above) and unions the
appropriate tables. If we used multi-source models, how would Teiid union together the
data source specific metadata tables? Would we require that all of the metadata tables
have the same names?
A further complication: We use Teiid to access these app specific metadata tables which
allow us to keep the physical storage of the metadata separate from the logical
presentation. Some of our metadata is physically stored in CSV files and we create Teiid
views (again using this recursive translator) based on TEXTTABLE to create the appropriate
logical Teiid view of the data. If we went went the multi-source model approach, could
the source be another view? I see a problem trying to dynamically read the Teiid
metadata. Currently, to define a view using our recursive translator, you have to
statically supply the Teiid metadata.
The data tables for our application have heterogeneous schemas and I think that static
views on top of those to define security requirements (we probably can't use hasRole,
instead we would write a custom security function) would work just fine.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:50 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://jira.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins commented on TEIID-1326:
---------------------------------------
So without significant changes multi-source is not a good fit here as it assumes the same
physical metadata for each source - which works best if the sources are the same database
type.
Could we could give you hook to change just the view definitions rather than the whole
query structure at runtime?
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:01 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://jira.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin.s...
]
Mark Addleman commented on TEIID-1326:
--------------------------------------
Yes, a hook to dynamically change the view definitions seems like it would work
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:01 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://jira.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins updated TEIID-1326:
----------------------------------
Fix Version/s: 7.3
Complexity: Low
Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 7.3
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:31 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1326:
---------------------------------------
Here again would you want the connection to be present?
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 7.3
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1326:
----------------------------------
Fix Version/s: 7.4
(was: 7.3)
Pushing to 7.4
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:56 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1326:
--------------------------------------
I just saw your question. Here again would you want the connection to be present? I
don't think a connection is very useful (or maybe even possible) at the point before
it reaches the query planner.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:05 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1326:
---------------------------------------
added the org.teiid.metadata.MetadataProvider interface in teiid api. An instance can be
injected onto the RuntimeEngineDeployer via the setMetadataProvider method.
The instance will be consulted to provide ViewDefinitions, which are simply the sql text
and a scope so that it can be made specific to the user rather than applying to the whole
vdb. The instance will be consulted once per request for each view accessed. This keeps
the view definition consistent for planning purposes, such as determining union
partitions, default updatablity, etc.
The view definition will have a basic validation check, but we are not currently looking
for advanced issues such as potentially recursive definitions.
Some general tie will be needed in the cache eventing logic to purge prepared plans that
have had their views modified.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:28 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1326:
---------------------------------------
I should add that this approach has several advantages over the current direct
manipulation of Table metadata records (possibly through ddl).
1. that the view definitions can be made user specific, without api changes to the
metadata classes.
2. a single class can be consulted which can simplify updating the same view across
multiple vdb versions.
3. dml or a single instance administrative call would need to made on each member in a
cluster (we may address this through a live operational repository in the future)
4. related to number 3, changes to the metadata records are not-persistent.
So having this metadata update or costing updates, etc. through a real operational
repository with notifications can be a long term direction, but for now we'll have to
settle.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:05 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1326.
-----------------------------------
Labels: 7.4CR1 (was: )
Resolution: Done
Added alter statements to allow for the update of view and procedure definitions at
runtime. For these updates to be persistent the system must be configured with a
org.teiid.metadata.MetadataRepository. The relevant docs will be in the reference and the
developers guide.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Labels: 7.4CR1
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 a.m.
New subject: [JBoss JIRA] (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Mark Addleman reopened TEIID-1326:
----------------------------------
It looks like trunk/api/src/main/java/org/teiid/metadata/MetadataProvider.java was deleted
as part of TEIID-245. I suspect this was a mistake?
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Labels: 7.4CR1
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 a.m.
New subject: [JBoss JIRA] (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1326:
--------------------------------------
It looks like trunk/api/src/main/java/org/teiid/metadata/MetadataProvider.java was deleted
as part of TEIID-245. I suspect this was a mistake?
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Labels: 7.4CR1
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:35 a.m.
New subject: [JBoss JIRA] (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1326:
---------------------------------------
See the MetadataRepository interface instead. The name was changed to better reflect that
it is now read/write.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Labels: 7.4CR1
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:49 a.m.
New subject: [JBoss JIRA] (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1326:
--------------------------------------
Thanks!
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Labels: 7.4CR1
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:40 p.m.
New subject: [JBoss JIRA] (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1326.
-----------------------------------
Resolution: Done
re-resolving. the docs do mention mention MetadataRepository, and it covered in the
teiid-jboss-beans.xml. With AS7, we'll need to update the docs more extensively as we
won't have the inline beans.xml documentation.
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Labels: 7.4CR1
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:19 a.m.
New subject: [JBoss JIRA] (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
[
https://issues.jboss.org/browse/TEIID-1326?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1326.
---------------------------------
API request: rewrite query/command before it reaches the teiid
planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://issues.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Labels: 7.4CR1
Fix For: 7.4
I'd like an API to inspect and rewrite a user query/command before it reaches the
Teiid planner. The use case is to rewrite the query/command to implement view-like
capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data
structure representing the query/command and use a visitor to rewrite the query. As a
convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4610
days inactive
5179
days old
19 comments
6 participants
participants (6)
-
Mark Addleman (Commented) (JIRA) -
Mark Addleman (JIRA)
-
Mark Addleman (Reopened) (JIRA)
-
Steven Hawkins (Commented) (JIRA)
-
Steven Hawkins (JIRA)
-
Steven Hawkins (Resolved) (JIRA)