You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/03/25 15:01:00 UTC
[jira] [Commented] (IMPALA-11145) Block reads on JSON table until we support it
[ https://issues.apache.org/jira/browse/IMPALA-11145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512419#comment-17512419 ]
ASF subversion and git services commented on IMPALA-11145:
----------------------------------------------------------
Commit dff5171b9879d3b7455c2deb41d9baf3207c716a in impala's branch refs/heads/master from pranav.lodha
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=dff5171 ]
IMPALA-11145: Block reads on JSON table until we support it
Since, scanning JSON tables leads to a BE crash, it's been blocked at
FE using appropriate error message. An end-to-end test has also been
included to test the blocking and the error message.
Change-Id: Idcebf5891f8db52be442f66a8efb1724d1e545aa
Reviewed-on: http://gerrit.cloudera.org:8080/18323
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Block reads on JSON table until we support it
> ---------------------------------------------
>
> Key: IMPALA-11145
> URL: https://issues.apache.org/jira/browse/IMPALA-11145
> Project: IMPALA
> Issue Type: Sub-task
> Components: Frontend
> Reporter: Quanlong Huang
> Assignee: Pranav Yogi Lodha
> Priority: Critical
>
> Before we finish IMPALA-10798, FE should not generate any plans scanning the JSON table. Otherwise, it leads to a crash in BE. I can simply reproduce the crash:
> Create a JSON table in Impala:
> {code:sql}
> create table my_json_tbl (id int, name string, age int) stored as jsonfile;
> {code}
> Upload a JSON file into its directory:
> {code:bash}
> $ cat id_name_age.json
> {"id": 0, "name": "Alice", "age", 10}
> {"id": 1, "name": "Bob", "age", 20}
> {"id": 2, "name": "Oracle", "age", 16}
> $ hdfs dfs -put id_name_age.json hdfs://localhost:20500/test-warehouse/my_json_tbl
> {code}
> Querying the table in Impala
> {code:sql}
> [localhost:21050] default> refresh my_json_tbl;
> [localhost:21050] default> show files in my_json_tbl;
> +--------------------------------------------------------------------+------+-----------+
> | Path | Size | Partition |
> +--------------------------------------------------------------------+------+-----------+
> | hdfs://localhost:20500/test-warehouse/my_json_tbl/id_name_age.json | 113B | |
> +--------------------------------------------------------------------+------+-----------+
> [localhost:21050] default> select * from my_json_tbl;
> Query: select * from my_json_tbl
> Query submitted at: 2022-02-22 13:50:04 (Coordinator: http://quanlong-OptiPlex-BJ:25000)
> Query progress can be monitored at: http://quanlong-OptiPlex-BJ:25000/query_plan?query_id=7c427bd4bc29881a:702a2a9b00000000
> [ ] 0%
> ERROR: Failed due to unreachable impalad(s): quanlong-OptiPlex-BJ:27002
> {code}
> The impalad at port 27002 crashed. Looking into its ERROR log file, i.e. logs/cluster/impalad_node2.ERROR:
> {code:java}
> F0222 13:50:05.099845 4112 hdfs-scan-node-base.cc:693] 7c427bd4bc29881a:702a2a9b00000001] Check failed: false Unexpected file type JSON
> *** Check failure stack trace: ***
> @ 0x570012c google::LogMessage::Fail()
> @ 0x57019dc google::LogMessage::SendToLog()
> @ 0x56ffa8a google::LogMessage::Flush()
> @ 0x5703648 google::LogMessageFatal::~LogMessageFatal()
> @ 0x2b6dadc impala::HdfsScanNodeBase::IssueInitialScanRanges()
> @ 0x2d478bb impala::HdfsScanNode::GetNext()
> @ 0x24ee836 impala::FragmentInstanceState::ExecInternal()
> @ 0x24eaa9b impala::FragmentInstanceState::Exec()
> @ 0x24258c1 impala::QueryState::ExecFInstance()
> @ 0x2423cbf _ZZN6impala10QueryState15StartFInstancesEvENKUlvE_clEv
> @ 0x242894b _ZN5boost6detail8function26void_function_obj_invoker0IZN6impala10QueryState15StartFInstancesEvEUlvE_vE6invokeERNS1_15function_bufferE
> @ 0x22c5769 boost::function0<>::operator()()
> @ 0x2a99f3a impala::Thread::SuperviseThread()
> @ 0x2aa288a boost::_bi::list5<>::operator()<>()
> @ 0x2aa27ae boost::_bi::bind_t<>::operator()()
> @ 0x2aa276f boost::detail::thread_data<>::run()
> @ 0x43a8d10 thread_proxy
> @ 0x7fd9616c36b9 start_thread
> @ 0x7fd95e0ff4dc clone
> {code}
> FE should reject such SELECT queries and return an error like "Reading JSON files is unsupported yet".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org