You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/10/11 15:15:36 UTC
[GitHub] [superset] gregmazur opened a new issue #17058: Apache Impala Error is not descreptive enough
gregmazur opened a new issue #17058:
URL: https://github.com/apache/superset/issues/17058
A clear and concise description of what the bug is.
#### How to reproduce the bug
1. Go to 'SQL Lab'
2. Click on 'Run' for a query that has certain number of rows, usually more then 100 rows
3. Scroll down to '....'
4. See error
`2021-10-11 14:41:41,504 WARNING: superset.views.base: [SupersetError(message='impala error: bytes expected', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'Apache Impala', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
Traceback (most recent call last):
File "/home/superset/venv/lib/python3.7/site-packages/superset/views/base.py", line 204, in wraps
return f(self, *args, **kwargs)
File "/home/superset/venv/lib/python3.7/site-packages/superset/utils/log.py", line 241, in wrapper
value = f(*args, **kwargs)
File "/home/superset/venv/lib/python3.7/site-packages/superset/views/core.py", line 2573, in sql_json
return self.sql_json_exec(request.json, log_params)
File "/home/superset/venv/lib/python3.7/site-packages/superset/views/core.py", line 2762, in sql_json_exec
session, rendered_query, query, expand_data, log_params
File "/home/superset/venv/lib/python3.7/site-packages/superset/views/core.py", line 2558, in _sql_json_sync
[SupersetError(**params) for params in data["errors"]]
superset.exceptions.SupersetErrorsException: [SupersetError(message='impala error: bytes expected', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'Apache Impala', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
Triggering query_id: 2447`
### Expected results
result. Or at least more detail stacktrace to investigate with impyla as there is no exception on Impala log
### Actual results
Apache Impala Error
#### Screenshots
### Environment
(please complete the following information):
- browser type and version: Chrome
- superset version: `superset 1.3.1`
- python version: `python -3.7`
- any feature flags active: more descriptive stack trace
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [X] I have reproduced the issue with at least the latest released version of superset.
- [X] I have checked the issue tracker for the same issue and I haven't found one similar.
### Additional context
trying to connect to Impala
Docker image python:3.7.9
impyla==0.15.0
thrift==0.13.0
thrift-sasl==0.4.2
thriftpy2==0.4.0
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] gregmazur commented on issue #17058: Apache Impala Error is not descreptive enough
Posted by GitBox <gi...@apache.org>.
gregmazur commented on issue #17058:
URL: https://github.com/apache/superset/issues/17058#issuecomment-944219169
Correct.
We ve been using Superset `0.20.4` with the same `impyla` version and it still works, however when we connect to the DB from the newer version it gives the following error. And yes when I request a smaller amount of data I receive the result. It is like if I select, let's say, one column then I can set row limit up to 10 k rows
Also while checking the Impala log I found at the time of the query such thing
`7:14:09.662 AM | INFO | cc:490 | 2d4616d71326a901:be2fab1e00000002] Error preparing scanner for scan range hdfs://nameservice/tablename/ladd_recs/1633960990608/partitionName=psnh/part-00001-2cada810-593f-4cd6-b19b-850ad70d0454.c000.snappy.parquet(0:21846). Cancelled in ScannerContext
-- | -- | -- | --
7:14:09.662 AM | INFO | cc:490 | 2d4616d71326a901:be2fab1e00000002] Error preparing scanner for scan range hdfs://nameservice/tablename/ladd_recs/1633960990608/partitionName=gpc/part-00001-2cada810-593f-4cd6-b19b-850ad70d0454.c000.snappy.parquet(5544:102400). Cancelled in IoMgr RequestContext
7:14:09.662 AM | INFO | cc:490 | 2d4616d71326a901:be2fab1e00000002] Error preparing scanner for scan range hdfs://nameservice/tablename/ladd_recs/1633960990608/partitionName=apco/part-00001-2cada810-593f-4cd6-b19b-850ad70d0454.c000.snappy.parquet(5544:102400). Cancelled in IoMgr RequestContext`
So I assume there is something to do with Superset
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] junlincc commented on issue #17058: Apache Impala Error is not descreptive enough
Posted by GitBox <gi...@apache.org>.
junlincc commented on issue #17058:
URL: https://github.com/apache/superset/issues/17058#issuecomment-941294479
correct me if i understand wrong. when you connect db:impala to superset, and run queries that is supposed to return 100+ rows in sql, you receive an error.
do you also get this error while running the query in Explore?
does it happen to other DBs?
what happen when you run smaller queries?
@gregmazur 🙏
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] gregmazur edited a comment on issue #17058: Apache Impala Error is not descreptive enough
Posted by GitBox <gi...@apache.org>.
gregmazur edited a comment on issue #17058:
URL: https://github.com/apache/superset/issues/17058#issuecomment-944219169
Correct.
We ve been using Superset `0.20.4` with the same `impyla` version and it still works, however when we connect to the DB from the newer version it gives the following error. And yes when I request a smaller amount of data I receive the result. It is like if I select, let's say, one column then I can set row limit up to 10 k rows
Also while checking the Impala log I found at the time of the query such thing
`7:14:09.662 AM | INFO | cc:490 | 2d4616d71326a901:be2fab1e00000002] Error preparing scanner for scan range hdfs://nameservice/tablename/ladd_recs/1633960990608/partitionName=psnh/part-00001-2cada810-593f-4cd6-b19b-850ad70d0454.c000.snappy.parquet(0:21846). Cancelled in ScannerContext
7:14:09.662 AM | INFO | cc:490 | 2d4616d71326a901:be2fab1e00000002] Error preparing scanner for scan range hdfs://nameservice/tablename/ladd_recs/1633960990608/partitionName=gpc/part-00001-2cada810-593f-4cd6-b19b-850ad70d0454.c000.snappy.parquet(5544:102400). Cancelled in IoMgr RequestContext
7:14:09.662 AM | INFO | cc:490 | 2d4616d71326a901:be2fab1e00000002] Error preparing scanner for scan range hdfs://nameservice/tablename/ladd_recs/1633960990608/partitionName=apco/part-00001-2cada810-593f-4cd6-b19b-850ad70d0454.c000.snappy.parquet(5544:102400). Cancelled in IoMgr RequestContext`
So I assume there is something to do with Superset
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] junlincc commented on issue #17058: Apache Impala Error is not descreptive enough
Posted by GitBox <gi...@apache.org>.
junlincc commented on issue #17058:
URL: https://github.com/apache/superset/issues/17058#issuecomment-941294479
correct me if i understand wrong. when you connect db:impala to superset, and run queries that is supposed to return 100+ rows in sql, you receive an error.
do you also get this error while running the query in Explore?
does it happen to other DBs?
what happen when you run smaller queries?
@gregmazur 🙏
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org