Update BanyanDB Java Client to 0.5.0

[lujiajing1126]

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
• Update the CHANGES log.

[wu-sheng]

FYI @wankai123

[wu-sheng]

@lujiajing1126 Please fix this #11370 (comment).

The Istio relative e2e are always failure due to GHA issues. I have setup the workflow to skip them.

[wu-sheng]

configuration-vocabulary.md should be updated too.

[wu-sheng]

I have tried rerun, profiling e2e with BanyanDB fails. I am not sure whether it is relative.

[wu-sheng]

@lujiajing1126 It still fails, it seems server side has some issues.

[lujiajing1126]

@lujiajing1126 It still fails, it seems server side has some issues.

Caused by: io.grpc.StatusRuntimeException: UNKNOWN: fail to analyze the query request for measure instance_traffic_minute: mandatory index rule conf:name:"id" op:BINARY_OP_IN value:{str_array:{value:"c3FydA==.1_dGVzdC1pbnN0YW5jZQ=="}}: unsupported condition operation: invalid query message
	at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:271) ~[grpc-stub-1.53.0.jar:1.53.0]
	at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:252) ~[grpc-stub-1.53.0.jar:1.53.0]
	at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:165) ~[grpc-stub-1.53.0.jar:1.53.0]
	at org.apache.skywalking.banyandb.measure.v1.MeasureServiceGrpc$MeasureServiceBlockingStub.query(MeasureServiceGrpc.java:263) ~[banyandb-java-client-0.5.0.jar:0.5.0]
	at org.apache.skywalking.banyandb.v1.client.BanyanDBClient.lambda$query$4(BanyanDBClient.java:386) ~[banyandb-java-client-0.5.0.jar:0.5.0]
	at org.apache.skywalking.banyandb.v1.client.grpc.HandleExceptionsWith.callAndTranslateApiException(HandleExceptionsWith.java:45) ~[banyandb-java-client-0.5.0.jar:0.5.0]
	at org.apache.skywalking.banyandb.v1.client.BanyanDBClient.query(BanyanDBClient.java:383) ~[banyandb-java-client-0.5.0.jar:0.5.0]
	at org.apache.skywalking.oap.server.storage.plugin.banyandb.BanyanDBStorageClient.query(BanyanDBStorageClient.java:128) ~[storage-banyandb-plugin-9.7.0-SNAPSHOT.jar:9.7.0-SNAPSHOT]
	at org.apache.skywalking.oap.server.storage.plugin.banyandb.stream.AbstractBanyanDBDAO.query(AbstractBanyanDBDAO.java:129) ~[storage-banyandb-plugin-9.7.0-SNAPSHOT.jar:9.7.0-SNAPSHOT]
	at org.apache.skywalking.oap.server.storage.plugin.banyandb.stream.AbstractBanyanDBDAO.query(AbstractBanyanDBDAO.java:115) ~[storage-banyandb-plugin-9.7.0-SNAPSHOT.jar:9.7.0-SNAPSHOT]
	at org.apache.skywalking.oap.server.storage.plugin.banyandb.stream.AbstractBanyanDBDAO.query(AbstractBanyanDBDAO.java:80) ~[storage-banyandb-plugin-9.7.0-SNAPSHOT.jar:9.7.0-SNAPSHOT]
	at org.apache.skywalking.oap.server.storage.plugin.banyandb.measure.BanyanDBMetadataQueryDAO.getInstances(BanyanDBMetadataQueryDAO.java:157) ~[storage-banyandb-plugin-9.7.0-SNAPSHOT.jar:9.7.0-SNAPSHOT]
	at org.apache.skywalking.oap.server.core.profiling.continuous.ContinuousProfilingQueryService.queryContinuousProfilingMonitoringInstances(ContinuousProfilingQueryService.java:150) ~[server-core-9.7.0-SNAPSHOT.jar:9.7.0-SNAPSHOT]
	at org.apache.skywalking.oap.query.graphql.resolver.ContinuousProfilingQuery.queryContinuousProfilingMonitoringInstances(ContinuousProfilingQuery.java:54) ~[query-graphql-plugin-9.7.0-SNAPSHOT.jar:9.7.0-SNAPSHOT]
	at jdk.internal.reflect.GeneratedMethodAccessor130.invoke(Unknown Source) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
	at java.lang.reflect.Method.invoke(Unknown Source) ~[?:?]
	at graphql.kickstart.tools.resolver.MethodFieldResolverDataFetcher.get(MethodFieldResolver.kt:282) ~[graphql-java-tools-13.0.1.jar:?]
	... 44 more

The problem is id index is missing for instance_traffic_minute. Any idea why this could work in v0.4.0? @hanahmily

[wu-sheng]

@hanahmily told me its an OAP banyandb storage plugin bug. He will comment soon.
Let's see.

There is a bug for 0.4 too, but accidentally work due to bugs at both sides.

[wu-sheng]

@lujiajing1126 We should have removed ID column, right? But in BanyanDBMetadataQueryDAO, getInstances doesn't work like getInstance. It still uses the ID as query condition, rather than decoding the ID and use series IDs.

I think this is the root cause.

[lujiajing1126]

@lujiajing1126 We should have removed ID column, right? But in BanyanDBMetadataQueryDAO, getInstances doesn't work like getInstance. It still uses the ID as query condition, rather than decoding the ID and use series IDs.

I think this is the root cause.

I see. Fixed.