On Wed, Jan 27, 2010 at 4:10 AM, Luke <[email protected]> wrote: > Dump table is actually a special case of map job, I'm not sure that it > should be part of the client API. Rather it should be a separate > utility class (a la the LoadData* classes) in the library. The same is > true for the "restore" feature. >
DUMP TABLE is going to be part of HQL, so that's why I was planning to make it part of the API. Also, the output is in the same format as SELECT, so the restore will be done with LOAD DATA INFILE. > DumpSpec seems too limiting, why not just use ScanSpec? Initially you > can limit the ScanSpec to be full table only (empty intervals) and > enhance later on using the get_scan_splits API. > Good point, if it's a separate API, there's no reason I can't use ScanSpec and throw exceptions for unsupported predicates. - Doug -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en.
