search

OrchardCMS / OrchardCore

Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework.
https://orchardcore.net
BSD 3-Clause "New" or "Revised" License
7.45k stars 2.41k forks source link

ElasticSearch Query Result not displaying anymore #16933

Closed Skrypt closed 3 weeks ago

Skrypt commented 4 weeks ago

image

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

@MikeAlhayek

MikeAlhayek commented 4 weeks ago

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 commented 3 weeks ago

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 commented 3 weeks ago

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

Piedone commented 3 weeks ago

Might be related that someone sees the same with Lucene.

PBMikeW commented 3 weeks ago

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

image

Skrypt commented 3 weeks ago

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

PBMikeW commented 3 weeks ago

I tested unticking store source and as per your screenshot you get result numbers but no actual results. The way you wrote image led me to believe this was intentional.

Piedone commented 3 weeks ago

Are we talking about this?

image

Yeah, this should definitely be ticked.

PBMikeW commented 3 weeks ago

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 commented 3 weeks ago

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 commented 3 weeks ago

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

MikeAlhayek commented 3 weeks ago

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