We deployed Kylo 0.7.1 on on Cloudera cluster and successfully ingested some data set from customer, however when open the Kylo UI, the Table page in "Feed Manager", in preview, the data can't be displayed correctly. However, same Hive table can be displayed correctly in Squirrel SQL Client, so we believe the data in Hive table is correct.
We suspect that this is due to there are embedded new line in one of the column "CODE" in some of rows. Further trouble shooting required to confirm this.
For further information, please contact Keven.Wang@thinkbiganalytics.com
Kylo 0.7.1 on Cloudera cluster
The issue appears to be with how Kylo's JDBC interface is working.
We do a inner query which appears to be affecting the results.
SELECT * FROM `system`.`parquet2` limit 15
will result in:
SELECT kylo_.* FROM (SELECT * FROM `system`.`parquet2` limit 15) kylo_ LIMIT 1000;
That causes issues and can be seen both in the hive client and in Kylo.
great to see the status of this case is done, so when can we expect a delivery? We had some difficult today to decide if we shall upgrade to kylo 0.8.0.1 for some important bug fixes which are required for one customised kylo/nifi template. Shall make a decision tonight, so will you be able to make a fix on either kylo 0.7.1 or 0.8.0.1? Thank you very much!
I have some new finding today. With the latest fix, it works with preview page also when you execute SQL select statement without where clause. For example if i execute "SELECT * FROM xxx WHERE xxxxx", then the result is again messed up. Is it the same in your env?
I cannot reproduce your issue.
Queries with/without the where clause all work.
What where clause are you trying?
I tried your sample file with numerous where clauses and all seem to be fine.
, I just did "SELECT * FROM use_case_two.demo jewelbox_ingest WHERE CODE IS NOT NULL", then the result is displayed incorrectly. I start to fully work in another project from today and my work has been handovered to and . Thank you!