[JBoss JIRA] (TEIID-4810) Translator Caching
by Van Halbert (JIRA)
Van Halbert created TEIID-4810:
----------------------------------
Summary: Translator Caching
Key: TEIID-4810
URL: https://issues.jboss.org/browse/TEIID-4810
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors, Query Engine
Affects Versions: 9.3
Reporter: Van Halbert
Assignee: Steven Hawkins
we also have a whole different level of caching for custom translators
we could expand on that
we could cache on any source query
that’s not something we’ve talked about putting any higher level UI around
this would be a development and documentation effort
this is different than the whole model materialisation
the difference is that this is at a source query level
vs when you are using cache hints and extension metadata
we don’t have anything for the design-time user
that’s another feature set around caching that we could put some exposure on it
otherwise it’s not really exposed
the idea there is that if you want to do some higher level caching
you can build that into your models or your user query
we could turn it on and off without having to use a custom translator
MMX had a feature like that but it was convoluted because it was mixed up with the user level query caching and they had to be enabled together
Attachments
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4672) Sheet with header becomes invalid
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4672?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4672:
---------------------------------------
Since it will take several days of coding effort to address this issue, the initial resolution will be to just document the situation and defer changes until there is a customer/community need.
> Sheet with header becomes invalid
> ---------------------------------
>
> Key: TEIID-4672
> URL: https://issues.jboss.org/browse/TEIID-4672
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> With a delete, such as a delete all from TEIID-4666, that removes all data rows subsequent select/delete/update queries do not function correctly because google will now treat the header as a data row.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4557) Enable memory management at the query level
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4557?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4557:
---------------------------------------
As mentioned in the initial comment, we now have single resource utilization limits with TEIID-2465 - those could be tightened if desired.
So with this issue I will look at query and session consumption. If there is anymore feedback on exactly what aspect of memory or control is desired, that would be good to have.
> Enable memory management at the query level
> -------------------------------------------
>
> Key: TEIID-4557
> URL: https://issues.jboss.org/browse/TEIID-4557
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> Allows managing (and limiting if needed) the memory consumed by the execution of a particular view. Maybe this can be done through a max. memory and swapping settings on the view.
> Would it also be possible to set a global memory limit for the execution of any query in the server or in a particular VDB. This provides a simple and general setting to guarantee no query can monopolize server resources
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4557) Enable memory management at the query level
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4557?page=com.atlassian.jira.plugin... ]
Work on TEIID-4557 started by Steven Hawkins.
---------------------------------------------
> Enable memory management at the query level
> -------------------------------------------
>
> Key: TEIID-4557
> URL: https://issues.jboss.org/browse/TEIID-4557
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> Allows managing (and limiting if needed) the memory consumed by the execution of a particular view. Maybe this can be done through a max. memory and swapping settings on the view.
> Would it also be possible to set a global memory limit for the execution of any query in the server or in a particular VDB. This provides a simple and general setting to guarantee no query can monopolize server resources
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-2465) Add additional size limitations
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2465?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2465.
-----------------------------------
Resolution: Done
Added limits to an individual buffermanager filestore (which primarily backs server side lobs), and a single table/tuplebuffer based upon existing settings - so that new explicit settings are not yet needed.
> Add additional size limitations
> -------------------------------
>
> Key: TEIID-2465
> URL: https://issues.jboss.org/browse/TEIID-2465
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> We should introduce a limit to lob (which is currently only correct for up to 2 gigs) and single tuplebuffer results in storage as to prevent too much resource consumption from a single use.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years