1

Hi,

I had a few ES queries, and when I upgraded to v4.0.0-beta+b3690 (Great, except my bug!), those queries stopped returning new data, although there’s new data in Kibana. I’m a bit stumped, is Redash caching…?

Alternatively, I don’t mind downgrading back to v3, but I haven’t been too successful in that either. Any documentation on downgrading?

Thanks.

2

If you manually execute the query, does it return with any data?

3

Thanks for the quick reply.

If I CURL the ES endpoint directly, the data is as I expect. In Redash, the same query is showing out of date data (since before I upgraded), even after refreshing. The same old data is returned if I create a NEW query, with the same query string. Basically, Redash is out of date, everywhere else is up to date.

4

While Redash does cache query results, when you execute the query it skips the cache. To make sure it’s not a caching issue in Redash, you can slightly change the query text to change its signature.

Can you try this?

5

Sure,

{
  "query": {
    "query_string": {
      "query": "name:LongName"
    }
  }
}

to

{
  "query": {
      "query_string": {
          "query": "name:LongNa*"
      }
  }
}

Same result…