-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Rest only High Level APIs completeness #47678
Comments
Pinging @elastic/es-core-features (:Core/Features/Java High Level REST Client) |
Do you plan to complete those legacy RHLC api? @hub-cap |
Hi @hub-cap, I am a beginner, can I work on this? |
@qianyuxiang01 I do not plan to personally complete these. I welcome community submissions. @har-vy YES U CAN! :D Just pick one, maybe delete alias (the payload on the response is likely smaller so its easier to deal with). Feel free to post up a WIP and ask questions. |
Hi, @har-vy do you take a look? I can manage to do this one. |
@Deivids sure, I would probably have to pass this on. |
The delete alias call is a rest only API call, but should still be added to the rest client. This commit adds it as well as relevant tests. Ref elastic#47678
Hi, anyone on this right now. I was thinking picking it up if possible |
I have done the delete alias. You can feel free to choose one of the API's and tell me so I can put your name next to it. |
Hub-cap thanks for the quick reply. I think I'll go with the source API |
The delete alias call is a rest only API call, but should still be added to the rest client. This commit adds it as well as relevant tests. Ref #47678
Hi hub-cap, I am having issue build the source code. I am trying to build it on ubuntu 18.04. Doesn't seem like java12 exist for ubuntu 18.04. I tried to build with java13 but that did not work either. Do you know any orkaround for this? I apologize if this is not the right place to post the question. |
Hi, is anyone doing get upgrade? If not I can take it! |
The delete alias call is a rest only API call, but should still be added to the rest client. This commit adds it as well as relevant tests. Ref #47678
@mohamadLy see https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#contributing-to-the-elasticsearch-codebase @andrewjohnson2 I can mark you down if you like. |
Thanks! I am new to the project and trying to understand some things. To clarify, there is a REST API that exposes get upgrade and I need to implement get upgrade in the high level REST client? Where in the codebase is it currently implemented? Thanks |
@andrewjohnson2 I am pretty new to this project also, trying to implement get source. Been doing some investigation on how to go about it. This is the path to the source code where you need to make your changes |
hey guys. first time contributor here, what API would who like me to try and tackle? @hub-cap |
I did some more research and found this: |
So, these are tricky APIs since they are REST only. This means they may not have a specific transport action associated w/ them. The best way to find it is what @andrewjohnson2 has pointed out, which is to find the URI of the action in question, You are right @andrewjohnson2 that this will be removed in the future, but it still exists today, so its still a valid use case for the client. |
@hrealinho you can choose one of the APIs that is not taken above |
@hub-cap thanks so much! For get upgrade specifically, will the implementation be similar in nature to the delete alias implementation? Such as editing similar files and such? If not do you have any references that could layout what needs to happen in general to implement these APIs? Thanks! |
yes @andrewjohnson2 you should be able to use that as a guide. |
Backport to 7.x branch of #50885. Relates to #47678 Co-authored-by: Maxim <[email protected]>
@martijnvg thanks a lot for the help with the tasks. It were my first PRs ever to opensource projects! |
@timoninmaxim You're welcome and thank you for picking up these tasks! |
Is get grok patterns API still available to start working on it? |
It is available if you want ti pick it |
Thanks! I will start working on it then. |
Hi,
However, it is running forever. Here are additional details about my environment: |
What does "forever" mean exactly? Is the build running, but slowly? Or has it stalled completely (and if so, where)? |
Right! So, it has been running for about 2 hours now.
It has stalled at this line I put the logs at a google doc here: |
Aha! It's not actually stalled, it's running and waiting for you to do stuff. I'll open an issue to clarify the CONTRIBUTING instructions - it's definitely not clear from that doc or from the build output that it's at the point where you can actually connect. At this point you can just connect via curl (in a different terminal session) with
|
@tvernum Thanks a lot! It means I was waiting for nothing ><
Excellent idea! I got the response! yay! |
I have started working on the get grok patterns (GET /_ingest/processor/grok) API call to include it in the client.
|
@Priya-Raut are you still working on the solution? |
* Deprecates _upgrade API Ref elastic#47678 * Move deprecation flags to path section. Add deprecation warning tests for _upgrade API. Ref elastic#47678
Hi @hub-cap . Is this issue still open? I would like to work on this issue. |
The Java Rest High Level Client has been deprecated (and removed) in later versions of Elasticsearch, in favor of the official Elasticsearch Java Client — https://github.com/elastic/elasticsearch-java I'm going to close this issue since it is no longer needed. |
There are a number of API that are exposed via REST but not via the Transport Client. They don't necessarily have to be implemented if the goal is feature parity with the Transport Client, yet we should probably have a look at why they were not added to the Transport Client and whether it makes sense to add their support to the high-level REST Client or not. I don't think it makes sense to add support for cat API and ingest processor grok, hence I took them out already.
- [ ] get upgrade (@timoninmaxim)taken from #27205
The text was updated successfully, but these errors were encountered: