future invoke would block at org.apache.dubbo.rpc.AsyncRpcResult#getValue

[uglycow]

future invoke would block at org.apache.dubbo.rpc.AsyncRpcResult#getValue.

DubboInvoker now return AsyncRpcResult other than RpcResult with a default value. the framework would block when a filter try to access the the result value, even though it's future invoke.

it just behave differently.

[carryxyh]

If u want to get value from future and the future is not completed, it will block.

DubboInvoker now return AsyncRpcResult other than RpcResult with a default value

Nope, just in async way, but not in sync way.

[uglycow]

the invoke return very soon and i would get a default value when i access the result value in my filter in async way before.

now, the invoke would block and i would get the real value when i access the result value in my filter.

different behavior.

[carryxyh]

Don't get your point.
Is this cause some exceptions or sth?

Due to the new async method used in the latest version of dubbo. If you need to handle real results in a filter in an asynchronous scenario, use the onResponse method.

[uglycow]

i mean if a legacy filter occasionally tried to access the result value, we would get blocked there, that's not the case before.

[carryxyh]

Yes,
The new version is not compatible with the upgrade. The old version of the filter needs to be modified to a certain extent, which is normal.

[chickenlj]

DubboInvoker now return AsyncRpcResult other than RpcResult with a default value. the framework would block when a filter try to access the the result value, even though it's future invoke.

I agree with what @uglycow pointed out, we should avoid blocking legacy Filter extensions.

[chickenlj]

Fixed with #3185