NihalJain commented on PR #1995: URL: https://github.com/apache/phoenix/pull/1995#issuecomment-2422646833
> There was already a DISCUSS thread on this back in Januray 2023, but nothing happened. I think that this is visible and high impact enough to warrant another [DISCUSS] thread. I think we should do this, BTW. Sure @stoty Thank you for the reference. Let me chime into DISCUSS thread and put up what we plan to do here. > Thank you so much for picking this up. I just stumbled upon the [previous PR](https://github.com/apache/phoenix/pull/1548), [Jira issue](https://issues.apache.org/jira/browse/PHOENIX-6851) and the [previous mailing list thread](https://lists.apache.org/thread/9gbh5xs544h4q4w4xt64oy9osy8g8f81). Thank you @lfrancke for bringing this up again on DISCUSS, and for pointing out the JIRA for previous issue. > I do appreciate the work a lot and can try to help out where I can. Sure will be great if you can help with reviews. Will let you know if anything else if needed. > I also appreciate that you split the PR up in multiple commits. If it's not too much work splitting this up in at least two PRs would help tremendously with reviewing it. One that does all the "machinery" and another that runs the reformat etc. I plan to raise 3 PRs . This PR was just to demo the level of inconsistency we have in the codebase and seek feedback. Let me create appropriate JIRAs and raise 3 distinct PRs. 1. Add spotless plugin to format code in phoenix 2. Run spotless:apply to format code in phoenix 3. Add spotless phoenix pre commit check Also need to break the "machinery" part into tasks: task 1 and task 3 as we may want to add to pre-commit only after all issues are fixed with task2. This way we can have ease of backporting as well since task 2 generated code may differ for all branches. -- 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]
