2020
DOI: 10.1007/s00778-020-00633-6
|View full text |Cite
|
Sign up to set email alerts
|

DIFF: a relational interface for large-scale data explanation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
54
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 23 publications
(54 citation statements)
references
References 43 publications
0
54
0
Order By: Relevance
“…For example, expressing the query in Listing 2 using existing SQL clauses (see Figure 3) is much more verbose, requiring a complex sub-query for each (grouping, measure). Prior work have proposed similar succinct abstractions such as GROUPING SETs [17] and CUBE [22] (both widely adopted by most of the databases) and more recently DIFF [6], which share our overall goal that with an extended syntax, complex analytic queries are easier to write and optimize.…”
Section: Syntax and Semanticsmentioning
confidence: 99%
See 2 more Smart Citations
“…For example, expressing the query in Listing 2 using existing SQL clauses (see Figure 3) is much more verbose, requiring a complex sub-query for each (grouping, measure). Prior work have proposed similar succinct abstractions such as GROUPING SETs [17] and CUBE [22] (both widely adopted by most of the databases) and more recently DIFF [6], which share our overall goal that with an extended syntax, complex analytic queries are easier to write and optimize.…”
Section: Syntax and Semanticsmentioning
confidence: 99%
“…In contrast, we provide extensions to traditional query optimization and execution layers of relational databases to support comparative queries like other SQL queries. Similar to our approach, there have been database extensions [38,23,26,33], the most recent being the DIFF operator [6], that support association and frequent pattern mining. While our focus is on aggregate distance measures such as Lp norms (our focus), we share their goal that with an extended syntax, complex analytic queries are easier to write and optimize.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Inference Query Explain [1,33,34,44] Rain [ Generating an explanation (i.e., a predicate) from inference data can certainly help to understand the answer to an inference query. However, an ML pipeline does not only contain the inference data but also the training and source data.…”
Section: Sql Explainmentioning
confidence: 99%
“…Unfortunately, existing SQL explanation approaches [1,33,34,44] are ill-equipped to address this setting (Table 1) because they are based on analysis of the query provenance. Although they can generate a predicate explanation over the inference data, the provenance analysis does not extend across model training nor UDFs, which are prevalent in data science workflows.…”
Section: Sql Explainmentioning
confidence: 99%