ElasticSearch Query Result not displaying anymore

[Skrypt]

The ElasticSearch Queries are not showing results anymore. Any reason why?

@MikeAlhayek

[MikeAlhayek]

Not sure. I don't see others reporting this being an issue. Are there any errors in the log file?

I can try to reproduce the issue if you share the exact step to reproduce it.

[Skrypt]

Just pull latest dev branch and install blog recipe then setup ElasticSearch. Create an index and query it with a match all query like it does.

Maybe not reported but that's a regression.

[Piedone]

We have a UI test testing Elasticsearch and it works with 2.0.1 BTW.

[Piedone]

Might be related that someone sees the same with Lucene.

[PBMikeW]

Latest dev and blank site recipe I'm unable to replicate the issue. Did you tick store source data in index?

[Skrypt]

I did not. But it should return results still. Unless something has changed since I wrote it.

[PBMikeW]

I tested unticking store source and as per your screenshot you get result numbers but no actual results. The way you wrote

led me to believe this was intentional.

[Piedone]

Are we talking about this?

Yeah, this should definitely be ticked.

[PBMikeW]

Are we talking about this?
Yeah, this should definitely be ticked.

Yes thats what I'm referring to. Unticking gives the result that Skrypt is seeing and I thought it was intentional.

[Skrypt]

Memory fails. Maybe you guys are right. But else, I'm pretty sure at some point it was working. Source is just the original data stored in the index. Else, just like Lucene works ; it should return results and display them.

[Skrypt]

I'm closing this issue as there is a workaround. I will open a new one if I find something else.

[MikeAlhayek]

I don't use this UI. But I would expect it to return at least the content item id if there is no source