Show HN: X to Elasticsearch Sync

Re:Show HN: X to Elasticsearch Sync by BrentOzar on Saturday November 18, 2017 @11:26AM (#15729591)

I couldn't figure this out in the documentation - how are you keeping the data up to date? Is there some kind of scheduled refresh that pulls all the data from the database periodically, or how are you detecting which rows changed?

In particular, how are you implementing this in, say, the MSSQL importer?

> Adaptors may be able to track changes as they happen in source data. This "tail" capability allows a ABC to stay running and keep the sinks in sync.

[ Parent | on HN ]

Re:Show HN: X to Elasticsearch Sync by TYPE_FASTER on Saturday November 18, 2017 @02:44PM (#15730322)

I’m assuming they’re adding a trigger to the source table.

[ Parent | on HN ]

Re:Show HN: X to Elasticsearch Sync by BrentOzar on Saturday November 18, 2017 @02:55PM (#15730354)

> I’m assuming they’re adding a trigger to the source table.

Their video demo for SQL Server simply points the command line at a connection string, and it then says 2 item(s) indexed. There wasn't a way to pick specific tables.

That means if the trigger method is true, they're adding a trigger by default to every single table in the database. That would be a remarkably bad idea.

[ Parent | on HN ]

Re:Show HN: X to Elasticsearch Sync by Mister_Snuggles on Saturday November 18, 2017 @06:12PM (#15731204)

The PostgreSQL one uses the logical replication feature, perhaps the MSSQL piece does something similar.

[ Parent | on HN ]