On Wed, Sep 23, 2009 at 10:09 AM, James Henstridge <[email protected]>wrote:
> > I'm not quite sure I understand your problem. > > If you are using a bulk loader tool to insert data into the database > outside of Storm's control, wouldn't you want to retrieve it via > store.get() or store.find()? If you're instantiating a new object, > then Storm will issue an INSERT to add the new row. > > Here is some context: we are using Storm for ETL, and we have code which is used for both direct to database inserts/updates (a normal Storm store), and which is also being reused for high volume bulk inserts for the initial historical data loads. During the bulk insert the objects having Storm properties are being persisted to text files instead of the database. Right now the API is a bit awkward and we want to have it be as consistent as possible to maximize code reuse. For example, the bulk load store needs to understand what to do with ReferenceSet and Reference attributes. -- ZeOmega Open Minds' Open Solutions 3010 Gaylord Parkway, Ste. 210 Frisco TX, 75034 http://www.zeomega.com Brad Allen 214-618-9880 (ext. 8006)
-- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
