Superseded by use-dataguide merge proposal.
--
https://code.launchpad.net/~zorba-coders/zorba/dataguide/+merge/173026
Your team Zorba Coders is subscribed to branch lp:zorba.
--
Mailing list: https://launchpad.net/~zorba-coders
Post to : zorba-coders@lists.launchpad.net
Unsubscribe :
I've done some additional testing, and these are the results:
For the xray query, the largest that we have in the testsuite, compilation time
with --compile-only is pretty much the same with and without the dataguide
computaiton, at around ~0.08 sec.
With a specially constructed query that
DataGuides serve as dynamic schemas, generated from the database. What we
generate is a
schema from the query.
Still, it is a data schema, not a query schema. The one in the paper would be a
Database DataGuide and ours would be Query DataGuide. I would agree to change
it to
- I find the name dataguide misleading because it's a guide on the query and
not on the data. Maybe QueryPruneGuide would be more meaningful
The query itself is not pruned, the data is. I think dataguide is the
established term -- see for example this paper:
- I find the name dataguide misleading because it's a guide on the query and
not on the data. Maybe QueryPruneGuide would be more meaningful
The query itself is not pruned, the data is. I think dataguide is the
established term -- see for example this paper:
Review: Approve
--
https://code.launchpad.net/~zorba-coders/zorba/dataguide/+merge/173026
Your team Zorba Coders is subscribed to branch lp:zorba.
--
Mailing list: https://launchpad.net/~zorba-coders
Post to : zorba-coders@lists.launchpad.net
Unsubscribe :
Review: Needs Fixing
- I find the name dataguide misleading because it's a guide on the query and
not on the data. Maybe QueryPruneGuide would be more meaningful
- Can the user also use the zann_explores_json annotation?
- Why is the dataguide parameter on the Store's getCollection() function?
7 matches
Mail list logo
