[JBoss JIRA] (TEIID-2338) staging table performance
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2338?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2338.
-----------------------------------
Fix Version/s: 8.3
Resolution: Done
Addressed by detecting the need for indexes against explicit staging tables. This works when there are parametrized filters against the staging table with the general assumption that the parameters are coming from input sets.
There is still some need for the Designer issue to cover more complicated scenarios - usage of staging tables in subqueries or in joins without input set criteria (although the latter case could be detected - but was left as a TODO with this issue).
> staging table performance
> -------------------------
>
> Key: TEIID-2338
> URL: https://issues.jboss.org/browse/TEIID-2338
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> Large staging tables should be indexed based upon their usage to improve performance.
> Further usage analysis could limit the size of the initial staging table, but is somewhat complicated - and references can be used in dynamic sql.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-2346) TempTable key and leaf sizing is reversed
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2346:
-------------------------------------
Summary: TempTable key and leaf sizing is reversed
Key: TEIID-2346
URL: https://issues.jboss.org/browse/TEIID-2346
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
The key/leaf sizing is reversed which generally means that the memory reserved will be in greater than what is needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2182:
-------------------------------------
Yes, admin is the only way. I will change the API accordingly.
> Mechanism to hook up event listener into Teiid runtime
> ------------------------------------------------------
>
> Key: TEIID-2182
> URL: https://issues.jboss.org/browse/TEIID-2182
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi, Server
> Affects Versions: 8.1
> Environment: Windows 7 64 bit
> Reporter: Anil Allewar
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization.
> This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application.
> Please see the thread below for the context & details
> https://community.jboss.org/message/756060
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2182:
---------------------------------------
> since there are other ways to get to the context, I thought it was best to leave out of the interface to keep it simple.
The only supported way would be to use an admin connection and get the VDB from there correct? I was just thinking that since we have the VDB available it could be useful in determining next steps before what amounts to a remote call is made.
> I do not think I understand your comment about general event listener. I wanted to avoid adding any new interfaces for same purpose.
We cannot (should not) modify an interface in anything except a major release as it will be a breaking change for any implementers. The other approach would be to use an abstract base class which allows for new methods with only a minor chance to be breaking (if for whatever reason the user choose the same method signature).
> Mechanism to hook up event listener into Teiid runtime
> ------------------------------------------------------
>
> Key: TEIID-2182
> URL: https://issues.jboss.org/browse/TEIID-2182
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi, Server
> Affects Versions: 8.1
> Environment: Windows 7 64 bit
> Reporter: Anil Allewar
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization.
> This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application.
> Please see the thread below for the context & details
> https://community.jboss.org/message/756060
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2182:
-------------------------------------
since there are other ways to get to the context, I thought it was best to leave out of the interface to keep it simple. I was thinking there may be few more events we can expose through this interface like data source add/remove or translator add/remove etc.
I do not think I understand your comment about general event listener. I wanted to avoid adding any new interfaces for same purpose.
> Mechanism to hook up event listener into Teiid runtime
> ------------------------------------------------------
>
> Key: TEIID-2182
> URL: https://issues.jboss.org/browse/TEIID-2182
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi, Server
> Affects Versions: 8.1
> Environment: Windows 7 64 bit
> Reporter: Anil Allewar
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization.
> This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application.
> Please see the thread below for the context & details
> https://community.jboss.org/message/756060
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2182:
---------------------------------------
Is there more context that we should be providing to the listener, for example the VDB object rather than just the name/version. Also at least for non-major releases if we need to add more methods then we would introduce new interfaces rather than requiring the modification of the general EventListener.
> Mechanism to hook up event listener into Teiid runtime
> ------------------------------------------------------
>
> Key: TEIID-2182
> URL: https://issues.jboss.org/browse/TEIID-2182
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi, Server
> Affects Versions: 8.1
> Environment: Windows 7 64 bit
> Reporter: Anil Allewar
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization.
> This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application.
> Please see the thread below for the context & details
> https://community.jboss.org/message/756060
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-1757) Add Support for OData Data Sources
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-1757?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-1757:
--------------------------------
Assignee: Ramesh Reddy
Fix Version/s: 8.3
(was: Open To Community)
Complexity: High
Component/s: Misc. Connectors
Affects: Documentation (Ref Guide, User Guide, etc.),Release Notes
> Add Support for OData Data Sources
> ----------------------------------
>
> Key: TEIID-1757
> URL: https://issues.jboss.org/browse/TEIID-1757
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Ted Jones
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> OData data sources, like SAP Gateway, should be consumable by Teiid. I suggest either a new translator or extending the existing web service translator to enable the OData protocol. A new translator would be cleaner, but since OData uses REST, it may not make sense to to have another translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2182.
---------------------------------
Resolution: Done
Added a new callback interface called "EventListener" in teiid-api project, which can be registered on "EventDistributor". Currently this interface notifies about VDB load/unload and ACTIVE. Other events as needed can be added to the same interface in future if needed. Note, you can add only "inVM" listeners. However, for users who are inclined, they can integrate with other technologies like ESB, JMX or messaging to generate remote event if needed.
User can get access in "EventDistributor" through JNDI look up in AS7 environment and through "getEventDistrubutor" method in the embedded scenario.
> Mechanism to hook up event listener into Teiid runtime
> ------------------------------------------------------
>
> Key: TEIID-2182
> URL: https://issues.jboss.org/browse/TEIID-2182
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi, Server
> Affects Versions: 8.1
> Environment: Windows 7 64 bit
> Reporter: Anil Allewar
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization.
> This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application.
> Please see the thread below for the context & details
> https://community.jboss.org/message/756060
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (TEIID-2338) staging table performance
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2338?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2338:
----------------------------------
Summary: staging table performance (was: common table expression performance)
Description:
Large staging tables should be indexed based upon their usage to improve performance.
Further usage analysis could limit the size of the initial staging table, but is somewhat complicated - and references can be used in dynamic sql.
was:
Large common table expressions should be indexed based upon their usage in the query to improve performance.
Also given that we will now back-off of bad dependent joins, we should be more optimistic with using common tables as dependent joins (which would also reduce the need for an index).
Forum Reference: https://community.jboss.org/message/786894
> staging table performance
> -------------------------
>
> Key: TEIID-2338
> URL: https://issues.jboss.org/browse/TEIID-2338
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> Large staging tables should be indexed based upon their usage to improve performance.
> Further usage analysis could limit the size of the initial staging table, but is somewhat complicated - and references can be used in dynamic sql.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months