Difference between revisions of "PrismDemo"
From Schema Evolution
Line 2: | Line 2: | ||
''Please notice that this software is currently under development, and not officially released yet. | ''Please notice that this software is currently under development, and not officially released yet. | ||
'' | '' | ||
− | Contact Carlo Curino at carlo@curino.us for questions or suggestions. | + | |
+ | Contact Carlo Curino at mailto:carlo@curino.us for questions or suggestions. | ||
== Limitations of the Current Demo == | == Limitations of the Current Demo == |
Revision as of 23:10, 8 May 2008
The on-line Demo of Prism is available at http://yellowstone.cs.ucla.edu:8180/Prism . This is an AJAX front-end while the backend is a Java service (running on tomcat) and connecting to a MySQL backend. Please notice that this software is currently under development, and not officially released yet.
Contact Carlo Curino at mailto:carlo@curino.us for questions or suggestions.
Contents |
Limitations of the Current Demo
- The default schema you will be testing doesn't contains any integrity constraints, thus some of the System optimizations are not accessible at the moment.
- The SQL Parser accepted a limited syntax with explicit aliases specified, and no aggregates
- The interface still has some glitch and session management issue (reset cookies in the browser and reload).
- The interface doesn't warn (yet) before removing or editing SMOs (also if cascade actions are involved).
Suggested Test
Configuration:
- Select the Configuration Tab
- Click Load Schema, leaving the configuration parameters to the default (MediaWiki Schema 48)
SMO-Design:
- Select SMO-Design Tab
- Try to input the following SMO: DECOMPOSE TABLE objectcache INTO ob1(keyname, value), ob2(keyname,exptime);
- Add the smo to the working set
- Click on Show Resulting Schema to visualize the resulting schema
- Add the following SMO: COPY TABLE blobs INTO b2;
- Add the following SMO: DROP TABLE archive; (notice the various feedback on information preservation and redundancy)
- Add the following SMO: DROP TABLE blobs;
- Add the following SMO: DROP TABLE b2;
Inverse-Design:
- Select Inverse-Design Tab
- Observe the inverses computed by the system
- On the right hand-side the system computes query "support" (there are 3 queries at the moment in the system), click on the buttons to see failing query
- Click on "show supported schema buttons" to see the supported schema.
- Edit SMO 48:4-48:3 and substitute it with a NOP; (other SMO are modified accordingly!)
- Visualize schema supported at version 48:0
Validation:
- Select Validation Tab
- The DEDs forward and backward are shown (scroll to skip initial type and schema definitions)
- Input the query SELECT o.exptime,o.keyname,o.value FROM objectcache o;
Deployment:
- Select Deployment Tab
- Observe SQL views (scroll to objectcache table)
- Observe SQL data migration script