For Appium-Java client 8.0.2 is it necessary to use appium node 2.0 Beta ?
As I am not able to do few of the feature on 1.X.X appium server for example programmatically running the server , taking out adb logs etc. Can anybody tell ?
check my answer here: No route found for /status
java client 8 and above are compatible with appium 2 features so it is reasonable to upgrade your appium server as well. but, I think you should be able to do the same thing (or at least most of them) with those versions as well.
@GAGANDEEP_SINGH why don’t you want to upgrade to appium 2 ?
Personally, I can tell you that I was a bit afraid of this step (upgrading) since it is a “beta” version but, after researching and getting some answer from appium guys I can tell you that it works great! so, if you have the same concerns regarding appium 2, give it a try 
I am getting this while taking logs from driver.manage().logs().get(“logcat”) , So I think it is not compatible with 1.X.X version yes on beta 2.0 version it is working but I cant upgrade organization framework on beta version.
Please see the logs what I am getting
2022-07-28 04:28:59:382 - [HTTP] --> POST /wd/hub/session/b93b7f9f-8d88-430e-b1be-49bd8ae463b2/se/log
2022-07-28 04:28:59:382 - [HTTP] {“type”:“logcat”}
2022-07-28 04:28:59:384 - [W3C (b93b7f9f)] Driver proxy active, passing request on via HTTP proxy
2022-07-28 04:28:59:385 - [debug] [WD Proxy] Matched ‘/wd/hub/session/b93b7f9f-8d88-430e-b1be-49bd8ae463b2/se/log’ to command name ‘getLog’
2022-07-28 04:28:59:385 - [debug] [WD Proxy] Proxying [POST /wd/hub/session/b93b7f9f-8d88-430e-b1be-49bd8ae463b2/se/log] to [POST http://127.0.0.1:35842/wd/hub/session/8e55de6b-3895-47e4-8995-f5be7352acfb/se/log] with body: {“type”:“logcat”}
2022-07-28 04:28:59:407 - [WD Proxy] Got response with status 404: {“sessionId”:null,“value”:{“error”:“unknown command”,“message”:“The requested resource could not be found, or a request was received using an HTTP method that is not supported by the mapped resource”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.UnknownCommandException: The requested resource could not be found, or a request was received using an HTTP method that is not supported by the mapped resource\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:75)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:345)\n\tat io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandler…
2022-07-28 04:28:59:434 - [debug] [W3C] Matched W3C error code ‘unknown command’ to UnknownCommandError
2022-07-28 04:28:59:434 - [HTTP] <-- POST /wd/hub/session/b93b7f9f-8d88-430e-b1be-49bd8ae463b2/se/log 404 53 ms - 3529