2013
DOI: 10.1109/mcse.2013.42
|View full text |Cite
|
Sign up to set email alerts
|

Collaborative Science Workflows in SQL

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2014
2014
2022
2022

Publication Types

Select...
3
1
1

Relationship

2
3

Authors

Journals

citations
Cited by 8 publications
(6 citation statements)
references
References 5 publications
0
6
0
Order By: Relevance
“…Based on our experience with SQLShare [3], we believe that science users can write data analysis tasks in SQL. We expect Datalog's declarative style to have similar appeal, especially for recursive queries.…”
Section: Supported Query Languagesmentioning
confidence: 99%
See 1 more Smart Citation
“…Based on our experience with SQLShare [3], we believe that science users can write data analysis tasks in SQL. We expect Datalog's declarative style to have similar appeal, especially for recursive queries.…”
Section: Supported Query Languagesmentioning
confidence: 99%
“…Myria strikes a balance between these extremes: we adopt a core programming model that extends relational algebra with iteration that affords rich, iteration-aware optimization without sacrificing expressive power. Guided by prior experience in delivering databaseas-a-service capabilities to scientists [3], we aim to support both "users" and "algorithm designers" with a common set of web-based interfaces, languages, and APIs that scale gracefully from simple SPJ queries to advanced application-specific analytics tasks. Like Hyracks, we emphasize the use of core parallel query processing concepts as a first-class concern, but we place less emphasis on supporting legacy code written for Hadoop or Pregel and more emphasis on empowering non-specialists, especially scientists.…”
Section: Introductionmentioning
confidence: 99%
“…All three languages are compiled to the same intermediate representation based on an extension of RA+While, then optimized to produce a parallel physical plan for execution on a cluster. Based on our experience with SQLShare [9] (described below), we know that science users can and will write data analysis tasks in declarative languages, but we seek new language features to capture a greater proportion of their tasks. Myria's execution layer, MyriaX, adopts state-of-the-art system design principles: it uses a pipelined, possibly cyclic graph of dataflow operators that make efficient use of I/O and memory, and it has built-in support for asynchronous evaluation of recursive queries.…”
Section: Big Data Systemsmentioning
confidence: 99%
“…The SQLShare experiment has been remarkably successful in demonstrating the utility of databases in new contexts; it currently has hundreds of science users who have uploaded several thousand datasets of varying size and complexity and issued tens of thousands of hand-written SQL queries. We have seen collections of scripts written in R and Python replaced with a handful of SQL queries, simplifying collaborative analysis to the exchange of links into SQLShare [9]. We have seen SQLShare used to facilitate open data and complexity hiding: at least one public dataset is a view that joins 50 distinct tables.…”
Section: User-facing Toolsmentioning
confidence: 99%
“…Federated databases provide the ability to give users the feel of a data warehouse without physically moving data into a central repository [9]. As an example of a federated database, consider Myria [10,11], a distributed database that uses SQL or MyriaL as the language all of which was developed at the University of Washington. One of the challenges in database federation has been in developing a programming API that can be used to interact with the ever-increasing variety of databases and storage engines [12].…”
Section: Introductionmentioning
confidence: 99%