chaokunyang opened a new issue, #1947:
URL: https://github.com/apache/fury/issues/1947

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/fury/issues) 
and found no similar issues.
   
   
   ### Version
   
   main
   
   ### Component(s)
   
   Java
   
   ### Minimal reproduce step
   
   None
   
   ### What did you expect to see?
   
   java.lang.Error: java.lang.IllegalAccessException: no such constructor: 
org.apache.flink.table.data.binary.BinaryStringDataFuryCodec_0.<init>(Fury,Class)void/invokeSpecial
   
   
   ### What did you see instead?
   
   ```java
   java.lang.Error: java.lang.IllegalAccessException: no such constructor: 
org.apache.flink.table.data.binary.BinaryStringDataFuryCodec_0.<init>(Fury,Class)void/invokeSpecial
   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1155) 
~[?:1.8.0_372]
   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
~[?:1.8.0_372]
   at java.lang.Thread.run(Thread.java:879) [?:1.8.0_372]
   Caused by: java.lang.IllegalAccessException: no such constructor: 
org.apache.flink.table.data.binary.BinaryStringDataFuryCodec_0.<init>(Fury,Class)void/invokeSpecial
   at java.lang.invoke.MemberName.makeAccessException(MemberName.java:867) 
~[?:1.8.0_372]
   at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1003) 
~[?:1.8.0_372]
   at 
java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1386) 
~[?:1.8.0_372]
   at 
java.lang.invoke.MethodHandles$Lookup.findConstructor(MethodHandles.java:924) 
~[?:1.8.0_372]
   at 
org.apache.fury.serializer.Serializers.createSerializer(Serializers.java:127) 
~[flash-serializer-v1.jar:?]
   at 
org.apache.fury.serializer.Serializers.newSerializer(Serializers.java:104) 
~[flash-serializer-v1.jar:?]
   at 
org.apache.fury.resolver.ClassResolver$1.onSuccess(ClassResolver.java:941) 
~[flash-serializer-v1.jar:?]
   at 
org.apache.fury.resolver.ClassResolver$1.onSuccess(ClassResolver.java:938) 
~[flash-serializer-v1.jar:?]
   at 
org.apache.fury.builder.JITContext.lambda$registerSerializerJITCallback$0(JITContext.java:94)
 ~[flash-serializer-v1.jar:?]
   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
~[?:1.8.0_372]
   ... 2 more
   Caused by: java.lang.LinkageError: bad method type alias: (Fury,Class)void 
not visible from class 
org.apache.flink.table.data.binary.BinaryStringDataFuryCodec_0
   at java.lang.invoke.MemberName.checkForTypeAlias(MemberName.java:793) 
~[?:1.8.0_372]
   at java.lang.invoke.MemberName$Factory.resolve(MemberName.java:976) 
~[?:1.8.0_372]
   at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1000) 
~[?:1.8.0_372]
   at 
java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1386) 
~[?:1.8.0_372]
   at 
java.lang.invoke.MethodHandles$Lookup.findConstructor(MethodHandles.java:924) 
~[?:1.8.0_372]
   at 
org.apache.fury.serializer.Serializers.createSerializer(Serializers.java:127) 
~[flash-serializer-v1.jar:?]
   at 
org.apache.fury.serializer.Serializers.newSerializer(Serializers.java:104) 
~[flash-serializer-v1.jar:?]
   at 
org.apache.fury.resolver.ClassResolver$1.onSuccess(ClassResolver.java:941) 
~[flash-serializer-v1.jar:?]
   at 
org.apache.fury.resolver.ClassResolver$1.onSuccess(ClassResolver.java:938) 
~[flash-se rializer-v1.jar:?]
   at 
org.apache.fury.builder.JITContext.lambda$registerSerializerJITCallback$0(JITContext.java:94)
 ~[flash-serializer-v1.jar:?]
   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
~[?:1.8.0_372]
   ... 2 more
   ```
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to