Skip to content

Add new parameters to set Spark custom configurations #4172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

jeffersonezra
Copy link
Contributor

@jeffersonezra jeffersonezra commented Jun 21, 2017

Description

This change adds new parameters SparkDefaults, SparkThriftConf, Spark2Defaults, Spark2ThriftConf to the Add-AzureHDInsightConfigValuesCommand cmdlet. The parameters are used to set the Spark-Defaults, Spark-Thrift-SparkConf, Spark2-Defaults and Spark2-Thrift-SparkConf Ambari sections of the configurations.

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

General Guidelines

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

  • Pull request includes test coverage for the included changes.
  • PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

  • New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
  • Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

  • Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
  • Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
  • Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

@msftclas
Copy link

@jeffersonezra,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffersonezra one comment about the markdown help

Also, can you provide tests for the new parameters?

@@ -232,6 +234,58 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -Spark2Defaults
Specifies the Spark2 Defaults configurations of this HDInsight cluster.```yaml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffersonezra can you fix this file so that the ```yaml is on a line by itself. For example:

### -RServer
Specifies the RServer configurations. Valid only for RServer clusters.
```yaml
Text
```

@cormacpayne
Copy link
Member

@azuresdkci test this please

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffersonezra one clarification comment, otherwise LGTM

@@ -82,6 +82,18 @@ public class AddAzureHDInsightConfigValuesCommand : HDInsightCmdletBase
[Parameter(HelpMessage = "Gets the RServer configurations.")]
public Hashtable RServer { get; set; }

[Parameter(HelpMessage = "Gets the Spark Defaults configurations of this HDInsight cluster.")]
public Hashtable SparkDefaults { get; set; }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffersonezra out of curiosity, is it possible for a configuration to have values for both Spark and Spark2 properties? For example, should it be valid for a user to provide values for SparkDefaults and Spark2Defaults?

@cormacpayne
Copy link
Member

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffersonezra one more comment

{
AzureHDInsightConfig config = new AzureHDInsightConfig();

var addConfigValuesCmdlet = new AddAzureHDInsightConfigValuesCommand
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffersonezra should this test be updated since it is using Spark and Spark2 in the same cmdlet call? Or at least have this test split into two, one for each version?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really required, it still tests the whether the configs are correctly set. But I've split it into two.

@cormacpayne
Copy link
Member

@cormacpayne cormacpayne merged commit d34efd4 into Azure:preview Jun 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants