[JBoss JIRA] (TEIID-3209) Issues with mat view ttl
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3209?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3209:
-------------------------------------
These are mostly solved with TEIID-3215, TEIID-3212
> Issues with mat view ttl
> ------------------------
>
> Key: TEIID-3209
> URL: https://issues.jboss.org/browse/TEIID-3209
> Project: Teiid
> Issue Type: Bug
> Components: Documentation, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> The docs / code have matview_ttl as required, but the code will also prefer to use the cache hint ttl if it also supplied. I believe the cache hint should not be used in this case.
> Generally there is also: TEIID-2194 which we should probably prefer properties over the cache hint because they are more targeted and can be more easily be manipulated at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 3 months
[JBoss JIRA] (TEIID-3209) Issues with mat view ttl
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3209?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3209:
-------------------------------------
Assignee: Steven Hawkins
> Issues with mat view ttl
> ------------------------
>
> Key: TEIID-3209
> URL: https://issues.jboss.org/browse/TEIID-3209
> Project: Teiid
> Issue Type: Bug
> Components: Documentation, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> The docs / code have matview_ttl as required, but the code will also prefer to use the cache hint ttl if it also supplied. I believe the cache hint should not be used in this case.
> Generally there is also: TEIID-2194 which we should probably prefer properties over the cache hint because they are more targeted and can be more easily be manipulated at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 3 months
[JBoss JIRA] (TEIID-2481) common table (with) push down improvements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2481.
-----------------------------------
Fix Version/s: 8.8
(was: 8.10)
Resolution: Done
Marking as resolved against 8.8, since that is where we allowed mergable view layers. Of the other improvements, the only one that seems like it should be tackled proactively is the inlining when common table expressions are not supported. This is not however a good fit with planning currently as we would most naturally make that decision prior to optimization, which means more than likely there would be multiple references. So I'm resolving for now and we can revisit as needed.
> common table (with) push down improvements
> ------------------------------------------
>
> Key: TEIID-2481
> URL: https://issues.jboss.org/browse/TEIID-2481
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> The general strategy for with pushdown should better handle:
> - a with clause that can be pushed against a source that does not support common table. If a single reference or some other sufficient condition is met then we should just inline the pushdown rather than inhibiting the whole query from pushing down.
> - even if a source supports with pushdown, it may be more performant in some circumstances to inline the common table reference (such as only a single reference). This is complicated slightly by subqueries.
> - alternatively in some situations even if a with clause can be pushed, it may be better to not perform the pushdown -e.g. two separate pushdown accesses to a common table that is expensive to compute (this may need to be hint driven).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 3 months
[JBoss JIRA] (TEIID-3053) Detect when returnable procedure results need to be processed in the procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3053?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3053.
-----------------------------------
Resolution: Done
Added detection of temp table usage and will only process in scope if there are transactional source queries or temp table usage.
> Detect when returnable procedure results need to be processed in the procedure
> ------------------------------------------------------------------------------
>
> Key: TEIID-3053
> URL: https://issues.jboss.org/browse/TEIID-3053
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.9
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> With TEIID-3052 we are now fully processing almost all results in the originating procedure scope whereas before we were effective performing pipelining in that the results were created off of the tuple source on demand.
> With some upfront or processing time detection we could see when the processorplan is relying upon resources from the program scope and if not go ahead and pop/return the results as before. We could also develop a better strategy for dealing with the case when resources are needed.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3053) Detect when returnable procedure results need to be processed in the procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3053?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3053:
----------------------------------
Fix Version/s: 8.10
> Detect when returnable procedure results need to be processed in the procedure
> ------------------------------------------------------------------------------
>
> Key: TEIID-3053
> URL: https://issues.jboss.org/browse/TEIID-3053
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.9
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> With TEIID-3052 we are now fully processing almost all results in the originating procedure scope whereas before we were effective performing pipelining in that the results were created off of the tuple source on demand.
> With some upfront or processing time detection we could see when the processorplan is relying upon resources from the program scope and if not go ahead and pop/return the results as before. We could also develop a better strategy for dealing with the case when resources are needed.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-1544) Add a limit to the number of dependent queries that can be issued.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1544?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-1544.
-----------------------------------
Fix Version/s: (was: 8.10)
Resolution: Out of Date
Effectively resolved with TEIID-2559. The only issue is if the auto dependent join backoff would need to be tweaked via a translator property or some other non-hint mechanism, but that hasn't been seen as an issue yet.
> Add a limit to the number of dependent queries that can be issued.
> ------------------------------------------------------------------
>
> Key: TEIID-1544
> URL: https://issues.jboss.org/browse/TEIID-1544
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
>
> There should be a mechanism to limit the number of dependent join queries generated. Ideally this should apply to both cost and hint based dependent joins.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3216:
----------------------------------
Issue Type: Enhancement (was: Task)
Fix Version/s: 8.10
(was: Open To Community)
The pull request has been committed with some updates. There are a couple of limitations that may need captured - expressions can't be used as update values, like is not supported in update/delete, characters needing url encoding are not supported (but could be a google issue), and not all strings were localized (some of which pre-date this commit). The first two could be addressed with capabilities if needed.
> Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector
> ----------------------------------------------------------------------------
>
> Key: TEIID-3216
> URL: https://issues.jboss.org/browse/TEIID-3216
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Filip Elias
> Assignee: Filip Elias
> Fix For: 8.10
>
>
> Current plan is to use list-based feed of the Google Data API[1].
> There are three known issues:
> performance - to delete/update 100 rows Teiid must generate 100 http requests
> consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't.
> headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet)
> Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers.
> [1] https://developers.google.com/google-apps/spreadsheets/
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months