Carbondata can provide some way to disable usage of multi-layered index and provide full table scan. This may help in following cases; 1. Small tables occupying only few number of blocks are probably better of using full table scan. 2. Queries with large number of projections with no filter may benefit from using full table scan. 3. Testing different scenarios and comparing with multiple HDFS file formats that do not provide multi layer index will be easier.
Also, Carbondata scan internally should be smart enough to detect this based on query, data size, etc. Any comments? -- View this message in context: http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/Discussion-option-to-disable-multi-layered-index-scan-and-use-full-table-scan-tp1526.html Sent from the Apache CarbonData Mailing List archive mailing list archive at Nabble.com.
