[jira] [Updated] (HDDS-388) Fix the name of the db profile configuration key
[ https://issues.apache.org/jira/browse/HDDS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anu Engineer updated HDDS-388: -- Resolution: Fixed Status: Resolved (was: Patch Available) [~elek] Thanks for the contribution. I have committed this to trunk. > Fix the name of the db profile configuration key > > > Key: HDDS-388 > URL: https://issues.apache.org/jira/browse/HDDS-388 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Trivial > Fix For: 0.2.1 > > Attachments: HDDS-388.001.patch > > > HDDS-359 introduced a new configuration for db profiles but at the end the > name of the configuration key in ozone-default (ozone.db.profile) is > different from the one which is used in the constant (hdds.db.profile). (It's > moved to the HddsConfigKeys at the last minute) > As a result TestOzoneConfigurationFields is failing for precommit tests. > Uploading the trivial fix. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-388) Fix the name of the db profile configuration key
[ https://issues.apache.org/jira/browse/HDDS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated HDDS-388: --- Fix Version/s: 0.2.1 > Fix the name of the db profile configuration key > > > Key: HDDS-388 > URL: https://issues.apache.org/jira/browse/HDDS-388 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Trivial > Fix For: 0.2.1 > > Attachments: HDDS-388.001.patch > > > HDDS-359 introduced a new configuration for db profiles but at the end the > name of the configuration key in ozone-default (ozone.db.profile) is > different from the one which is used in the constant (hdds.db.profile). (It's > moved to the HddsConfigKeys at the last minute) > As a result TestOzoneConfigurationFields is failing for precommit tests. > Uploading the trivial fix. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-388) Fix the name of the db profile configuration key
[ https://issues.apache.org/jira/browse/HDDS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-388: -- Status: Patch Available (was: Open) > Fix the name of the db profile configuration key > > > Key: HDDS-388 > URL: https://issues.apache.org/jira/browse/HDDS-388 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Trivial > Attachments: HDDS-388.001.patch > > > HDDS-359 introduced a new configuration for db profiles but at the end the > name of the configuration key in ozone-default (ozone.db.profile) is > different from the one which is used in the constant (hdds.db.profile). (It's > moved to the HddsConfigKeys at the last minute) > As a result TestOzoneConfigurationFields is failing for precommit tests. > Uploading the trivial fix. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-388) Fix the name of the db profile configuration key
[ https://issues.apache.org/jira/browse/HDDS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-388: -- Attachment: HDDS-388.001.patch > Fix the name of the db profile configuration key > > > Key: HDDS-388 > URL: https://issues.apache.org/jira/browse/HDDS-388 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Trivial > Attachments: HDDS-388.001.patch > > > HDDS-359 introduced a new configuration for db profiles but at the end the > name of the configuration key in ozone-default (ozone.db.profile) is > different from the one which is used in the constant (hdds.db.profile). (It's > moved to the HddsConfigKeys at the last minute) > As a result TestOzoneConfigurationFields is failing for precommit tests. > Uploading the trivial fix. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org