Hi @Dan Burkert , i have tried exactly the same DDL and it give the error. I used hue/impala to create the table. Can you help? ParseException: Syntax error in line 4:undefined: RANGE(year, month) ( ^ Encountered: RANGE Expected: CACHED, COMMENT, LOCATION, PARTITION, PARTITIONED, PRODUCED, ROW, SORT, STORED, TBLPROPERTIES, UNCACHED, WITH CAUSED BY: Exception: Syntax error   ... View more

A kudu table ... View more

You did not mentioned the version of CDH. But I think the problem is that spark launches many executors to read, and those executors are not co-located with the Kudu tablet servers. I dont know if you are just reading/filtering the data, or reading and writing into parquet - it depends how the spark job is executed. What I also noticed, that running multiple spark jobs agains the same table (with different partitions) did not help either. ... View more

Hey @RikG, you are correct.  The way errors are communicated is dependent on the configured FlushMode.  In your example the FlushMode is not set, so it's the default of AUTO_FLUSH_SYNC.  In AUTO_FLUSH_SYNC mode any per-row errors are immediately returned as part of the OperationResponse, since the write happens synchronously.  In AUTO_FLUSH_BACKGROUND mode it's necessary to call getPendingErrors.  The docs on AUTO_FLUSH_BACKGROUND cover this to some extent. ... View more

DROP TABLE IF EXISTS kudu_db.fact_patientencounter_kudu; CREATE TABLE kudu_db.fact_patientencounter_kudu PRIMARY KEY (pk_patientencounterid, fk_agencyid) PARTITION BY HASH(fk_agencyid) PARTITIONS 3 STORED AS KUDU AS SELECT pk_patientencounterid, fk_agencyid FROM default.fact_patientencounter   The above does work. Thanks for the quick replies on this. ... View more

I have been re-run the test, and kudu perform much better this time(though it's still a little bit slower than parquet), thanks for @mpercy's suggestion. I changed two  things by re-runing the test: 1, increase the partitions for the fact table from 60 to 768(affact all queries) 2, change the query3.sql 'or' predicate into 'in' predicate, so predicate can push down to kudu(only affact query 3)   below is the re-run result: (column 'kudu60' is the previous result, which means the partitions of fact table is 60 )  (column 'kudu768' is the new result, which means the partitions of fact table is 768)    ... View more

Got it, thanks a lot. ... View more