Hdinsight
439
Total Pages
279
Linux-Friendly Pages
160
Pages with Bias
36.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
867 issues found
Showing 426-450 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line examples that use Windows-specific syntax (e.g., 'set' for environment variables, caret '^' for line continuation, and Windows paths for jq), and by listing PowerShell as a primary method. There are no explicit Linux/bash shell examples, and the curl examples are tailored for Windows command prompt rather than bash. The use of Windows tools and patterns is prevalent, while Linux equivalents are not shown.
Recommendations
- Add explicit Linux/bash shell examples for all curl commands, using bash syntax for environment variables (e.g., 'export'), line continuation (backslash '\'), and typical Linux paths for jq (e.g., '/usr/bin/jq').
- Present both Windows and Linux examples side-by-side or clearly label which environment each example is for.
- Avoid using Windows-specific tools or paths in generic curl examples; provide cross-platform alternatives.
- In the prerequisites, clarify that curl/jq usage is cross-platform and provide installation guidance for both Windows and Linux.
- Ensure that Linux/bash examples are given equal prominence to Windows/PowerShell examples.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
...doop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (such as SQL Server Integration Services, Excel, PowerShell, and C#) when discussing how to move or consume data after Hive transformation. Linux-native or cross-platform alternatives are not mentioned or are relegated to secondary status. There are no examples or instructions for Linux-based tools or workflows, and PowerShell is suggested for automation without mentioning Bash or other Linux scripting options.
Recommendations
- Include Linux-native tools (e.g., mention using Bash scripts, cron jobs, or Linux-based ETL tools) alongside or before Windows-specific tools like PowerShell.
- Provide examples of consuming Hive data using Linux tools (e.g., Python scripts, shell commands, or open-source ETL frameworks like Apache NiFi or Airflow).
- When mentioning SQL Server Integration Services (SSIS), also mention open-source or cross-platform alternatives such as Apache Sqoop (which is briefly mentioned, but not emphasized) or Talend.
- For automation, suggest using Bash or other Linux-native schedulers (e.g., cron) in addition to PowerShell and Azure Logic Apps.
- When discussing data consumption, include examples for Linux users (e.g., using pandas in Python, command-line tools, or connecting via JDBC/ODBC from Linux environments).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-troubleshoot-data-lake-files.md
...sight/hadoop/hdinsight-troubleshoot-data-lake-files.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias, especially in the certificate renewal section, where only PowerShell scripts and Windows-centric tools are provided for managing certificates and service principal credentials. There are no equivalent Bash, Linux CLI, or cross-platform Azure CLI examples for these critical operations. The troubleshooting steps for cluster access use generic commands (hdfs, curl) that are cross-platform, but the remediation steps for certificate management are exclusively Windows/PowerShell-focused.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for certificate creation, management, and assignment, suitable for Linux/macOS environments.
- Include explicit instructions for Linux users on how to generate certificates (e.g., using openssl), associate them with service principals, and update HDInsight clusters.
- When presenting scripts, offer both PowerShell and Bash/Azure CLI versions, or at least mention cross-platform alternatives.
- Avoid assuming the user is on Windows; clarify which steps are OS-specific and provide parity for Linux users.
- Reference Azure CLI documentation and commands alongside PowerShell cmdlets for all Azure resource management tasks.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-visual-studio-tools-get-started.md
...adoop/apache-hadoop-visual-studio-tools-get-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on using Visual Studio and Data Lake Tools, which are Windows-only tools. All instructions, screenshots, and workflows assume the user is on Windows with Visual Studio installed. There are no examples or guidance for Linux users or for using equivalent tools on Linux. The only mention of non-Windows tooling is a brief reference to Azure PowerShell and the Azure portal, but no Linux command-line or cross-platform alternatives are provided.
Recommendations
- Add equivalent instructions for connecting to HDInsight and running Hive queries using cross-platform tools such as VS Code, Azure CLI, or SSH.
- Provide Linux-specific examples for cluster management, job submission, and data exploration (e.g., using Hive CLI, Beeline, or Jupyter Notebooks).
- Include references to open-source or cross-platform editors (such as VS Code) and show how to use them with HDInsight.
- Clearly indicate that Data Lake Tools for Visual Studio is a Windows-only solution and suggest alternatives for Linux/macOS users.
- Add a section or links to documentation on using HDInsight from Linux environments, including command-line and scripting options.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-sqoop-dotnet-sdk.md
...hdinsight/hadoop/apache-hadoop-use-sqoop-dotnet-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments. It assumes the use of Visual Studio, C#, and the .NET SDK, with instructions for using the NuGet Package Manager Console (a PowerShell-based tool). There are no examples or guidance for Linux or cross-platform development environments, nor are alternative tools or workflows (such as using the Azure CLI, Python SDK, or command-line Sqoop invocations) mentioned. The only nod to Linux is in the limitations section, which describes what doesn't work on Linux-based HDInsight clusters, rather than how to work with them.
Recommendations
- Provide equivalent instructions for setting up and running Sqoop jobs using cross-platform tools, such as the Azure CLI, Python SDK, or direct REST API calls.
- Include examples for running Sqoop jobs from Linux or macOS environments, not just from Visual Studio and .NET.
- Offer guidance for using open-source editors (e.g., VS Code) and terminal-based workflows.
- Mention and demonstrate how to install necessary SDKs and dependencies on Linux.
- Reorder or parallelize instructions so that Linux and Windows approaches are given equal prominence.
- Clarify which steps are Windows-specific and provide alternatives for other platforms.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/connect-install-beeline.md
...n/articles/hdinsight/hadoop/connect-install-beeline.md
High Priority
View Details →
Detected Bias Types
Windows First
Wsl Heavy
Missing Native Linux Example
Summary
The documentation page demonstrates a Windows-first bias, particularly in the 'Install Beeline client' section, which exclusively describes installation using Windows Subsystem for Linux (WSL) and references Windows file paths. There are no native Linux or macOS installation instructions, and the only local installation scenario assumes a Windows environment. Throughout the rest of the page, command-line examples are generic Bash and do not show overt Windows or PowerShell bias, but the installation guidance lacks parity for non-Windows users.
Recommendations
- Add a section with installation instructions for native Linux distributions (e.g., Ubuntu, CentOS) without referencing WSL or Windows paths.
- Include installation steps for macOS users, or explicitly state if unsupported.
- Rephrase the installation steps to present Linux and Windows (via WSL) as parallel options, not just WSL.
- Where file paths are mentioned, provide both Windows/WSL and Linux-native examples.
- Consider adding a table or callout summarizing OS-specific steps for clarity.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-troubleshoot-converting-service-principal-certificate.md
...-troubleshoot-converting-service-principal-certificate.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell and C# examples for converting a certificate to a base-64 string, both of which are Windows-centric. There are no Linux or cross-platform command-line examples (such as using OpenSSL or base64 utilities), and Windows tools and patterns are mentioned exclusively.
Recommendations
- Add Linux shell command examples (e.g., using openssl and base64) for converting a .pfx file to a base-64 string.
- Include cross-platform tools and instructions, such as using the 'base64' command available on Linux/macOS.
- Present Windows and Linux examples side-by-side or in parallel sections to ensure parity.
- Explicitly mention that the process can be performed on both Windows and Linux, and provide guidance for both environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md
.../main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by emphasizing Azure PowerShell usage from a workstation, referencing Windows-specific tools and workflows (such as Azure PowerShell and .NET SDK for Hadoop) before or instead of Linux-native approaches, and lacking direct Linux command-line examples. While SSH is mentioned as a cross-platform method, the walkthroughs and detailed instructions focus on Windows-centric tooling, and Linux-specific examples or guidance are minimal or deferred to external links.
Recommendations
- Provide Linux/Unix/macOS command-line examples (e.g., using SSH and Bash) alongside or before Windows/PowerShell examples.
- Include walkthroughs for running Sqoop jobs directly from a Linux or macOS terminal, not just via SSH or Windows tools.
- Balance the presentation of tooling by giving equal prominence to Linux-native methods (such as Bash scripts, SSH, or native Sqoop CLI usage) in both the main text and summary tables.
- Clarify in each section which instructions apply to which operating systems, and avoid assuming the user is on Windows.
- Where PowerShell is used, offer equivalent Bash or shell script commands for Linux/macOS users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell, SSIS) are highlighted, sometimes before or more prominently than cross-platform or Linux-native alternatives. PowerShell is listed as a method for batch processing, but there is no equivalent Linux shell example. Integration with SQL Server Integration Services (SSIS) and Azure Feature Pack, both Windows-centric, is described in detail, while Linux-native scheduling and orchestration options (like cron or shell scripting) are not mentioned. However, cross-platform tools (VS Code, Beeline, REST API) are included, and some Linux/Unix references exist.
Recommendations
- Add explicit Linux shell (bash) and scripting examples for running Hive queries, similar to the PowerShell example.
- When listing client tools, present cross-platform or Linux-native tools (Beeline, REST API, VS Code) before Windows-only tools (Visual Studio, PowerShell).
- Include Linux-native scheduling/orchestration examples (e.g., using cron, shell scripts, or Airflow) alongside Windows/SSIS options.
- Balance the coverage of Windows and Linux tools in the 'How to use Hive' and 'Scheduling Hive queries' sections.
- Where Windows-specific tools are mentioned, provide equivalent Linux alternatives or note their absence.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/submit-apache-hadoop-jobs-programmatically.md
...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation lists Windows-centric tools (.NET SDK and PowerShell) before cross-platform or Linux-native options (curl). PowerShell is given equal prominence to curl, despite being primarily a Windows tool. There are no explicit Linux shell or Bash examples, and the structure implicitly prioritizes Windows workflows.
Recommendations
- Add explicit Bash or Linux shell examples and resources alongside or before PowerShell.
- Reorder the tools to list cross-platform options (curl, Bash) before Windows-specific tools (PowerShell, .NET SDK).
- Clarify which tools are cross-platform and which are Windows-specific to guide users appropriately.
- Consider including Python SDK or CLI examples, which are popular in Linux environments.
- Ensure parity in depth and detail between Windows and Linux instructions throughout the documentation.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-build-java-maven-linux.md
...hdinsight/hbase/apache-hbase-build-java-maven-linux.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All local environment setup instructions, directory paths, and file operations use Windows Command Prompt syntax (e.g., `cmd`, `DEL`, `notepad`, `C:\HDI`). The only text editor mentioned is Microsoft Notepad. The PowerShell workflow is described in detail, but there are no equivalent Linux/Bash examples for local development, file editing, or uploading files to HDInsight. Linux users are left to infer the necessary commands and tools, despite the fact that HDInsight clusters themselves are Linux-based.
Recommendations
- Provide parallel Linux/Bash examples for all command-line instructions, including directory creation, file deletion, and file editing (e.g., use `mkdir`, `rm`, `nano`/`vim`).
- Mention and demonstrate the use of cross-platform or Linux-native text editors (e.g., nano, vim, gedit) alongside Notepad.
- Include a section or callouts for Linux/macOS users, showing how to perform all steps (project setup, file editing, Maven usage, SCP/SSH) in a Unix-like environment.
- Offer Bash scripts or command blocks for uploading JAR files and running jobs, similar to the detailed PowerShell module, possibly using Azure CLI or direct SSH/SCP.
- Reorder or balance the presentation so that Linux and Windows instructions are given equal prominence, or provide tabs/switchers for each platform.
- Clarify in the prerequisites and test environment sections that the instructions are Windows-specific, and direct Linux/macOS users to the appropriate alternative steps.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/hbase-troubleshoot-start-fails.md
...cles/hdinsight/hbase/hbase-troubleshoot-start-fails.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows a mild Windows bias by referencing the Ambari UI (a graphical tool often used on Windows) as the primary method for restarting services and changing configurations, and by mentioning Azure Storage Explorer and Cloud Explorer (both Windows-centric tools) before or instead of CLI/HDFS alternatives. There are no explicit Linux shell or command-line examples for service management, and the documentation does not provide parity for Linux-native workflows.
Recommendations
- Include Linux command-line alternatives for all Ambari UI actions, such as using systemctl or service commands to restart HBase/HMaster services.
- When referencing Azure Storage Explorer or Cloud Explorer, also provide equivalent HDFS CLI commands for file operations (e.g., deleting files, listing directories).
- Ensure that all examples and troubleshooting steps are platform-agnostic or provide both Windows (UI/tools) and Linux (CLI) workflows.
- Clarify that Ambari UI and Azure Storage Explorer are cross-platform, but provide explicit instructions for Linux users where workflows differ.
- Add notes or links to documentation on managing HDInsight clusters from the Linux command line, especially for users who may not have access to graphical tools.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/troubleshoot-invalidnetworkconfigurationerrorcode-cluster-creation-fails.md
...idnetworkconfigurationerrorcode-cluster-creation-fails.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation is generally Linux-focused, as HDInsight clusters run on Linux, and most troubleshooting steps use Linux commands (ssh, nslookup, dig, cat /etc/resolv.conf). However, there is evidence of Windows bias in several areas: PowerShell and Azure Runbook are referenced as primary automation tools, and Windows VMs are mentioned as DNS server options before Linux in one instance. The documentation also references Windows tooling (PowerShell cmdlets) without providing equivalent CLI or Bash alternatives.
Recommendations
- When mentioning automation or scripting (e.g., 'EnableVmProtection' in PowerShell), also provide equivalent Azure CLI or Bash examples for parity.
- When suggesting deploying a DNS server VM, mention Linux first (since HDInsight is Linux-based) or provide parallel instructions for both Linux and Windows.
- Where PowerShell cmdlets are referenced (e.g., Get-AzVirtualNetwork), include Azure CLI equivalents (e.g., az network vnet show) to support users on non-Windows platforms.
- Review all troubleshooting steps to ensure that Linux and cross-platform tools are always presented at least equally, if not with Linux-first emphasis given the HDInsight context.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-rest-sdk.md
...main/articles/hdinsight/hbase/apache-hbase-rest-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing installation instructions using the Visual Studio NuGet Package Manager Console (a Windows-centric tool) and omitting equivalent Linux installation guidance. All code examples are in C#/.NET, which is more commonly associated with Windows development environments. There are no references to Linux-native development workflows, tools, or command-line usage, despite HBase and HDInsight being cross-platform technologies.
Recommendations
- Include instructions for installing the .NET SDK using the dotnet CLI (e.g., 'dotnet add package Microsoft.HBase.Client'), which works on both Windows and Linux.
- Mention and provide examples for developing with the HBase .NET SDK on Linux (e.g., using VS Code, JetBrains Rider, or the command line).
- Add a note or section on how to authenticate and connect from Linux environments, including any differences in handling credentials or environment variables.
- Balance references to Visual Studio with cross-platform editors and tools.
- If possible, provide a brief example of using the SDK from a Linux shell or containerized environment.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-using-phoenix-query-server-rest-sdk.md
...se/apache-hbase-using-phoenix-query-server-rest-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing installation instructions only for the .NET SDK via the Visual Studio NuGet Package Manager Console (a Windows/PowerShell-centric tool), omitting any Linux or cross-platform installation guidance. All code examples are in C# and assume a Windows development environment, with no mention of Linux-compatible workflows or tools. There is no reference to using the SDK from Linux, nor are there CLI or alternative installation instructions for non-Windows users.
Recommendations
- Add instructions for installing the NuGet package using the dotnet CLI (e.g., 'dotnet add package Microsoft.Phoenix.Client'), which works on Linux, macOS, and Windows.
- Explicitly mention that the SDK and examples are cross-platform if applicable, and provide any prerequisites for Linux/macOS users (such as .NET SDK installation).
- Include example commands for Linux/macOS environments, such as using the terminal/bash to install the SDK.
- Clarify any differences or additional steps required for Linux users (e.g., authentication, environment variables, or file paths).
- Consider providing at least one example of running the sample code on Linux (e.g., using VS Code or the dotnet CLI).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/python-udf-hdinsight.md
...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both shell (Linux/Unix) and PowerShell (Windows) examples for uploading files and running jobs on HDInsight. However, there is a notable emphasis on PowerShell, with extensive, detailed scripts and troubleshooting steps provided for PowerShell, while Linux shell examples are more concise and sometimes less detailed. PowerShell is presented as the primary remote automation tool, and some troubleshooting steps (such as line ending conversion) are only shown for PowerShell. There is also a lack of parity in remote job submission: PowerShell is the only method shown for submitting jobs remotely, with no equivalent Linux (e.g., Bash, Azure CLI) examples. Additionally, Windows-specific issues (like CRLF line endings) are discussed, but no Linux-specific troubleshooting is provided.
Recommendations
- Provide equivalent remote job submission examples using Azure CLI or Bash scripts for Linux users, not just PowerShell.
- Ensure troubleshooting steps (such as line ending conversions) are also shown using Linux tools (e.g., dos2unix, sed) alongside PowerShell.
- Balance the level of detail between PowerShell and shell (Bash) examples, ensuring Linux users have equally comprehensive instructions.
- Mention and demonstrate cross-platform tools (like Azure CLI) before or alongside Windows-specific tools like PowerShell.
- Clarify in each section which examples are platform-specific, and provide guidance for both Windows and Linux users where workflows differ.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-query-with-phoenix.md
...les/hdinsight/hbase/apache-hbase-query-with-phoenix.md
High Priority
View Details →
Detected Bias Types
Windows First
Cmd Prompt Examples
Missing Linux Example
Summary
The documentation presents the curl and ssh commands using Windows command prompt (cmd) syntax and terminology (e.g., 'command prompt', code block labeled as 'cmd'), even though the prerequisites and context (SSH, bash paths) are Linux-centric. There are no explicit Linux/Unix shell examples or clarifications for Linux users, and the initial instructions assume a Windows environment by default.
Recommendations
- Provide both Windows and Linux/macOS command examples where relevant, or clarify which OS the example is for.
- Label code blocks appropriately (e.g., 'bash' for shell commands, 'powershell' for PowerShell, 'cmd' for Windows command prompt).
- Explicitly mention Linux/macOS equivalents for commands like curl and ssh, and note any syntax differences.
- Avoid using 'command prompt' generically; specify 'Windows command prompt' or 'terminal' as appropriate.
- If the workflow is intended to be cross-platform, ensure parity in instructions and examples for both Windows and Linux/macOS users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/troubleshoot-rest-api.md
...main/articles/hdinsight/hbase/troubleshoot-rest-api.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references the IIS Gateway module as the source of the security issue, which is a Windows-specific technology. There is no mention of Linux equivalents or how the issue might manifest or be mitigated in Linux-based HDInsight clusters. No Linux-specific troubleshooting steps or examples are provided, and the documentation implicitly assumes a Windows-centric deployment by focusing on IIS.
Recommendations
- Clarify whether the security issue with the ':' character in the namespace is specific to IIS Gateway (Windows) or also applies to Linux-based HDInsight clusters.
- If Linux-based clusters are not affected, explicitly state this and provide guidance for Linux users.
- If Linux-based clusters have a similar issue, describe the equivalent Linux gateway/module and how to troubleshoot or mitigate the problem.
- Provide examples or troubleshooting steps for both Windows and Linux deployments to ensure parity.
- Avoid assuming IIS Gateway as the default; mention alternatives or how the REST API behaves in non-Windows environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell commands for package installation, referencing the PowerShell client GUID in authentication, and providing command-line examples with Windows-style prompts and environment variables (e.g., %HBASE_HOME%). There are no Linux shell or cross-platform examples for SDK installation or command-line operations, and Windows tools/patterns are mentioned before or instead of Linux equivalents.
Recommendations
- Provide equivalent Linux/Unix shell examples for installing NuGet packages (e.g., using dotnet CLI or NuGet CLI on Linux).
- When referencing client IDs or authentication flows, clarify that the example is for Windows/PowerShell and provide alternatives for Linux environments.
- For command-line operations (such as HBase balancing), include Linux shell examples (e.g., using $HBASE_HOME/bin and standard bash syntax) alongside Windows examples.
- Avoid using only Windows environment variable syntax (e.g., %HBASE_HOME%)—include $HBASE_HOME for Linux.
- Add a section or callouts for Linux/macOS users, especially for steps that differ from Windows.
- Ensure all code and command-line snippets are cross-platform or clearly indicate which OS they target.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-storage.md
...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a detailed PowerShell script for verifying additional storage accounts but does not offer an equivalent Linux/Unix shell (Bash) or Azure CLI example. The verification section leads with a PowerShell solution and only follows with a GUI-based (Ambari) method, omitting command-line Linux alternatives. This can disadvantage users working primarily in Linux environments, especially since HDInsight clusters are typically Linux-based.
Recommendations
- Add a Bash or Azure CLI example for verifying additional storage accounts in the cluster, using curl, jq, or az commands.
- Present Linux/CLI-based verification methods before or alongside PowerShell examples to reflect the Linux-first nature of HDInsight clusters.
- Ensure that all PowerShell scripts have equivalent Bash or cross-platform alternatives.
- Clarify in the prerequisites and verification sections that both Windows and Linux users are supported, and provide links to relevant tools for each platform.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-apps-install-applications.md
...icles/hdinsight/hdinsight-apps-install-applications.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a web GUI often associated with Windows workflows), mentioning Azure PowerShell and Azure Classic CLI as automation options, and omitting explicit Linux CLI (Bash/Azure CLI) examples. The only command-line automation tools mentioned are PowerShell and the Classic CLI, with no mention of Bash or Azure CLI commands. There are no step-by-step examples for Linux users, and the workflow is described in a way that assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Add explicit examples using Azure CLI (az) commands for installing, listing, and managing HDInsight applications, alongside or before PowerShell examples.
- Provide step-by-step instructions for performing the same tasks via Bash shell or Linux terminal, not just via the Azure portal.
- Mention and demonstrate the use of SSH and Linux-native tools for cluster management where appropriate.
- Ensure that any references to automation or scripting include both PowerShell and Bash/Azure CLI equivalents.
- Reorder sections or examples so that Linux-native approaches are presented before or alongside Windows/PowerShell methods.
- Clarify that the Azure portal is cross-platform, but also provide parity for users who prefer or require command-line interfaces on Linux.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-authorize-users-to-ambari.md
...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both PowerShell (Windows) and curl/bash (Linux/macOS) examples for adding users to Ambari. However, the PowerShell example is presented before the curl/bash example, and the PowerShell section is more detailed and prominent. The documentation also references PowerShell as a primary tool for cluster interaction, and Windows-centric terminology and tools are mentioned before Linux equivalents. There is a brief note that the bash script would need modifications for Windows, but no equivalent note for adapting PowerShell for Linux/macOS. Overall, there is a subtle Windows bias in ordering, detail, and tool emphasis.
Recommendations
- Present Linux/bash/curl examples before or alongside PowerShell examples to avoid implying Windows is the primary or preferred platform.
- Ensure that both PowerShell and bash/curl examples are equally detailed and prominent.
- Add explicit notes on how to adapt PowerShell scripts for Linux/macOS (e.g., using PowerShell Core), just as there is a note for adapting bash scripts for Windows.
- Mention cross-platform tools (e.g., REST API via curl, Python, or other scripting languages) as first-class options for automation.
- Review other sections for similar ordering or tool emphasis and strive for parity in instructions and language.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-capacity-planning.md
...main/articles/hdinsight/hdinsight-capacity-planning.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. It references PowerShell scripts and Azure Automation (which is closely associated with Windows/PowerShell) as the only example for automating cluster provisioning and deletion, without mentioning Linux-native alternatives. The order of mention and examples provided (e.g., PowerShell before any Linux scripting) further reinforce a Windows-first perspective. There are no explicit Linux shell or cross-platform CLI examples, and no mention of Bash scripting or Linux automation tools.
Recommendations
- Provide equivalent Bash or Azure CLI script examples for cluster provisioning and deletion alongside PowerShell examples.
- Mention cross-platform automation options, such as using Bash scripts with cron jobs or Azure CLI, not just Azure Automation and PowerShell.
- When referencing scripting or automation, present both Windows (PowerShell) and Linux (Bash, CLI) options in parallel, or explicitly state that all operations can be performed from Linux environments.
- Include links to documentation on using Azure CLI and Bash for HDInsight management.
- Review other sections for implicit assumptions of Windows usage and ensure Linux parity in instructions and tooling references.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-config-for-vscode.md
...main/articles/hdinsight/hdinsight-config-for-vscode.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing Windows-specific paths and tools (e.g., C:\Program Files\7-Zip, D:\winutils, winutils.exe) in configuration examples, without providing Linux equivalents or mentioning cross-platform alternatives. There are no Linux or macOS-specific instructions or examples, and the only explicit OS mention is 'windows OS only' for winutils.exe. This may confuse or exclude users on non-Windows platforms.
Recommendations
- For each configuration property that lists a Windows path (e.g., JAVA_HOME, SCALA_HOME, SPARK_HOME), provide equivalent Linux/macOS examples (e.g., /usr/lib/jvm/java-8-openjdk-amd64/ for JAVA_HOME).
- Clarify which settings are Windows-only and which are cross-platform; explicitly mention Linux/macOS compatibility where applicable.
- For tools like 7-Zip and winutils.exe, suggest Linux/macOS alternatives or note when they are not required on those platforms.
- Add a section or table summarizing OS-specific requirements and configuration differences.
- Where possible, use environment-agnostic variables or instructions (e.g., $HOME, ~/bin) in addition to Windows paths.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-with-secure-transfer-storage.md
...oop-create-linux-clusters-with-secure-transfer-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets, and mentioning Windows-centric tools and patterns. Although Azure CLI is included (which is cross-platform), PowerShell is still given prominence and appears before CLI examples. There are no explicit Linux shell or scripting examples, and no mention of Linux-native tools or workflows.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
- Include Linux shell (bash) command examples for relevant operations, such as using curl or az CLI from bash.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands for Linux environments.
- Avoid assuming PowerShell as the default scripting environment; provide parity in instructions for bash and other common Linux shells.
- Where possible, add troubleshooting steps or configuration guidance specific to Linux environments.