bhasudha opened a new issue, #7290: URL: https://github.com/apache/hudi/issues/7290
**_Tips before filing an issue_** - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)? - Join the mailing list to engage in conversations and get faster support at [email protected]. - If you have triaged this as a bug, then file an [issue](https://issues.apache.org/jira/projects/HUDI/issues) directly. **Describe the problem you faced** GlobalDeleteKeyGenerator is meant to be used for writes that have all Delete records and the index type is Global. However, We have added KeyGenerator to the table config validation path to ensure keygenerator cannot be changed. This begs the question how and why would one use the GlobalDeleteKeyGenerator if the keygenerator cannot be changed. **To Reproduce** Steps to reproduce the behavior: 1. Use a keygenerator other than GlobalDeleteKeyGenerator 2. Change to GlobalDeleteKeyGenerator in the next write. 3. 4. **Expected behavior** A clear and concise description of what you expected to happen. **Environment Description** * Hudi version : * Spark version : * Hive version : * Hadoop version : * Storage (HDFS/S3/GCS..) : * Running on Docker? (yes/no) : **Additional context** Add any other context about the problem here. **Stacktrace** ```Add the stacktrace of the error.``` -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
