Proceedings of the 2012 ACM SIGMOD International Conference on Management of Data 2012
DOI: 10.1145/2213836.2213966
|View full text |Cite
|
Sign up to set email alerts
|

Adaptive optimizations of recursive queries in teradata

Abstract: Recursive queries were introduced as part of ANSI SQL 99 to support processing of hierarchical data like air flight schedules, bill-of-materials, data cube dimension hierarchies, and ancestordescendant information (e.g. XML data stored in relations). Recently, recursive queries have also found extensive use in web data analysis such as social network and click stream data. Teradata implemented recursive queries in V2R6 using static plans whereby a query is executed in multiple iterations, each iteration corres… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 9 publications
(3 citation statements)
references
References 29 publications
0
3
0
Order By: Relevance
“…The reason is that the cost of 20 relational joins on the large Twitter table exceeds the temporary-memory limits of VoltDB, and time-out the queries on a commercial disk-based RDBMS after 5 hours of execution. Also, as the number of self-joins increases in the Native Relational-Core approach, the relational optimizer may not be able to select the best join algorithm due to inaccurate cardinality estimations of the in- termediate results (see [24] for details). The relational engine is already very efficient in performing filtering predicates.…”
Section: Reachability Queries With Filtering Predicatesmentioning
confidence: 99%
“…The reason is that the cost of 20 relational joins on the large Twitter table exceeds the temporary-memory limits of VoltDB, and time-out the queries on a commercial disk-based RDBMS after 5 hours of execution. Also, as the number of self-joins increases in the Native Relational-Core approach, the relational optimizer may not be able to select the best join algorithm due to inaccurate cardinality estimations of the in- termediate results (see [24] for details). The relational engine is already very efficient in performing filtering predicates.…”
Section: Reachability Queries With Filtering Predicatesmentioning
confidence: 99%
“…On the same principle, query execution is continuously monitored, run-time statistics are collected and the parallelism degree or the partition key choice is dynamically modified. Re-optimization is also applied for recursive queries in [28], where the estimation errors may be propagated to later iterations. The authors proposed two mechanisms.…”
Section: Re-optimizationmentioning
confidence: 99%
“…General purpose large graph management has drawn great research interest [26], [27], [28], [29], [30], [31], [32], [33], [34], [35]. Early work [36] illustrates the challenging issues of large graph management.…”
Section: Related Workmentioning
confidence: 99%