[PR] [hotfix][dist] Don't print jindo log when deploy on console mode [fluss]

["swuferhong (via GitHub)" <gi...@apache.org>]

swuferhong opened a new pull request, #2577:
URL: https://github.com/apache/fluss/pull/2577

   <!--
   *Thank you very much for contributing to Fluss - we are happy that you want to help us improve Fluss. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*
   
   ## Contribution Checklist
   
     - Make sure that the pull request corresponds to a [GitHub issue](https://github.com/apache/fluss/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no issue.
   
     - Name the pull request in the format "[component] Title of the pull request", where *[component]* should be replaced by the name of the component being changed. Typically, this corresponds to the component label assigned to the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are unsure about which is the best component.
   
     - Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
   
     - Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes.
   
     - Each pull request should address only one issue, not mix up code from multiple issues.
   
   
   **(The sections below can be removed for hotfixes or typos)**
   -->
   
   ### Purpose
   
   <!-- Linking this pull request to the issue -->
   Linked issue: close #xxx
   
   Don't print jindo log when deploy on console mode.
   
   <!-- What is the purpose of the change -->
   
   ### Brief change log
   
   <!-- Please describe the changes made in this pull request and explain how they address the issue -->
   
   ### Tests
   
   <!-- List UT and IT cases to verify this change -->
   
   ### API and Format
   
   <!-- Does this change affect API or storage format -->
   
   ### Documentation
   
   <!-- Does this change introduce a new feature -->
   


-- 
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: issues-unsubscribe@fluss.apache.org

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

Re: [PR] [hotfix][dist] Don't print jindo log when deploy on console mode [fluss]

["swuferhong (via GitHub)" <gi...@apache.org>]

swuferhong merged PR #2577:
URL: https://github.com/apache/fluss/pull/2577


-- 
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: issues-unsubscribe@fluss.apache.org

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

Re: [PR] [hotfix][dist] Don't print jindo log when deploy on console mode [fluss]

["wuchong (via GitHub)" <gi...@apache.org>]

wuchong commented on code in PR #2577:
URL: https://github.com/apache/fluss/pull/2577#discussion_r2778442443


##########
fluss-dist/src/main/resources/conf/log4j-console.properties:
##########
@@ -57,3 +57,9 @@ appender.rolling.strategy.max=${env:MAX_LOG_FILE_NUMBER:-10}
 # Suppress the irrelevant (wrong) warnings from the Netty channel handler
 logger.netty.name=org.jboss.netty.channel.DefaultChannelPipeline
 logger.netty.level=OFF
+# don't print jindo log
+logger.jindo_fsStats.name=com.aliyun.jindodata.common.FsStats
+logger.jindo_fsStats.level=OFF
+logger.jindo_jnative.name=com.aliyun.jindodata.jnative.NativeLogger
+logger.jindo_jnative.level=OFF

Review Comment:
   @swuferhong @luoyuxia This looks odd because the open-source Fluss distribution doesn't include any Jindo dependencies, yet the log4j configuration is disabling Jindo's logging. Such changes should be kept internal—for example, in `fluss-ali/fluss-ali-dist`. Moreover, we may need to add logging configurations for other internal dependencies in the future as well.



-- 
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: issues-unsubscribe@fluss.apache.org

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