maropu commented on issue #24960: [SPARK-28156][SQL] Self-join should not miss cached view URL: https://github.com/apache/spark/pull/24960#issuecomment-507511937 (This might be off-topic and this is just a question though...) btw, any reason not to use optimized plans instead of analyzed plans for plan caches? Just to avoid overheads? In case that we do so, it seems self-joins in the description uses the cached view; ``` == Optimized Logical Plan == Project [a#37, b#38] +- Join Inner, (a#37 = a#73) :- Project [a#37, b#38] : +- Filter isnotnull(a#37) : +- InMemoryRelation [a#37, b#38, c#39, d#40], StorageLevel(disk, memory, deserialized, 1 replicas) : +- *(1) FileScan orc default.table1[a#37,b#38,c#39,d#40] Batched: true, DataFilters: [], Format: ORC, Location: InMemoryFileIndex[file:/Users/maropu/Repositories/spark/spark-master/spark-warehouse/table1], PartitionFilters: [], PushedFilters: [], ReadSchema: struct<a:int,b:int,c:int,d:int> +- Project [a#37 AS a#73] +- Filter isnotnull(a#37) +- InMemoryRelation [a#37, b#38, c#39, d#40], StorageLevel(disk, memory, deserialized, 1 replicas) +- *(1) FileScan orc default.table1[a#37,b#38,c#39,d#40] Batched: true, DataFilters: [], Format: ORC, Location: InMemoryFileIndex[file:/Users/maropu/Repositories/spark/spark-master/spark-warehouse/table1], PartitionFilters: [], PushedFilters: [], ReadSchema: struct<a:int,b:int,c:int,d:int> ```
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
