Skip to content
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

[Bug]: A null pointer error occurs when using S3 as Storage when using the kyuubi terminal. #2862

Closed
2 tasks done
upczsh opened this issue May 24, 2024 · 0 comments · Fixed by #2863
Closed
2 tasks done
Labels
type:bug Something isn't working

Comments

@upczsh
Copy link
Contributor

upczsh commented May 24, 2024

What happened?

A null pointer error occurs when using S3 as Storage when using the kyuubi terminal.
image
image

Affects Versions

master/0.6.0

What engines are you seeing the problem on?

AMS

How to reproduce

  1. Use S3 as internal catalog
  2. Use kyuubi to use this catalog

Relevant log output

2024-05-24 16:05:55,652 INFO [terminal-execute-1] [com.netease.arctic.server.terminal.kyuubi.KyuubiTerminalSessionFactory] [] - 
2024-05-24 16:05:55,652 ERROR [terminal-execute-1] [com.netease.arctic.server.terminal.TerminalSessionContext] [] - something error when execute script. 
java.lang.NullPointerException: null
        at java.util.Hashtable.put(Hashtable.java:460) ~[?:1.8.0_312]
        at com.netease.arctic.server.terminal.kyuubi.KyuubiTerminalSessionFactory.create(KyuubiTerminalSessionFactory.java:126) ~[amoro-ams-server-0.6.0.jar:?]
        at com.netease.arctic.server.terminal.TerminalSessionContext.lazyLoadSession(TerminalSessionContext.java:165) ~[amoro-ams-server-0.6.0.jar:?]
        at com.netease.arctic.server.terminal.TerminalSessionContext.access$200(TerminalSessionContext.java:40) ~[amoro-ams-server-0.6.0.jar:?]
        at com.netease.arctic.server.terminal.TerminalSessionContext$ExecutionTask.lambda$get$0(TerminalSessionContext.java:198) ~[amoro-ams-server-0.6.0.jar:?]
        at com.netease.arctic.table.TableMetaStore.call(TableMetaStore.java:234) ~[amoro-core-0.6.0.jar:?]
        at com.netease.arctic.table.TableMetaStore.doAs(TableMetaStore.java:207) ~[amoro-core-0.6.0.jar:?]
        at com.netease.arctic.server.terminal.TerminalSessionContext$ExecutionTask.get(TerminalSessionContext.java:196) [amoro-ams-server-0.6.0.jar:?]
        at com.netease.arctic.server.terminal.TerminalSessionContext$ExecutionTask.get(TerminalSessionContext.java:171) [amoro-ams-server-0.6.0.jar:?]
        at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604) [?:1.8.0_312]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_312]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_312]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312]

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

  • I agree to follow this project's Code of Conduct
@upczsh upczsh added the type:bug Something isn't working label May 24, 2024
upczsh pushed a commit to upczsh/amoro that referenced this issue May 24, 2024
…ng S3 as Storage when using the kyuubi terminal.
upczsh pushed a commit to upczsh/amoro that referenced this issue May 24, 2024
…ng S3 as Storage when using the kyuubi terminal.
upczsh pushed a commit to upczsh/amoro that referenced this issue May 24, 2024
…ng S3 as Storage when using the kyuubi terminal.
upczsh pushed a commit to upczsh/amoro that referenced this issue May 24, 2024
…ng S3 as Storage when using the kyuubi terminal.
upczsh pushed a commit to upczsh/amoro that referenced this issue May 28, 2024
…ng S3 as Storage when using the kyuubi terminal.
upczsh pushed a commit to upczsh/amoro that referenced this issue May 28, 2024
…ng S3 as Storage when using the kyuubi terminal.
upczsh pushed a commit to upczsh/amoro that referenced this issue May 28, 2024
…ng S3 as Storage when using the kyuubi terminal.
baiyangtx added a commit that referenced this issue May 30, 2024
…orage when using the kyuubi terminal. (#2863)

* [AMORO-2862] Fix bug #2862 A null pointer error occurs when using S3 as Storage when using the kyuubi terminal.

* [AMORO-2862] Fix bug #2862 A null pointer error occurs when using S3 as Storage when using the kyuubi terminal.

* [AMORO-2862] Fix bug #2862 A null pointer error occurs when using S3 as Storage when using the kyuubi terminal.

* [AMORO-2862] Fix bug #2862 A null pointer error occurs when using S3 as Storage when using the kyuubi terminal.

* [AMORO-2862] Fix bug #2862 A null pointer error occurs when using S3 as Storage when using the kyuubi terminal.

* [AMORO-2862] Fix bug #2862 A null pointer error occurs when using S3 as Storage when using the kyuubi terminal.

---------

Co-authored-by: zhaoshuaihua <zhaoshuaihua@kingsoft.com>
Co-authored-by: ZhouJinsong <zhoujinsong0505@163.com>
Co-authored-by: baiyangtx <xiangnebula@163.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
1 participant