New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Elasticsearch 5.x #1461
Conversation
This PR addresses #1383 |
Hi! I also work on elasticsearch 5 support for haystack. My project lies in this repo. What do you say if I offer you to work together at this project? Or at least borrow the idea. |
I just merged #1460 so it might be good to see how small this request can be |
@ElSaico travis has whitelisted elasticsearch 5.x repo. We can update/simplify travis.yml ;) |
@Alkalit just managed to fix the last of the issues, but thank you for your offer! @acdha the major source of shared code is |
@ElSaico That seems reasonable – I've been meaning to take a look at that in general and seeing how much we could refactor into shared utilities or methods on Things like https://github.com/django-haystack/django-haystack/blob/master/haystack/backends/elasticsearch_backend.py#L309 or django-haystack/haystack/backends/elasticsearch_backend.py Lines 413 to 420 in f8921b6
|
What is the timeframe for merging this into a stable release? |
We have been using ES5 with haystack in our production for about 20 days now. For our needs it seems reasonably stable. |
@seocam thanks - I can do a release soon but since I don't use it I'm not entirely comfortable saying it's been well tested |
@acdha I totally understand! Even I would be a lot more comfortable with more people using it from the branch before having a new version out. |
Maybe I'll merge it and publish a -pre release to make it easier for people to test |
@acdha Any update on pre release for ES 5.X??. |
@acdha any update on pre release for ES 5.x ! |
@acdha Please. |
@SalahAdDin typo? I don't have anything to do with django-haystack |
ES 5.x support branch doesn't work for me.
Sorry, false issue. I included wrong class in settings.py. Included Elasticsearch5SearchBackend instead of Elasticsearch5SearchEngine. Well done! |
Is there anything holding it to be merged yet? |
@alanjds More test results from people using ES would be helpful |
@acdha I see. Looks like I would have the 1st cobaia project using this... But the good news is that nobody said "It have a problem. Be never merged. Beware and run to the hills!". Thanks. |
@alanjds the time taken to merge it isn't high but I don't really have that much time for an in-depth review. If you have some positive test results that'd save me the time there. |
Could it be possible to merge it? |
@millerf If you have time to work on this, test results are appreciated |
I have very little experience with all that ES, so I am a bit perplexed... |
Merge pull request #1369 from janwin/fix-empty-list-convert
When will this be official? |
ES 5.x got issue while executing Traceback (most recent call last): |
Currently haystack doesn’t support ES 5.x.
…On Fri, 8 Jun 2018 at 15:07 Lokesh Pahal ***@***.***> wrote:
ES 5.x got issue while executing rebuild_index command
Traceback (most recent call last):
File "manage.py", line 15, in
execute_from_command_line(sys.argv)
File
"/var/www/MSDev/env/lib/python3.6/site-packages/django/core/management/
*init*.py", line 371, in execute_from_command_line
utility.execute()
File
"/var/www/MSDev/env/lib/python3.6/site-packages/django/core/management/
*init*.py", line 365, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/var/www/MSDev/env/lib/python3.6/site-packages/django/core/management/base.py",
line 288, in run_from_argv
self.execute(*args, **cmd_options)
File
"/var/www/MSDev/env/lib/python3.6/site-packages/django/core/management/base.py",
line 335, in execute
output = self.handle(*args, **options)
File
"/var/www/MSDev/env/lib/python3.6/site-packages/haystack/management/commands/rebuild_index.py",
line 36, in handle
call_command('clear_index', **options)
File
"/var/www/MSDev/env/lib/python3.6/site-packages/django/core/management/
*init*.py", line 133, in call_command
', '.join(sorted(valid_options)),
TypeError: Unknown option(s) for clear_index command: batchsize, workers.
Valid options are: commit, help, interactive, no_color, nocommit, noinput,
pythonpath, settings, skip_checks, stderr, stdout, traceback, using,
verbosity, version.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1461 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZuKazm_QnoMb3LkKce3x617qYXmXHWlks5t6jDAgaJpZM4LLugB>
.
|
All tests are passing on my project. I will use it on production and tell you results in a few days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working on production system since 72h, no issues.
Thanks for testing - I’ll merge it later today |
This might need a rebase before merge, we are waiting for you @acdha :-) |
Indeed - I didn’t have time for that last week since it was more involved than I thought
|
I merged this in my working branch (see acdha@e366f49) but we still need to fix the GIS code to work with Django 2: https://travis-ci.org/acdha/django-haystack/jobs/393751311#L2309-L2319 |
Rebased and merged with 1fda20e to fix the get_coords calls |
Can this be pushed to pypi? |
Hi, When this will be released? Thanks! |
I get this exception when searching data |
Based on #1460 - will be properly rebased once it's accepted.
So far only two features seem to be failing, according to the test suite:
fielddata
)Any help to solve any of those would be appreciated.