[GitHub] [carbondata] CarbonDataQA2 commented on pull request #4246: [CARBONDATA-4320] Fix clean files removing wrong delta files

2022-01-09 Thread GitBox


CarbonDataQA2 commented on pull request #4246:
URL: https://github.com/apache/carbondata/pull/4246#issuecomment-1008606702


   Build Failed  with Spark 2.3.4, Please check CI 
http://121.244.95.60:12602/job/ApacheCarbonPRBuilder2.3/6200/
   


-- 
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: dev-unsubscr...@carbondata.apache.org

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




[GitHub] [carbondata] CarbonDataQA2 commented on pull request #4238: Carbon CI Test

2022-01-09 Thread GitBox


CarbonDataQA2 commented on pull request #4238:
URL: https://github.com/apache/carbondata/pull/4238#issuecomment-1008605016


   Build Failed  with Spark 2.4.5, Please check CI 
http://121.244.95.60:12602/job/ApacheCarbon_PR_Builder_2.4.5/4456/
   


-- 
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: dev-unsubscr...@carbondata.apache.org

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




[GitHub] [carbondata] CarbonDataQA2 commented on pull request #4238: Carbon CI Test

2022-01-09 Thread GitBox


CarbonDataQA2 commented on pull request #4238:
URL: https://github.com/apache/carbondata/pull/4238#issuecomment-1008586068


   Build Success with Spark 2.3.4, Please check CI 
http://121.244.95.60:12602/job/ApacheCarbonPRBuilder2.3/6201/
   


-- 
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: dev-unsubscr...@carbondata.apache.org

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




[GitHub] [carbondata] kunal642 commented on pull request #4246: [CARBONDATA-4320] Fix clean files removing wrong delta files

2022-01-09 Thread GitBox


kunal642 commented on pull request #4246:
URL: https://github.com/apache/carbondata/pull/4246#issuecomment-1008546624


   retest this please


-- 
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: dev-unsubscr...@carbondata.apache.org

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




[GitHub] [carbondata] ShreelekhyaG commented on pull request #4238: Carbon CI Test

2022-01-09 Thread GitBox


ShreelekhyaG commented on pull request #4238:
URL: https://github.com/apache/carbondata/pull/4238#issuecomment-1008545229


   retest this please


-- 
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: dev-unsubscr...@carbondata.apache.org

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




Re: [DISCUSSION] Log4j2 Vulnerability (CVE-2021-44228, CVE-2021-45046,CVE-2021-45105) Analysis

2022-01-09 Thread Liang Chen
Thanks, Indhumathi.
These analysis info would be very helpful for us.

Regards
Liang

On 2021/12/30 12:31:12 Indhumathi M wrote:
> Hello all, this discussion is related to a Log4j2 vulnerability.
> 
> As you may be aware, there has been a critical vulnerability in Log4j2, the
> Java Logging Library,
> 
> that could result in Remote Code Execution (RCE) if an affected version of
> log4j (2.0 <= log4j <= 2.15.0)
> 
> logs an attacker-controlled string value without proper validation. Please
> see more details on CVE-2021-44228
> .
> 
> We currently believe that the Apache CarbonData platform is not impacted.
> Apache CarbonData does not
> 
> directly use a version of log4j known to be affected by the vulnerability.
> We have reviewed the code and
> 
> run the vulnerability tool, as per the tool report, these three
> vulnerabilities (CVE-2021-44228,
> 
> CVE-2021-45046,CVE-2021-45105) are not identified.
> 
> 
> Regards,
> 
> Indhumathi M
>