celinayk opened a new pull request, #5298:
URL: https://github.com/apache/zeppelin/pull/5298

   ### What is this PR for?
     `BigQueryInterpreter.pollJob(...)` printed job polling status directly to 
standard output via `System.out.println(...)`, bypassing Zeppelin's 
SLF4J/Log4j2 logging           
     configuration, log levels, and appenders. This made diagnostics noisy and 
hard to route in server/interpreter deployments. This PR replaces the direct 
stdout call with a    
     structured SLF4J logger call. 
   
   
   ### What type of PR is it?
   Improvement
   
   
   ### Todos
     * [x] Replace `System.out.println(...)` in `pollJob(...)` with 
`LOGGER.info(...)`                                                              
                              
     * [x] Preserve job state and wait interval information in the log message  
                                                                                
                  
     * [x] No behavior changes to polling, sleeping, or returned job handling
   
   ### What is the Jira issue?
   [ZEPPELIN-6496](https://issues.apache.org/jira/browse/ZEPPELIN-6496)
   
   ### How should this be tested?
     * `rg -n "System\.out\.println|System\.err\.println" 
bigquery/src/main/java/org/apache/zeppelin/bigquery` returns no results         
                                        
     * `./mvnw test -pl bigquery` compiles/builds successfully                  
                                                                                
                  
     * Manually trigger a BigQuery job poll and confirm the state/interval now 
appears via the configured logger instead of raw stdout  
   
   ### Screenshots (if appropriate)
   N/A
   
   ### Questions:
   * Does the license files need to update? No   
   * Is there breaking changes for older versions? No   
   * Does this needs documentation? No   
   


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