How to push the data for Vertica Database ?

[jerald]

Hi,
i'm new bee to vertica database. In Oracle using listener we can push the data from database.

In vertica is there possibility to push the data from database.

[BoMBaY]

Oracle Net Listener is a separate process that runs on the database server computer. It receives incoming client connection requests and manages the traffic of these requests to the database server.

https://docs.oracle.com/cd/E11882_01/ne ... nercfg.htm

I'm not sure what you mean by "push the data from database via listener".

If you mean spool data from Oracle database via sqlplus. For Vertica you can use \o via vsql.

If I miss understand, Can you explain more or show me an example.

[jerald]

Thanks for replying.

I am looking at a design where I run a Java program which listens to vertica database table changes (namely DML statements) and get notifications in my Java program. I have done a similar design for oracle database using "Database Change Listener" and hoping to implement a similar design for vertica database.

Hope this is clear.

[NorbertKrupa]

When you say table changes, do you mean the actual data or the table structure? If the former, then you should use some sort of sequence.

[JimKnicely]

Maybe monitor the v_monitor.query_requests table looking for DML?

Something like this, but maybe a little more robust depending in the requirements...

Code: Select all

select request from v_monitor.query_requests where request ilike 'insert%' or request ilike '%update' or request ilike '%delete' and start_timestamp > [[time last checked]];

[jerald]

This approach will require polling the mentioned table at regular intervals to find out the data changes. What I am looking for is some sort of notification (as close as realtime) in the Java layer, as soon as a record is inserted/updated/deleted. I am trying to figure out, if there is any approach in Vertica database similar to "Database Change Listener" for Oracle.

[JimKnicely]

I am unaware of anything in Vertica that will "automatically" push data to a destination. I'm not sure why you'd ever want that.

Don't forget that Vertica is a analytics database, not an OLTP. How are you updating Vertica? What ever process that is (i.e. an ETL tool) why not have that process also send the inserts, updates and/or deletes to whatever other destination you need?