timsants opened a new pull request #8169:
URL: https://github.com/apache/pinot/pull/8169


   ## Description
   
   This change adds a broker config for disabling Groovy transform and filter 
functions in the table ingestion config as it is a security risk. See Github 
issue https://github.com/apache/pinot/issues/7966. By default, Groovy is 
allowed for backwards compatibility to not break existing use cases which 
currently use Groovy.
   
   ### Testing
   Added unit tests and tested config with quick-start config override.
   
   ## Upgrade Notes
   Does this PR prevent a zero down-time upgrade? (Assume upgrade order: 
Controller, Broker, Server, Minion)
   * [ ] Yes (Please label as **<code>backward-incompat</code>**, and complete 
the section below on Release Notes)
   
   Does this PR fix a zero-downtime upgrade introduced earlier?
   * [ ] Yes (Please label this as **<code>backward-incompat</code>**, and 
complete the section below on Release Notes)
   
   Does this PR otherwise need attention when creating release notes? Things to 
consider:
   * [x] Yes (Please label this PR as **<code>release-notes</code>** and 
complete the section on Release Notes)
   ## Release Notes
   <!-- If you have tagged this as either backward-incompat or release-notes,
   you MUST add text here that you would like to see appear in release notes of 
the
   next release. -->
   
   Introduced new config for disabling Groovy in ingestionConfig: 
`controller.disable.groovy`. If not defined, defaults to `false`.
   


-- 
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: commits-unsubscr...@pinot.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org

Reply via email to