nsivabalan opened a new pull request, #7841:
URL: https://github.com/apache/hudi/pull/7841

   ### Change Logs
   
   Looks like we are parsing all partitions and files from file system to 
initialize metadata table for a new data table. Infact, at the end of it, we 
discard all of them since they are not committed. This patch is optimizing the 
code block of interest. 
   This impact CTAS specifically. Also fixed some of the job description 
(spark) along the way. 
   
   Here is the snapshot for a simple CTAS command w/ and w/o the fix. 
   
   <img width="1778" alt="Screen Shot 2023-02-03 at 1 36 55 AM" 
src="https://user-images.githubusercontent.com/513218/216566324-b88f3f46-723e-4712-b62d-f4ac9dacdb98.png";>
   
   w/ the fix
   <img width="1775" alt="Screen Shot 2023-02-03 at 1 13 26 AM" 
src="https://user-images.githubusercontent.com/513218/216566376-e63374dd-1666-44b5-874f-89221e6dcb92.png";>
   
   ### Impact
   
   Improves perf of initialization of metadata table for a new table.
   
   ### Risk level (write none, low medium or high below)
   
   low. 
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change_
   
   - _The config description must be updated if new configs are added or the 
default value of the configs are changed_
   - _Any new feature or user-facing change requires updating the Hudi website. 
Please create a Jira ticket, attach the
     ticket number here and follow the 
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to 
make
     changes to the website._
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


-- 
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]

Reply via email to