Aastha Agrrawal

@wmoustafa @ljfgem , I integrated my PR with the existing end-to-end translation pipeline for Spark. I tested it out with all unit tests and all the production views. No regression...

thanks for the changes! LGTM!

@caicancai thank you for picking this line of work. Please refer to the provided sample pseudo-code below to structure your code: ``` Convert(RelNode coralRelNode) { // Step 1: Convert CoralRel...

Also, when an input hive SQL with `LATERAL VIEW UNNEST(..)` is converted to CoralSqlNode, it is represented using one AS operator. We should also represent this CoralSqlNode using 2 AS...

As discussed offline, please check if it is possible to use `StructKind.PEEK_FIELDS_NO_EXPAND` during all RelNode creation steps in the translation pipeline so that we dont have `StructKind.FULLY_QUALIFIED` type struct fields...

> > As discussed offline, please check if it is possible to use StructKind.PEEK_FIELDS_NO_EXPAND during all RelNode creation steps > > What are the "all RelNode creation steps"? How to...

the ideal translation in this case should be: `SELECT * FROM tmpissue WHERE TRY_CAST(name AS INTEGER) = 1 AND TRY_CAST(name AS INTEGER) IS NOT NULL` Coral should generate the `try_cast()`...

Thanks for the PR, purely based on the PR description, should the namespace unique-fication be at the conflicting layer? ``` "com.app.Parent.Ctx0" "com.app.Parent.Ctx1" ``` Also, some of the testing done section...

From Coral-Schema’s perspective, it converges hive schema & avro schema literal. The input here is a "single-element union", but it isn’t represented as a "uniontype" in the passed hive schema,...