[JBoss JIRA] (TEIID-2578) add/remove schema elements
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2578:
-------------------------------------
Yes, when VIEW is created using the inline column definitions (with any extension metadata) etc, then ALTER is going to make sure any changes to the transformation confirms to the previously defined column structure. If user needs to add/drop any columns, then user MUST define the view in the second form.
> add/remove schema elements
> --------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-4021) MSSQL Pagination
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4021:
---------------------------------------
The assumption is that a single translator connects to a single source/version. However in the case of translators that auto-configure to the given version you are expecting that we'll manage creating new instances when necessary correct? Can you log something for that?
Another workaround is to add multiple executionfactory instances to allow for each to be configured independently.
> MSSQL Pagination
> ----------------
>
> Key: TEIID-4021
> URL: https://issues.jboss.org/browse/TEIID-4021
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> I'm using Teiid 8.11.3 with mssql translator.
> I have a huge table over sql server 2008 on which i'm applying pagination.
> I noticed slowliness in the query execution over this table at each time I increase the pagination.
> I monitored the JDBC queries execute by teiid and found out that it is using top n according to the limit used into the query.
> For example:
> in teiid : Select * from mytable LIMIT 90 , 10
> is translated in JDBC: select top 100 from mytable
> Since my table contains millions of records, when fetching the last page, the executed jdbc query is retrieving the whole table top n, to return in result the last 10 records. And the execution is taking too much time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-2578) add/remove schema elements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2578:
---------------------------------------
> not allow the user to define the column definitions inline
At least defining the column names is required. Also we need to associate extension metadata with the columns as well. So for CREATE there still needs to be the option to define the columns.
> add/remove schema elements
> --------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-2578) add/remove schema elements
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2578:
-------------------------------------
IMO, Teiid should have limited DDL language for definition of the VIEW to
{code}
CREATE VIEW <view-name> OPTIONS (...) AS <stmt>
ALTER VIEW <view-name> OPTIONS(...) AS <stmt>
{code}
as it defined other database view definitions, not allow the user to define the column definitions inline. This would have solved the above issue. I am leaning towards limiting the functionality that, we allow only to change the transformation of the view (which Teiid already does) which covers all the cases.
> add/remove schema elements
> --------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-4021) MSSQL Pagination
by Mark Tawk (JIRA)
[ https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-4021:
----------------------------------
But I still believe that it should be managed at teiid level since it is a case that may be encountered when connecting to multiple MSSQL DBs of different versions.
> MSSQL Pagination
> ----------------
>
> Key: TEIID-4021
> URL: https://issues.jboss.org/browse/TEIID-4021
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> I'm using Teiid 8.11.3 with mssql translator.
> I have a huge table over sql server 2008 on which i'm applying pagination.
> I noticed slowliness in the query execution over this table at each time I increase the pagination.
> I monitored the JDBC queries execute by teiid and found out that it is using top n according to the limit used into the query.
> For example:
> in teiid : Select * from mytable LIMIT 90 , 10
> is translated in JDBC: select top 100 from mytable
> Since my table contains millions of records, when fetching the last page, the executed jdbc query is retrieving the whole table top n, to return in result the last 10 records. And the execution is taking too much time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-4021) MSSQL Pagination
by Mark Tawk (JIRA)
[ https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-4021:
----------------------------------
I have manually assigned the MSSQL execution factory to the lowest MSSQL version and it works.
> MSSQL Pagination
> ----------------
>
> Key: TEIID-4021
> URL: https://issues.jboss.org/browse/TEIID-4021
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> I'm using Teiid 8.11.3 with mssql translator.
> I have a huge table over sql server 2008 on which i'm applying pagination.
> I noticed slowliness in the query execution over this table at each time I increase the pagination.
> I monitored the JDBC queries execute by teiid and found out that it is using top n according to the limit used into the query.
> For example:
> in teiid : Select * from mytable LIMIT 90 , 10
> is translated in JDBC: select top 100 from mytable
> Since my table contains millions of records, when fetching the last page, the executed jdbc query is retrieving the whole table top n, to return in result the last 10 records. And the execution is taking too much time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months