This is similar to what I am
Jun 25, 2012
This is similar to what I am looking for, but I have no desire for the export connector to be used as a means to retrieve data. We are writing state to a table and syncing table state in memory with a semi-realtime application. We would like to keep the table in VoltDB for other queries; however, polling the database for changes is very costly when we have many subscribers, but we may be able to write a workaround using these export features. Do you know of any problems if we just save the entries back into another VoltDB table after sending them off for syncing?
Seems like the proper way to do this right now is
[ VoltDB ] <- Data -> [ Exports Connector ] <- Data for Storage -> [ VoltDB ]
Where the Exports connector sends a broadcast to all the clients we wish to notify of changes.
Could work that way too, just
Jun 26, 2012
Could work that way too, just felt it would be safer if the exports table actually had a real backing store rather than the in-memory caches. Export-only tables are an option that we have not fully investigated after seeing this.
May 24, 2013
Yes we can updated multiple table with the help of the stored procedure, but while updating each time the trigger will be fired.