av9ash/GitBugs huggingface dataset:
Bug: ABFS handles nonexistent/non-auth accounts badly
Status: Open | Priority: Major | Resolution: 
Created: 03/May/23 13:17
Affects Version/s: 3.3.5

Testing storediag with a nonexistent account/bucket raises interesting failures modes

# DNS failures are retried, rather than fail fast
# a container which exists but you can't access fails with the wrong exception


{code}
org.apache.hadoop.fs.FileAlreadyExistsException: Operation failed: "This endpoint does not support BlobStorageEvents or SoftDelete. Please disable these account features if you would like to use this endpoint.", 409, HEAD, https://somewhere.dfs.core.windows

{code}


Proposed
# failfast on host not found, escalate to an account not found
# recognise and translate that does not support BlobStorageEvents 

side issue: is that failure leaking secrets about another a/c? or is it always raised if not authed
Bug: User in staticPriorities cost also shouldn't be accumulated to totalDecayedCallCost and totalRawCallCost.
Status: Open | Priority: Major | Resolution: 
Created: 07/Apr/23 01:43

After HADOOP-17165, we can avoid to restrict some important user who has many request.

In HADOOP-17346, the solution is similar to HADOOP-17165, but the user is service user. And another improvement in HADOOP-17346 is that we can avoid backoff by response time. 

HADOOP-17280 solve the problem "Service-user cost shouldn't be accumulated to totalDecayedCallCost and totalRawCallCost." for HADOOP-17165. HADOOP-17346 also fix it.

I think some code is redundancy, we should reconstruct.
Bug: Generic Build Improvements
Status: Open | Priority: Major | Resolution: 
Created: 13/Apr/23 07:35

Some proposed build changes.
 * Add  {{surefire.failIfNoSpecifiedTests}} as false in POM, else it fails if the test specified in -Dtest isn't there in that module, creates problem when you plan to run multiple tests across multiple sub-projects from the root of the project. (https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#failifnospecifiedtests)

