`CREATE OR REPLACE VIEW` preserves other dialects.
- Dominant language
- Java
- Stars
- 9.2k
- Forks
- 3.5k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 129
Description
### Feature Request / Improvement
For a view that contains multiple dialects, if we run `CREATE OR REPLACE VIEW` directly, it will delete the SQL for the other dialects and leave only the latest Spark SQL. Is my understanding correct that this should instead update only the Spark portion of the SQL and preserve the SQL for other engines?
### Query engine
Spark
### Willingness to contribute
- [x] I can contribute this improvement/feature independently
- [ ] I would be willing to contribute this improvement/feature with guidance from the Iceberg community
- [ ] I cannot contribute this improvement/feature at this time
Contributor guide
Research direction
The issue names no files or tests. Start by reproducing CREATE OR REPLACE VIEW for a view containing multiple dialects in Spark, then trace the view update path; done means updating only the Spark SQL while preserving SQL for the other engines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- data-engineering, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100