[jira] [Updated] (HDDS-1846) Default value for checksum bytes is different in ozone-site.xml and code

2019-07-23 Thread Arpit Agarwal (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HDDS-1846:

  Resolution: Fixed
   Fix Version/s: 0.5.0
Target Version/s:   (was: 0.5.0)
  Status: Resolved  (was: Patch Available)

> Default value for checksum bytes is different in ozone-site.xml and code
> 
>
> Key: HDDS-1846
> URL: https://issues.apache.org/jira/browse/HDDS-1846
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.5.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> 
>  ozone.client.checksum.type
>  CRC32
>  OZONE, CLIENT, MANAGEMENT
>  The checksum type [NONE/ CRC32/ CRC32C/ SHA256/ MD5] determines
>  which algorithm would be used to compute checksum for chunk data.
>  Default checksum type is SHA256.
>  
> 
> OzoneConfigKeys.java
> public static final String OZONE_CLIENT_CHECKSUM_TYPE_DEFAULT = "SHA256";
>  
> HDDS-1149 changes in ozone-default.xml, but not changed in java code. This 
> Jira is to fix this issue.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-1846) Default value for checksum bytes is different in ozone-site.xml and code

2019-07-22 Thread Bharat Viswanadham (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Viswanadham updated HDDS-1846:
-
Target Version/s: 0.5.0
  Status: Patch Available  (was: Open)

> Default value for checksum bytes is different in ozone-site.xml and code
> 
>
> Key: HDDS-1846
> URL: https://issues.apache.org/jira/browse/HDDS-1846
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 
>  ozone.client.checksum.type
>  CRC32
>  OZONE, CLIENT, MANAGEMENT
>  The checksum type [NONE/ CRC32/ CRC32C/ SHA256/ MD5] determines
>  which algorithm would be used to compute checksum for chunk data.
>  Default checksum type is SHA256.
>  
> 
> OzoneConfigKeys.java
> public static final String OZONE_CLIENT_CHECKSUM_TYPE_DEFAULT = "SHA256";
>  
> HDDS-1149 changes in ozone-default.xml, but not changed in java code. This 
> Jira is to fix this issue.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-1846) Default value for checksum bytes is different in ozone-site.xml and code

2019-07-22 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-1846:
-
Labels: pull-request-available  (was: )

> Default value for checksum bytes is different in ozone-site.xml and code
> 
>
> Key: HDDS-1846
> URL: https://issues.apache.org/jira/browse/HDDS-1846
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
>  Labels: pull-request-available
>
> 
>  ozone.client.checksum.type
>  CRC32
>  OZONE, CLIENT, MANAGEMENT
>  The checksum type [NONE/ CRC32/ CRC32C/ SHA256/ MD5] determines
>  which algorithm would be used to compute checksum for chunk data.
>  Default checksum type is SHA256.
>  
> 
> OzoneConfigKeys.java
> public static final String OZONE_CLIENT_CHECKSUM_TYPE_DEFAULT = "SHA256";
>  
> HDDS-1149 changes in ozone-default.xml, but not changed in java code. This 
> Jira is to fix this issue.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org