On Wed, Jan 27, 2010 at 12:13 PM, Luke <[email protected]> wrote: > On Wed, Jan 27, 2010 at 7:04 AM, Doug Judd <[email protected]> wrote: > > 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. > > Well, "load data infile" is not part of the API. I don't think it > belongs there either. People can always access HQL through the HQL > interpreter (available via the Thrift API as well). >
Sounds reasonable. We can leave it out of the API for now. As long as people can script backups in HQL, that's the important thing. If there is demand for the DUMP TABLE feature through the API in the future, we can always add it. - 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.
