br1ghtyang / asterixdb

Automatically exported from code.google.com/p/asterixdb
0 stars 0 forks source link

Need to rethink/fix ASTERIX instance lifecycle #130

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
We need to move, before we ship, to a more "traditional" database 
lifecycle/model.  We should not have an "overwrite the world" flat.  Instead, 
we should have a utility that creates an ASTERIX instance and initializes its 
catalogs (the metadata dataverse) - and then the API should only be able to 
connect to an existina ASTERIX instance and add/drop dataverses and their 
contents from there.  Another utility should make it possible to clean up an 
ASTERIX instance (i.e., to destroy it).

Original issue reported on code.google.com by dtab...@gmail.com on 7 Jun 2012 at 6:30

GoogleCodeExporter commented 8 years ago
To some extent, this issue is related to issue 127.
Currently newUniverse flag in test.properties control the life-cycle of 
existing data.

Original comment by pouria.p...@gmail.com on 10 Aug 2012 at 5:29

GoogleCodeExporter commented 8 years ago
This flag needs to come down off the flagpole... :-)

Original comment by dtab...@gmail.com on 14 Aug 2012 at 5:42

GoogleCodeExporter commented 8 years ago
Pouria, is this implemented completely and code reviewed. If yes please let me 
know and I can verify and mark this issue as verified. Thanks.

Original comment by khfaraaz82 on 16 Oct 2012 at 5:59

GoogleCodeExporter commented 8 years ago
This issue needs design discussion.
Specially after the changes that have been made into the Metadata/Bootstrap 
components in VLDB-Demno Branch.

Original comment by pouria.p...@gmail.com on 19 Nov 2012 at 7:34

GoogleCodeExporter commented 8 years ago
Thanks Pouria, please send an email to Mike and Vinayak and set up a time to 
discuss further action on this issue.

Original comment by khfaraaz82 on 19 Nov 2012 at 8:34

GoogleCodeExporter commented 8 years ago

Original comment by vinay...@gmail.com on 7 Dec 2012 at 7:35

GoogleCodeExporter commented 8 years ago

Original comment by khfaraaz82 on 7 Dec 2012 at 7:43

GoogleCodeExporter commented 8 years ago

Original comment by RamanGro...@gmail.com on 26 Jan 2013 at 3:00

GoogleCodeExporter commented 8 years ago
Fixed via Managix.

Original comment by RamanGro...@gmail.com on 8 Apr 2013 at 11:33