trino unnest字段投掷trinoqueryError(type = internal_error,name = page_transport_error)

发布于 2025-02-08 09:36:04 字数 1209 浏览 3 评论 0原文

我试图在Trino中打开两个字段,并且在运行查询大约30分钟后会引发以下错误。源表只有大约3K记录,而我试图打开的字段具有许多子元素,并且是类型行。以下是错误的瞥见。

16:58:28  Runtime Error in model indirect_comm_blah (models/sdm/indirect_comm_blah.sql)
16:58:28    TrinoQueryError(type=INTERNAL_ERROR, name=PAGE_TRANSPORT_ERROR, message="Error fetching http://172.22.xx.xx:8080/v1/task/20220618_164136_00199_pkifc.1.1.0/results/0/0: Expected response code to be 200, but was 503:

以下是我的查询:

SELECT * FROM hosting_ssl ssl,
    UNNEST(main_array) as main_extract,
    UNNEST (sub_array) AS sub_extract

字段main_arraysub_array是类型:

main_array : array(row(col1 varchar, col2 varchar, col3 varchar, col4 varchar, col5 boolean))

sub_array : array(row(col_a varchar, col_b varchar, col_c varchar, col_d varchar, col_e boolean, col_f varchar, col_g varchar, col_h varchar, col_i integer, col_j varchar, col_k varchar, col_l varchar, col_m varchar, col_n varchar, col_o varchar, col_p array(varchar)))

我还注意到,而不是选择CTE中的所有字段,而是避免选择字段main_array和sub_array和sub_array提供了快速输出。这是因为字段的类型main_arraysub_array吗?

I'm trying to unnest two fields in Trino and it throws the below error after running the query for around 30 minutes. The source table has only around 3k records, and the fields I'm trying to unnest has many child elements and is of the type row. Below is the glimpse of the error.

16:58:28  Runtime Error in model indirect_comm_blah (models/sdm/indirect_comm_blah.sql)
16:58:28    TrinoQueryError(type=INTERNAL_ERROR, name=PAGE_TRANSPORT_ERROR, message="Error fetching http://172.22.xx.xx:8080/v1/task/20220618_164136_00199_pkifc.1.1.0/results/0/0: Expected response code to be 200, but was 503:

Below is my query :

SELECT * FROM hosting_ssl ssl,
    UNNEST(main_array) as main_extract,
    UNNEST (sub_array) AS sub_extract

The fields main_array and sub_array are of type:

main_array : array(row(col1 varchar, col2 varchar, col3 varchar, col4 varchar, col5 boolean))

sub_array : array(row(col_a varchar, col_b varchar, col_c varchar, col_d varchar, col_e boolean, col_f varchar, col_g varchar, col_h varchar, col_i integer, col_j varchar, col_k varchar, col_l varchar, col_m varchar, col_n varchar, col_o varchar, col_p array(varchar)))

I also noticed that instead of selecting all fields in the cte, avoid selecting the fields main_array and sub_array gives the output quick. Is this happening because of the type of the fields main_array and sub_array ?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

黯然 2025-02-15 09:36:04

尝试明确指定交叉加入以执行未努力的数据加入:

SELECT * 
FROM hosting_ssl ssl
CROSS JOIN UNNEST(main_array) as main_extract(me),
CROSS JOIN UNNEST(sub_array) AS sub_extract(se)

Try specifying explicitly CROSS JOIN to perform join with unnested data:

SELECT * 
FROM hosting_ssl ssl
CROSS JOIN UNNEST(main_array) as main_extract(me),
CROSS JOIN UNNEST(sub_array) AS sub_extract(se)
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文