{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0:test (default-test) on project hadoop-build-tools: No tests matching pattern "TestServiceInterruptHandling" were executed! (Set -Dsurefire.failIfNoSpecifiedTests=false to ignore this error.)
{noformat}
 * Disable Concurrent builds: Folks push multiple commits in 5-10 mins while pre-commit is running already, so good to discourage this.

 * Add threshold to number of builds per day, saves resources for genuine PR's against someone pushing multiple commits. (This & the above one: Copied idea from Hive)

 * Leverage Github Actions to delegate some of the tasks to them, so a bit of parallel execution and might save time, may be explore pushing JDK-11 related stuff to Github Actions (We don't run tests as of now for both JDK-11 & 8, tests are for 8 only in precommit)
Bug: ITestS3ACopyFromLocalFile: AuditFailureException
Status: Open | Priority: Minor | Resolution: 
Created: 30/Jun/23 17:11
Affects Version/s: 3.3.9

test failure in AuditFailureException 


{code}
java.nio.file.AccessDeniedException: s3a://stevel-london/fork-0007/test/source5589796147222327638: org.apache.hadoop.fs.s3a.audit.AuditFailureException: 92cd5c39-d723-4c9c-add8-635f15196a2e-00000003 unaudited operation executing a request outside an audit span {object_list_request 'fork-0007/test/source5589796147222327638/' size=2, mutating=false}

{code}

the stack trace shows something is happening in an executor so maybe the context hasn't got in
Bug: ITestS3AFileSystemStatistic failure on mvn verify
Status: Open | Priority: Minor | Resolution: 
Created: 27/Jun/23 12:51

But succeeds when running by itself. Most likely fs might be reused between tests and we count the fsStats.getBytesRead()

```

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.393 s <<< FAILURE! - in org.apache.hadoop.fs.s3a.statistics.ITestS3AFileSystemStatistic
[ERROR] testBytesReadWithStream(org.apache.hadoop.fs.s3a.statistics.ITestS3AFileSystemStatistic)  Time elapsed: 2.392 s  <<< FAILURE!
java.lang.AssertionError: Mismatch in number of FS bytes read by InputStreams expected:<2048> but was:<69944985>
    at org.junit.Assert.fail(Assert.java:89)
    at org.junit.Assert.failNotEquals(Assert.java:835)
    at org.junit.Assert.assertEquals(Assert.java:647)
    at org.apache.hadoop.fs.s3a.statistics.ITestS3AFileSystemStatistic.testBytesReadWithStream(ITestS3AFileSystemStatistic.java:72)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

```
Bug: Improve S3ABlockOutputStream recovery
Status: Reopened | Priority: Minor | Resolution: 
Created: 17/Apr/23 17:45

If an application crashes during an S3ABlockOutputStream upload, it's possible to complete the upload if fast.upload.buffer is set to disk by uploading the s3ablock file with putObject as the final part of the multipart upload. If the application has multiple uploads running in parallel though and they're on the same part number when the application fails, then there is no way to determine which file belongs to which object, and recovery of either upload is impossible.

If the temporary file name for disk buffering included the s3 key, then every partial upload would be recoverable.

h3. Important disclaimer

This change does not directly add the Syncable semantics which applications that require {{Syncable.hsync()}} to only return after all pending data has been durably written to the destination path. S3 is not a filesystem and this change does not make it so.

What is does do is assist anyone trying to implement some post-crash recovery process which
# interrogates s3 to identofy pending uploads to a specific path and get a list of uploaded blocks yet to be committed
# scans the local fs.s3a.buffer dir directories to identify in-progress-write blocks for the same target destination. That is those which were being uploaded, queued for uploaded and the single "new data being written to" block for an output stream
# uploads all those pending blocks
# generates a new POST to complete a multipart upload with all the blocks in the correct order

All this patch does is ensure the buffered block filenames include the final path and block ID, to aid in identify which blocks need to be uploaded and what order. 

h2. warning
causes HADOOP-18744 -always include the relevant fix when backporting
Bug: Fix several maven build warnings
Status: Resolved | Priority: Minor | Resolution: Fixed
Created: 26/Apr/23 03:29
Affects Version/s: 3.4.0

{code}
[WARNING] 'build.plugins.plugin.version' for org.cyclonedx:cyclonedx-maven-plugin is missing.
{code}

{code}
[WARNING] Unknown keyword additionalItems - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
{code}

{code}
[WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:findbugs-maven-plugin is missing
{code}

{code}
[WARNING] Parameter 'requiresOnline' is unknown for plugin 'exec-maven-plugin:1.3.1:exec (pre-dist)'
{code}

{code}
[WARNING] Parameter 'destDir' (user property 'destDir') is deprecated: No reason given
{code}

{code}
[WARNING] Parameter 'tasks' is deprecated: Use target instead
[WARNING] Parameter tasks is deprecated, use target instead
{code}

{code}
[WARNING] Parameter 'systemProperties' is deprecated: Use systemPropertyVariables instead.
{code}
Bug: S3A: reject multipart copy requests when disabled
Status: Resolved | Priority: Minor | Resolution: Fixed
Created: 12/Apr/23 13:27
Affects Version/s: 3.4.0

follow-on to HADOOP-18637 and support for huge file uploads with stores which don't support MPU.

* prevent use of API against any s3 store when disabled, using logging auditor to reject it
* tests to verify rename of huge files still works (by setting large part size)
Bug: Upgrade maven-shade-plugin to 3.4.1
Status: Resolved | Priority: Minor | Resolution: Fixed
Created: 15/Jun/23 08:29
Affects Version/s: 3.4.0

Errors were reported while shading some of the upgraded dependencies due to their inclination towards later java versions e.g
{code:java}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.3.0:shade (default) on project hadoop-client-runtime: Error creating shaded jar: Problem shading JAR /home/rohit/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.15.0/jackson-core-2.15.0.jar entry META-INF/versions/19/com/fasterxml/jackson/core/io/doubleparser/FastDoubleSwar.class: java.lang.IllegalArgumentException: Unsupported class file major version 63 {code}
Version 3.4.1 seems to have fixed such issues.
Bug: Add debug log for getting details of tokenKindMap
Status: Resolved | Priority: Minor | Resolution: Fixed
Created: 22/Apr/23 15:01
Affects Version/s: 3.3.4

Currently there is no way to know what is store in tokenKindMap. There are also no debug logs . I think we should add gettokenKindMap method , so that caller can see the content of the tokenKindMap . It will really help to debug . 
{code:java}
while (tokenIdentifiers.hasNext()) {
          try {
            TokenIdentifier id = tokenIdentifiers.next();
            *tokenKindMap.put(id.getKind(), id.getClass());*
          } catch (ServiceConfigurationError | LinkageError e) {
            // failure to load a token implementation
            // log at debug and continue.
            LOG.debug("Failed to load token identifier implementation", e);
          }
        }
      }
{code}
Bug: AWS SDK v2  code tuning
Status: Resolved | Priority: Minor | Resolution: Duplicate
Created: 15/May/23 14:24
Affects Version/s: 3.4.0

tuning of the v2 sdk code prior to merge;

{code}
* 

hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/auth/AwsCredentialListProvider.java
L184 access denied exception. add test for this?

AWSClientConfig
TODO: Don't think you can set a socket factory for the netty client.


cloudstore: add the new paths
import software.amazon.awssdk.http.apache.ApacheHttpClient;
import software.amazon.awssdk.thirdparty.org.apache.http.conn.ssl.SSLConnectionSocketFactory;  
oftware.amazon.awssdk.services.s3.model.HeadBucketResponse;

hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/impl/HeaderProcessing.java
+add test for getHeaders(/) to see what comes back

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestS3ABucketExistence.java
L128 use explicit region constant rather than inline string

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestS3AConfiguration.java
L552: use intercept()

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestS3AEndpointRegion.java
L75: just throw the exception again
L87, L90, use constants

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/TestS3AAWSCredentialsProvider.java
L44 move o.a.h. imports into "real" hadoop block; include the sets one too

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/TestS3AProxy.java
is new ssl.proxy  setting consistent with what this pr does

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/auth/delegation/ITestSessionDelegationInFileystem.java
L335 TODO open, getObjectMetadata("/")

+cut hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/InconsistentS3ClientFactory.java

{code}
Bug: Support LZ4 compressionLevel
Status: Open | Priority: Minor | Resolution: 
Created: 29/Jun/23 17:35

The Hadoop's LZ4 compression codec now depends on lz4-java. There two type of compressor in lz4, `fastCompressor` and `highCompressor`. The default lz4 compressor in hadoop is fastCompressor, we also can use highCompressor by using config `IO_COMPRESSION_CODEC_LZ4_USELZ4HC_DEFAULT`

 

When we want to use highCompressor in hadoop, we only can use the default compression level, which is level 9. while highCompressor in lz4-java supports compression level from 1 to 17.

 

I think we can set a configuration to let users to choose different compresssionLevel for lz4 highCompressor.
Bug: S3ABlockOutputStream doesn't collect stats on multipart block uploads
Status: Resolved | Priority: Minor | Resolution: Duplicate
Created: 12/Apr/23 18:58
Affects Version/s: 3.3.5

assertion failures in HADOOP-18695 show that S3ABlockOutputStream isn't collecting stats on how long the individual post calls of multipart uploads: duration or number.
that is despite some counters in the IOStatistics of the stream set up to do this and merge to the FS in close()

Looks like the simplest fix is to instrument the FS to do collect these, rather than in-stream. in stream would be best for context stats
Bug: Move CodecPool getCompressor/getDecompressor logs to DEBUG
Status: Open | Priority: Trivial | Resolution: 
Created: 25/Apr/23 16:48
Affects Version/s: 3.3.6

The "Got brand new compressor|decompressor" logs in CodecPool[0] can be quite noisy when reading thousands of blocks and aren't that illuminating for the end user. I'd like to propose moving them from log.info to log.debug if there's no objection.

 

[0] https://github.com/apache/hadoop/blob/b737869e01fe3334b948a38fe3835e48873bf3a6/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/CodecPool.java#L149-L195
Bug: Wrong StringUtils.join() called in AbstractContractRootDirectoryTest
Status: Resolved | Priority: Trivial | Resolution: Fixed
Created: 21/Apr/23 13:56
Affects Version/s: 3.3.6

In the following call to {{StringUtils.join()}}, {{"\n"}} is treated as an element, not as a separator:

{code:title=https://github.com/apache/hadoop/blob/964c1902c8054dfe13c787222a12fb0daf1aaab9/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/contract/AbstractContractRootDirectoryTest.java#L199-L201}
    assertEquals("listStatus on empty root-directory returned found: "
        + join("\n", rootListStatus),
        0, rootListStatus.length);
{code}

Expected output:

{code}
[ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.711 s <<< FAILURE! - in org.apache.hadoop.fs.contract.hdfs.TestHDFSContractRootDirectory
[ERROR] testListEmptyRootDirectory(org.apache.hadoop.fs.contract.hdfs.TestHDFSContractRootDirectory)  Time elapsed: 0.011 s  <<< FAILURE!
java.lang.AssertionError: listStatus on empty root-directory returned found: HdfsLocatedFileStatus{path=hdfs://localhost:37225/test; isDirectory=true; ...} expected:<0> but was:<1>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:647)
	at org.apache.hadoop.fs.contract.AbstractContractRootDirectoryTest.testListEmptyRootDirectory(AbstractContractRootDirectoryTest.java:199)
{code}

Actual output:

{code}
[ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.708 s <<< FAILURE! - in org.apache.hadoop.fs.contract.hdfs.TestHDFSContractRootDirectory
[ERROR] testListEmptyRootDirectory(org.apache.hadoop.fs.contract.hdfs.TestHDFSContractRootDirectory)  Time elapsed: 0.011 s  <<< FAILURE!
java.lang.AssertionError: 
listStatus on empty root-directory returned found: 
[Lorg.apache.hadoop.fs.FileStatus;@73344c46 expected:<0> but was:<1>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:647)
	at org.apache.hadoop.fs.contract.AbstractContractRootDirectoryTest.testListEmptyRootDirectory(AbstractContractRootDirectoryTest.java:199)
{code}
Bug: Fix WriteOperations.listMultipartUploads function description
Status: Resolved | Priority: Trivial | Resolution: Fixed
Created: 02/May/23 19:04
Affects Version/s: 3.3.2

{code:java}
   /**
-   * Abort multipart uploads under a path: limited to the first
-   * few hundred.
-   * @param prefix prefix for uploads to abort
-   * @return a count of aborts
-   * @throws IOException trouble; FileNotFoundExceptions are swallowed.
+   * List in-progress multipart uploads under a path
+   * @param prefix prefix for uploads to list
+   * @return a list of in-progress multipart uploads
+   * @throws IOException on problems
    */
   List<MultipartUpload> listMultipartUploads(String prefix) {code}
Bug: WeakReferenceMap creation warning log doesn't format correctly
Status: Open | Priority: Trivial | Resolution: 
Created: 12/Jun/23 09:40
Affects Version/s: 3.3.5

{{WeakReferenceMap.create(K key)}} logs once at warning level if a reference to a key was lost during creation.



{code}
referenceLostDuringCreation.warn("reference to %s lost during creation", key);
{code}
but it uses %s as the insertion point for the key, when it should be {}.

this means the log, if it ever surfaces, won't include the key. 

i don't think this is a very important issue, but it exists.
Bug: Bump netty to the latest 4.1.61
Status: Resolved | Priority: Blocker | Resolution: Fixed
Created: 31/Mar/21 04:23
Affects Version/s: 3.2.3

For more details: https://netty.io/news/2021/03/09/4-1-60-Final.html

Actually, just yesterday there's a new version 4.1.61. https://netty.io/news/2021/03/30/4-1-61-Final.html
Bug: Build failure due to python2.7 deprecation by pip
Status: Resolved | Priority: Blocker | Resolution: Fixed
Created: 26/Jan/21 07:54
Affects Version/s: 3.4.0

The latest version of pip has deprecated its support for python 2.7 - [pip install on Python 2 fails with SyntaxError: sys.stderr.write(f"ERROR: \{exc}") · Issue #9500 · pypa/pip (github.com)|https://github.com/pypa/pip/issues/9500]

We encounter the following error while building Hadoop -
{code:java}
11:24:56  [0m[91mTraceback (most recent call last):
11:24:56    File "get-pip.py", line 24226, in <module>
11:24:56  [0m[91m    main()
11:24:56    File "get-pip.py", line 199, in main
11:24:56      bootstrap(tmpdir=tmpdir)
11:24:56    File "get-pip.py", line 82, in bootstrap
11:24:56      from pip._internal.cli.main import main as pip_entry_point
11:24:56    File "/tmp/tmpDXDtcP/pip.zip/pip/_internal/cli/main.py", line 60
11:24:56      sys.stderr.write(f"ERROR: {exc}")
11:24:56                                     ^
11:24:56  SyntaxError: invalid syntax {code}
Link : [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2567/16/consoleFull]
Bug: [branch-2.10] Docker image build fails due to the removal of openjdk-7-jdk package
Status: Resolved | Priority: Blocker | Resolution: Fixed
Created: 10/Mar/21 06:57
Affects Version/s: 2.10.1

openjdk-7-jdk has been removed from the openjdk ppa at the end of February 2021.

[https://launchpad.net/~openjdk-r/+archive/ubuntu/ppa/+packages?field.name_filter=&field.status_filter=superseded&field.series_filter=xenial]
Bug: [ERROR] unknown os.arch: riscv -> [Help 1] org.apache.maven.MavenExecutionException: unknown os.arch: riscv
Status: Open | Priority: Blocker | Resolution: 
Created: 22/Jan/21 18:40

I a have a remote access to [SiFive's U54-MC |https://www.sifive.com/cores/u54-mc]board.

[Here is |https://gist.github.com/advancedwebdeveloper/dbaaf3c8e1b9bf26d240ec4997dad815]the full log.

Since I have no exact list of JNI features/Maven artifacts, to consider - it is not clear from which of those I should start porting.
Bug: DistCp: Reduce memory usage on copying huge directories
Status: Resolved | Priority: Critical | Resolution: Fixed
Created: 16/Feb/21 13:04
Affects Version/s: 3.3.1

Presently distCp, uses the producer-consumer kind of setup while building the listing, the input queue and output queue are both unbounded, thus the listStatus grows quite huge.

Rel Code Part :

https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/SimpleCopyListing.java#L635

This goes on bredth-first traversal kind of stuff(uses queue instead of earlier stack), so if you have files at lower depth, it will like open up the entire tree and the start processing....
Bug: Where is hadoop-user-functions.sh.examples ?
Status: Resolved | Priority: Critical | Resolution: Invalid
Created: 03/Mar/21 12:51
Affects Version/s: 3.1.3

in UnixShellGuide page [https://hadoop.apache.org/docs/r3.1.3/hadoop-project-dist/hadoop-common/UnixShellGuide.html]

it is mentioned that 

{{Examples of function replacement are in the ??{{hadoop-user-functions.sh.examples}}?? file.}}

I've searched through whole Hadoop directory and source code, but there is no trace of this file except:

[hadoop-common-project/hadoop-common/src/site/markdown/UnixShellGuide.md]

which only mentions ??Examples of function replacement are in the `hadoop-user-functions.sh.examples` file.??
Bug: Update Dockerfile to use Focal
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 12/Jan/21 06:56
Affects Version/s: 3.4.0

Referring to the current Dockerfile, it seems like the toolchain provided by Ubuntu Bionic isn't on track with the versions of the libraries that are needed. Thus, we are separately installing Boost and other libraries (gcc-9 and CMake 3.19 needed by HDFS-15740). All these won't be necessary if we upgrade to Focal as these library versions are part of the Focal toolchain itself.
Bug: S3A doesn't calculate Content-MD5 on uploads
Status: Open | Priority: Major | Resolution: 
Created: 27/Jan/21 22:19

Hadoop doesn't specify the Content-MD5 of an object when uploading it to an S3 Bucket. This prevents uploads to buckets with Object Lock, that require the Content-MD5 to be specified.

 
{code:java}
com.amazonaws.services.s3.model.AmazonS3Exception: Content-MD5 HTTP header is required for Put Part requests with Object Lock parameters (Service: Amazon S3; Status Code: 400; Error Code: InvalidRequest; Request ID: ****************; S3 Extended Request ID: ****************************************************************************; Proxy: null), S3 Extended Request ID: ****************************************************************************
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1819)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1403)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1372)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1145)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:802)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:770)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:744)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:704)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:686)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:550)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:530)
	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5248)
	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5195)
	at com.amazonaws.services.s3.AmazonS3Client.doUploadPart(AmazonS3Client.java:3768)
	at com.amazonaws.services.s3.AmazonS3Client.uploadPart(AmazonS3Client.java:3753)
	at org.apache.hadoop.fs.s3a.S3AFileSystem.uploadPart(S3AFileSystem.java:2230)
	at org.apache.hadoop.fs.s3a.WriteOperationHelper.lambda$uploadPart$8(WriteOperationHelper.java:558)
	at org.apache.hadoop.fs.s3a.Invoker.once(Invoker.java:110)
	... 15 more{code}
 

Similar to https://issues.apache.org/jira/browse/JCLOUDS-1549

Related to https://issues.apache.org/jira/browse/HADOOP-13076
Bug: Make SM4 support optional for OpenSSL native code
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 29/Mar/21 05:20
Affects Version/s: 3.4.0

openssl-devel-1.1.1g provided by CentOS 8 does not work after HDFS-15098 because the SM4 is not enabled on the openssl package. We should not force users to install OpenSSL from source code even if they do not use SM4 feature.