SQL query result analysis SQL Debugging tool

1. Nautilus
Understanding query results origins
Owner : TZOMPANAKI AIKATERINI
2%

2. Nautilus
• SQL Query development tool
• Why do I receive this tuple ?
• Why don’t I receive this tuple ?
• How to get the awaited results ?
• Started 2009
• Under development
2

3. Code location
• Main project :
https://subversion.renater.fr/nautilus/trunk
Nautilus core + Why and Why Not algorithms
• New Query based explanation algorithms (Why Not Questions)
Stored in Gforge, conseil project
3

4. Why Not algorithms
• TedNaive : Full coverage – Time consuming
https://gforge.inria.fr/scm/viewvc.php/trunk/TedNaive/?root=conseil
• TedRevised : Important coverage – Improved execution time
https://gforge.inria.fr/scm/viewvc.php/trunk/TedRevised/?root=conseil
• NedExplain : Partial coverage – Faster
RIP, goodnight sweet prince.
4

5. Code specs
• Java (as an eclipse Plugin)
• 28K lines of code
• 230 classes
5

6. People involved
6
• Past contributors :
• Melanie Herschel
• Abhishek Choudhari (Summer intern 2012, INRIA)
• Hanno Eichelberger (Engineer, U Tübingen)
• Mathilde Verrier (Summer intern 2013, U Paris Sud)
• Current contributor
• Katerina Tzompanaki
• Alexandre Constantin (Engineer, CNRS) (valorisation-cleaning)

7. Architecture
7

8. Explanation manager Workflow
8
GUI
SQL Query
Database conf
Algorithm type
Tuple
SQL Parser
Debugging
scenario
DB
SQL Query
Query object
Artemis Why-Not NedExplain
TedExplain Conquer Conseil
Explanation Graph
Provenance
Why Algorithm Why Not Algorithm

9. Technical Dependencies
• Eclipse (bundled as a plugin)
• Postgres 9.1
• ZQL (java sql parser)
• db2jcc
• jfreechart-1.0.13
• jcommon-1.0.16
• jgraph
• swt
• swtgraphics2d
9

10. TODO
TedNaive:
• Implement TedRevised improving execution speed
Nautilus:
• Redo NedExplain algorithm
• Implement the query fixing functionality
10

11. Known Bugs
- Database connection is not closed when finishing a query analysis
11

12. Fin.
12

13. Paper
13
http://openproceedings.org/EDBT/2014/paper_204.pdf