What would be the plan? 5.x is EOL. And 6.x introduces new concepts and remove some deprecated things from 5.x. I managed to make it (kind of) work with 5.x but then, I found out about some removed features in 6.x. (parent/child are now joins, one document type per index, etc.) There is also the migration path to consider. Should we tell people to start from scratch? I'm not sure how it would be possible to migrate existing data without reindexing everything. But I'm not an ES expert either. Mathieu On Tue, Dec 10, 2019 at 8:32 PM Trinh Nguyen <dangtrinhnt@gmail.com> wrote:

Hi Mathieu,

We just found a bug and I'm trying to fix it. We do have a plan to support a later version like 6.x or 7.x but It's become a little bit complicated when I just changed job a couple of months ago. If you or someone can give me a hand, it would be much appreciated.

Bests,

On Wed, Dec 11, 2019 at 3:35 AM Mathieu Gagné <mgagne@calavera.ca> wrote:

...

Hi,

I'm reading the documentation for Searchlight and it's recommending ElasticSearch 5.x: https://docs.openstack.org/searchlight/latest/install/elasticsearch.html

I installed and tried to use Elasticsearch 5 and it doesn't work. The queries sent by Searchlight aren't accepted by Elasticsearch. For examples:

When listing facets: TransportError(400, u'parsing_exception', u'[terms] failed to parse field [size]'): RequestError: TransportError(400, u'parsing_exception', u'[terms] failed to parse field [size]')

When searching for images: No registered plugin for type owner: Exception: No registered plugin for type owner

Is there any work in progress to add support for Elasticsearch 5? In fact, Elasticsearch 5 is EOL. Are there plans to support later versions?

Thanks

-- Mathieu

-- Trinh Nguyen www.edlab.xyz

I don't mind reindexing from scratch. However my concern is the following: If people are already running Searchlight, they will be running ES 1.x or 2.x. (as ES 5.x and latest aren't supported atm by Searchlight) If we plan on updating Searchlight to support the latest supported ES versions, should we be concerned with the data migration for those existing users? If not, this could greatly speed up development as we wouldn't have to consider any form of backward compatibility or migration path. Also which versions should be supported? Would 6.x be enough? Should 7.x be targeted? Mathieu On Tue, Dec 17, 2019 at 8:06 PM Trinh Nguyen <dangtrinhnt@gmail.com> wrote:

Hi Mathieu.

Thanks for the effort. What you're saying is true. 5.x is EOL and may not be worth fixing. Adding support for 6.x could be a better option. Let me do some research on how to migrate data from 5.x to 6.x and let you know.

Thanks,

On Wed, Dec 18, 2019 at 6:38 AM Mathieu Gagné <mgagne@calavera.ca> wrote:

...

What would be the plan?

5.x is EOL. And 6.x introduces new concepts and remove some deprecated things from 5.x. I managed to make it (kind of) work with 5.x but then, I found out about some removed features in 6.x. (parent/child are now joins, one document type per index, etc.)

There is also the migration path to consider. Should we tell people to start from scratch? I'm not sure how it would be possible to migrate existing data without reindexing everything. But I'm not an ES expert either.

Mathieu

On Tue, Dec 10, 2019 at 8:32 PM Trinh Nguyen <dangtrinhnt@gmail.com> wrote:

...

Hi Mathieu,

We just found a bug and I'm trying to fix it. We do have a plan to support a later version like 6.x or 7.x but It's become a little bit complicated when I just changed job a couple of months ago. If you or someone can give me a hand, it would be much appreciated.

Bests,

On Wed, Dec 11, 2019 at 3:35 AM Mathieu Gagné <mgagne@calavera.ca> wrote:

...

Hi,

I'm reading the documentation for Searchlight and it's recommending ElasticSearch 5.x: https://docs.openstack.org/searchlight/latest/install/elasticsearch.html

I installed and tried to use Elasticsearch 5 and it doesn't work. The queries sent by Searchlight aren't accepted by Elasticsearch. For examples:

When listing facets: TransportError(400, u'parsing_exception', u'[terms] failed to parse field [size]'): RequestError: TransportError(400, u'parsing_exception', u'[terms] failed to parse field [size]')

When searching for images: No registered plugin for type owner: Exception: No registered plugin for type owner

Is there any work in progress to add support for Elasticsearch 5? In fact, Elasticsearch 5 is EOL. Are there plans to support later versions?

Thanks

-- Mathieu

-- Trinh Nguyen www.edlab.xyz

-- Trinh Nguyen www.edlab.xyz