[ 
https://issues.apache.org/jira/browse/IMPALA-10772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455375#comment-17455375
 ] 

ASF subversion and git services commented on IMPALA-10772:
----------------------------------------------------------

Commit 157086cb80cb54c6565da25cc327621f6b2b8513 in impala's branch 
refs/heads/master from Fucun Chu
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=157086c ]

IMPALA-10771: Add Tencent COS support

This patch adds support for COS(Cloud Object Storage). Using the
hadoop-cos, the implementation is similar to other remote FileSystems.

New flags for COS:
- num_cos_io_threads: Number of COS I/O threads. Defaults to be 16.

Follow-up:
- Support for caching COS file handles will be addressed in
   IMPALA-10772.
- test_concurrent_inserts and test_failing_inserts in
   test_acid_stress.py are skipped due to slow file listing on
   COS (IMPALA-10773).

Tests:
 - Upload hdfs test data to a COS bucket. Modify all locations in HMS
   DB to point to the COS bucket. Remove some hdfs caching params.
   Run CORE tests.

Change-Id: Idce135a7591d1b4c74425e365525be3086a39821
Reviewed-on: http://gerrit.cloudera.org:8080/17503
Reviewed-by: Joe McDonnell <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Enable file handle cache for COS files
> --------------------------------------
>
>                 Key: IMPALA-10772
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10772
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Fucun Chu
>            Priority: Major
>
> Similar to [IMPALA-8428|https://issues.apache.org/jira/browse/IMPALA-8428] 
> for S3 and [IMPALA-10202|https://issues.apache.org/jira/browse/IMPALA-10202] 
> for ABFS.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to