You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to compare the olivere/elastic to this repo, after some googling, I found this reply:
Very nice, I totally agree with Alex, for the long term, it's better to go with the official repo, which is this one. However, after trying out the examples, I found the documents EXTREMELY UNHELPFUL. Because the docs are like this:
So I have to switch to olivere's repo, because it works very well. I used his repo (whatever the version it was) couple of years ago for a project, it was also amazing.
However, like olivere said himself: "In the long run, you're probably better off with the official driver".
But if this driver is like this, all the necessary documents are missing, and if olivere doesn't continue to update his repo, all the golang users should write our own code to use elasticsearch?
Some clarity on the plans you guys have for this repo would be great.
** Also I have to be clear, I'm not complaining, at the end of the day, I believe you guys must have other things to worry about
The text was updated successfully, but these errors were encountered:
Hi guys,
I have a question:
What is this repo about??
I was trying to compare the olivere/elastic to this repo, after some googling, I found this reply:
Very nice, I totally agree with Alex, for the long term, it's better to go with the official repo, which is this one. However, after trying out the examples, I found the documents EXTREMELY UNHELPFUL. Because the docs are like this:
So I have to switch to olivere's repo, because it works very well. I used his repo (whatever the version it was) couple of years ago for a project, it was also amazing.
However, like olivere said himself: "In the long run, you're probably better off with the official driver".
But if this driver is like this, all the necessary documents are missing, and if olivere doesn't continue to update his repo, all the golang users should write our own code to use elasticsearch?
Some clarity on the plans you guys have for this repo would be great.
** Also I have to be clear, I'm not complaining, at the end of the day, I believe you guys must have other things to worry about
The text was updated successfully, but these errors were encountered: