Skip to content

Update where_stats after ingest of new data #62

@lossyrob

Description

@lossyrob

I'm running into a situation where a query is logged in the search_wheres table before new data is brought in. This causes queries to miss the newly ingested items, and returning only results from the previous set of partitions. In the case where a query was done before any items are ingested, it will return 0 results as no partitions are logged in search_wheres for that query.

Workaround is to perform a query like

delete from search_wheres  where _where LIKE '%COLLECTIONID%';

where COLLECTIONID is the collection ID for the recently ingested items.

Perhaps some purging of the search_wheres table should be done after a load to avoid mis-cached results? Or turn down the default TTL - as 1 day is a long time to wait for new items to show up.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions