ivan-demchenkov opened a new issue #10735: URL: https://github.com/apache/druid/issues/10735
According to the [docs](https://github.com/apache/druid/blob/master/docs/development/extensions-core/lookups-cached-global.md) the extension uses tsColumn to pull only new values: > The JDBC lookups will poll a database to populate its local cache. If the tsColumn is set it must be able to accept comparisons in the format '2015-01-01 00:00:00'. For example, the following must be valid SQL for the table SELECT * FROM some_lookup_table WHERE timestamp_column > '2015-01-01 00:00:00'. If the tsColumn is set, the caching service will attempt to only poll values that were written after the last sync. If tsColumn is not set, the entire table is pulled every time. But actually, it just checks if any records were modified using the tsColumn and then if so pulls the whole table anyway. See function **getLookupPairs** in the [code](https://github.com/apache/druid/blob/master/extensions-core/lookups-cached-global/src/main/java/org/apache/druid/server/lookup/namespace/JdbcCacheGenerator.java) - it doesn't use the tsColumn at all. Not sure if it's a bug in the documentation or in the extension itself. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org
