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 851-867 of 867 flagged pages
Hdinsight
Use Azure Monitor logs to monitor Azure HDInsight clusters
...insight/hdinsight-hadoop-oms-log-analytics-tutorial.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling Azure Monitor logs on HDInsight clusters. However, PowerShell (a Windows-centric tool) is consistently presented before Azure CLI, and PowerShell-specific prerequisites and commands are detailed with equal or greater prominence. The portal instructions also implicitly assume Windows usage, as the Azure portal is most commonly accessed from Windows environments. There are no Linux/macOS-specific instructions or troubleshooting tips, and no mention of Bash, shell scripting, or platform-specific nuances for non-Windows users.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
- Add explicit notes about cross-platform compatibility for Azure CLI, including any OS-specific caveats or troubleshooting steps for Linux/macOS users.
- Include Bash or shell script examples where relevant, especially for automation scenarios.
- Clarify that the Azure portal is accessible from any OS/browser, and provide guidance for Linux/macOS users if there are known issues.
- Add a section or callout for Linux/macOS users highlighting any differences or additional steps required.
Create Pull Request
Hdinsight
Use Azure Data Lake Storage Gen2 with Azure HDInsight clusters
...insight/hdinsight-hadoop-use-data-lake-storage-gen2.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Windows-specific tools (PowerShell) as a primary method for cluster creation, listing it alongside Portal and Azure CLI. However, the actual usage and data access examples are Linux/Unix-centric, using SSH and Bash/HDFS commands. There is a slight Windows bias in the ordering and inclusion of PowerShell, but Linux users are well-supported for operational tasks.
Recommendations
- Add explicit Linux/macOS equivalents for cluster creation, such as Bash scripts or direct Azure CLI examples, and ensure these are presented before or alongside PowerShell.
- Clarify that Azure CLI is cross-platform and provide example commands for Linux/macOS environments.
- If PowerShell is mentioned, also mention Bash or other Linux-native scripting options for parity.
- Consider reordering the 'Create HDInsight clusters' section to list Azure CLI before PowerShell, or group them as 'Command-line options'.
Hdinsight
Plan a virtual network for Azure HDInsight
...hdinsight/hdinsight-plan-virtual-network-deployment.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for network resource queries, but PowerShell commands are consistently listed first, and the scripting examples are written in PowerShell syntax. There are no explicit Linux/macOS shell examples (e.g., Bash), and the documentation does not mention OS-specific prerequisites or considerations for running CLI commands on non-Windows platforms. The overall structure and examples subtly favor Windows users by prioritizing PowerShell and not acknowledging Linux/macOS environments.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI (cross-platform) examples first.
- Explicitly mention that Azure CLI works natively on Linux/macOS and provide Bash shell examples where appropriate.
- Add notes or links about installing and using Azure CLI on Linux/macOS.
- Include troubleshooting tips or prerequisites for Linux/macOS users (e.g., authentication, environment setup).
- Where PowerShell scripts are shown, offer equivalent Bash scripts for common tasks.
Hdinsight
Manually scale a cluster - Azure HDInsight
...articles/hdinsight/hdinsight-scaling-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists PowerShell (Windows-centric) as the first utility for scaling clusters, with detailed command syntax, followed by Azure CLI and other options. While Azure CLI is cross-platform and Linux examples are present for cluster management tasks (SSH, bash commands), the initial emphasis on PowerShell and its placement may signal a Windows-first bias. There are no Linux-specific tools or examples missing, but the ordering and prominence of Windows tools could create minor friction for Linux/macOS users.
Recommendations
- List Azure CLI (cross-platform) before PowerShell in the utilities table to emphasize platform neutrality.
- Explicitly state that Azure CLI works on Linux/macOS/Windows, while PowerShell is Windows-centric.
- Add a note clarifying that all bash/SSH commands are applicable to Linux/macOS and Windows with WSL.
- Where possible, provide equivalent Linux shell commands alongside PowerShell examples if new examples are added in future revisions.
Hdinsight
Quickstart: Apache Hive in Azure HDInsight with Apache Zeppelin
...t/interactive-query/hdinsight-connect-hive-zeppelin.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by referencing Windows-centric tools (PowerShell, Visual Studio) and mentioning them before Linux equivalents. The cluster deletion instructions list PowerShell and Azure CLI, but PowerShell is mentioned first, and the next steps direct users to Visual Studio, a Windows-only tool, for further learning. No Linux/macOS-specific examples or tools are highlighted.
Recommendations
- Explicitly mention and provide examples for deleting clusters using Azure CLI and Bash, not just PowerShell.
- Offer alternative next steps for Linux/macOS users, such as connecting with VS Code, Jupyter, or other cross-platform tools.
- Ensure that references to tools like Visual Studio are accompanied by Linux/macOS alternatives.
- Where multiple tools are listed (e.g., PowerShell, Azure CLI), alternate the order or clarify cross-platform support.
Hdinsight
Connect Apache Kafka cluster with VM in different VNet on Azure HDInsight - Azure HDInsight
...fka/connect-kafka-cluster-with-vm-in-different-vnet.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows Example Present
Linux First
Summary
The documentation provides both Linux and Windows VM instructions for connecting to an Apache Kafka cluster across VNets. Linux is presented first in the example commands and steps, with explicit instructions for editing /etc/hosts and using curl. Windows instructions are present but limited to a note about editing the hosts file and a screenshot. No PowerShell or Windows-specific command-line examples are given, and Linux is the default for most steps.
Recommendations
- Provide explicit Windows command-line examples (e.g., using PowerShell or Command Prompt to test connectivity, such as 'Invoke-WebRequest' or 'curl' on Windows 10+).
- Include instructions for editing the Windows hosts file (e.g., using Notepad with administrator privileges) and mention required permissions.
- Clarify any differences in Kafka client usage or troubleshooting steps between Linux and Windows.
- Ensure parity in screenshots: show both Linux and Windows outputs for key steps (not just the hosts file edit).
Hdinsight
Quickstart: Create Apache Spark cluster using Bicep - Azure HDInsight
...dinsight/spark/apache-spark-jupyter-spark-use-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but PowerShell examples are consistently presented alongside CLI, and sometimes appear first. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since Bash or shell scripting alternatives for Linux/macOS users are not explicitly mentioned. However, the Azure CLI examples are cross-platform and appear in all critical steps, ensuring Linux/macOS users can complete the tasks.
Recommendations
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and is recommended for cross-platform use.
- Consider listing Azure CLI examples before PowerShell examples to reinforce CLI as the default, cross-platform choice.
- Add brief notes or links for installing and using Azure CLI on Linux/macOS.
- If scripting is discussed, provide Bash examples or clarify that CLI commands can be run in Bash/zsh/fish shells.
- Avoid implying PowerShell is required for Linux/macOS users; clarify that PowerShell Core is available cross-platform if needed.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/interactive-query-tutorial-analyze-flight-data.md
...uery/interactive-query-tutorial-analyze-flight-data.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides cross-platform instructions for most steps, using SSH, Bash, and Linux tools throughout. However, in the 'Upload data to an HDInsight cluster' section, the instructions say 'open a command prompt' before using scp, which may imply a Windows-first approach. Additionally, the 'Clean up resources' section mentions deleting clusters using 'your browser, PowerShell, or the Azure CLI', listing PowerShell (a Windows tool) before Azure CLI, which is more cross-platform. No explicit PowerShell-only examples or Windows-only tools are used in the main workflow, and Linux tools are well represented.
Recommendations
- Replace 'open a command prompt' with 'open a terminal' to be platform-neutral.
- In the clean-up section, list Azure CLI before PowerShell, or mention both together as cross-platform options.
- Ensure that all references to command-line tools use terminology that applies to both Windows and Linux (e.g., 'terminal' instead of 'command prompt').
- If PowerShell examples are provided, also provide Bash/Linux equivalents side-by-side.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
...cles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias by listing 'Azure portal, Azure PowerShell, or command-line interface' in that order when describing how to scale out worker nodes. PowerShell is a Windows-centric tool, and its mention before more cross-platform or Linux-native tools (such as Azure CLI or Bash) subtly prioritizes Windows workflows. However, the rest of the article is platform-neutral, focusing on Hive, Tez, and general Hadoop concepts, and does not provide OS-specific examples or instructions.
Recommendations
- When listing tools or interfaces, mention cross-platform or Linux-native tools (such as Azure CLI or Bash) before or alongside Windows-specific tools like PowerShell.
- Provide explicit Linux command-line examples (e.g., using Azure CLI in Bash) where relevant, especially in sections discussing cluster management.
- If mentioning PowerShell, clarify that equivalent commands are available for Linux/macOS users via Azure CLI or Bash.
- Consider adding a brief section or note on managing HDInsight clusters from Linux environments to ensure parity.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enable-private-link-on-kafka-rest-proxy-hdi-cluster.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enable-private-link-on-kafka-rest-proxy-hdi-cluster.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or commands, but it also omits any mention of how to perform the steps via command line or scripts (such as Azure CLI, PowerShell, or Bash). This lack of parity is a subtle form of bias, as it assumes users will use the Azure Portal UI, which is more common among Windows users. There are no explicit Windows tools or PowerShell commands, but the absence of Linux/CLI alternatives is a gap.
Recommendations
- Add step-by-step instructions for creating private endpoints and configuring DNS using Azure CLI commands, which are cross-platform and commonly used on Linux.
- Include examples for both Azure CLI and PowerShell (if relevant), and present them side-by-side or with clear tabs.
- Mention that these operations can be performed via the Azure Portal, Azure CLI, or PowerShell, and provide links to relevant documentation for each method.
- Ensure that any screenshots or UI references are supplemented with equivalent command-line instructions.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/azure-cli-samples.md
...docs/blob/main/articles/hdinsight/azure-cli-samples.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias in the prerequisites section, where Bash usage is described specifically as 'the Bash shell on Windows 10' and installation instructions are linked for Windows Subsystem for Linux (WSL) on Windows 10. There is no mention of native Linux or macOS environments, and no guidance for users running the Azure CLI from those platforms. All CLI examples use Bash syntax, which is cross-platform, but the only explicit environment guidance is for Windows users.
Recommendations
- Update the prerequisites section to mention that the Azure CLI and Bash examples work natively on Linux and macOS, not just on Windows (WSL).
- Provide installation links or brief instructions for Bash and Azure CLI on Linux and macOS, in addition to the current WSL/Windows guidance.
- Clarify that the examples are cross-platform and specify any differences (if any) for Linux, macOS, or Windows Command Prompt/PowerShell.
- Consider adding a short note or table summarizing how to adapt the examples for Windows Command Prompt or PowerShell, if relevant.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-phoenix-psql.md
.../articles/hdinsight/hbase/apache-hbase-phoenix-psql.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation uses 'command prompt' terminology and presents Windows-style commands (e.g., scp and ssh) with a 'cmd' code block label before switching to bash, but does not provide explicit Linux shell equivalents or clarify cross-platform usage. The initial instructions assume a Windows user context, which may confuse Linux users.
Recommendations
- Provide both Windows and Linux/macOS command examples where relevant, especially for file transfer and SSH steps.
- Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt' to avoid implying a Windows-only environment.
- Clarify that the commands (scp, ssh) are available on both Windows (with tools like Git Bash or WSL) and Linux/macOS, or provide platform-specific instructions if there are differences.
- Label code blocks appropriately (e.g., 'bash' instead of 'cmd') when the commands are not Windows-specific.
- Add a note at the beginning specifying that the instructions apply to both Windows and Linux/macOS users, and highlight any platform-specific prerequisites.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-tutorial-get-started-linux.md
...sight/hbase/apache-hbase-tutorial-get-started-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally focuses on Linux-based workflows (SSH, Bash, HBase shell, curl), but in the prerequisites section, it presents Windows (specifically Windows Subsystem for Linux) as the primary example for running Bash and curl commands, mentioning Linux/Unix shells only as alternatives. Windows PowerShell is referenced as an option, but no PowerShell-specific examples are provided. There are no exclusive Windows tools or PowerShell-heavy sections, and Linux examples are present throughout, but the ordering and phrasing in the prerequisites subtly prioritize Windows.
Recommendations
- In the prerequisites, mention Linux and macOS as primary platforms for Bash and curl, with Windows (via WSL) as an alternative, rather than the other way around.
- Provide explicit Linux/macOS command-line examples where appropriate, and clarify that the tutorial is platform-agnostic unless otherwise noted.
- If mentioning PowerShell, provide a concrete example or move the reference to a footnote or 'Other options' section.
- Review the ordering and phrasing to ensure Linux is not presented as secondary to Windows, especially since HDInsight clusters are Linux-based.
- Consider adding a short section or table summarizing how to run the commands on Linux, macOS, and Windows (with WSL), to reinforce parity.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-using-spark-query-hbase.md
...rticles/hdinsight/hdinsight-using-spark-query-hbase.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides SSH connection command examples using the Windows Command Prompt (cmd) syntax (e.g., 'ssh sshuser@CLUSTER-ssh.azurehdinsight.net') before any Linux-specific or cross-platform guidance. However, the majority of command-line examples (hbase shell, bash, scala, etc.) are platform-neutral or Linux-oriented, and there is no exclusive use of Windows tools or PowerShell, nor are Linux examples missing.
Recommendations
- When presenting SSH commands, use a platform-neutral format or provide both Windows (cmd/PowerShell) and Linux/macOS (bash/terminal) variants side-by-side.
- Explicitly state that the SSH commands work on both Windows (with OpenSSH or PuTTY) and Linux/macOS terminals, and provide guidance for each platform if there are differences.
- Where possible, avoid using the 'cmd' code block for SSH commands unless specifically targeting Windows users; use 'bash' or a generic code block for cross-platform compatibility.
- Add a short section at the start clarifying that all examples are intended for Linux-based HDInsight clusters, and that commands are to be run from a Bash shell unless otherwise noted.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/azure-cli-samples.md
...docs/blob/main/articles/hdinsight/azure-cli-samples.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows 10 and the Windows Subsystem for Linux (WSL) as the primary environment for running Bash, and by providing installation guidance specifically for WSL on Windows 10. While all CLI examples use Bash syntax, the documentation positions Windows (with WSL) as the default context, and only briefly mentions that examples can be adapted for the Windows Command prompt, without providing explicit Windows Command Prompt or PowerShell examples. There are no explicit Linux-native instructions or examples, nor are there PowerShell-heavy or Windows tools used in the commands.
Recommendations
- Present Bash usage in a platform-neutral way, e.g., 'The examples use Bash syntax, which is available on Linux, macOS, and Windows (via WSL or other means)'.
- Provide explicit instructions or notes for running the examples on native Linux and macOS systems, not just Windows with WSL.
- If mentioning WSL, also mention native Linux and macOS as supported environments.
- Consider including a table or section that shows how to adapt the variable setting and commands for Windows Command Prompt and/or PowerShell, or link to a guide for translating Bash to Windows shell syntax.
- Avoid positioning Windows as the default or primary platform unless there is a technical reason.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enable-private-link-on-kafka-rest-proxy-hdi-cluster.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enable-private-link-on-kafka-rest-proxy-hdi-cluster.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or tooling, but it also does not mention or show how to perform tasks using Linux or cross-platform tools. All instructions are GUI-based and generic, but there is a lack of parity for users who may prefer or require CLI-based (e.g., Bash, Azure CLI) instructions, which are common on Linux.
Recommendations
- Add equivalent step-by-step instructions using Azure CLI commands, which are cross-platform and commonly used on Linux.
- Include examples for configuring DNS using command-line tools (e.g., Azure CLI or PowerShell Core, which is cross-platform), not just portal-based steps.
- Explicitly mention that the steps can be performed from any OS using the Azure Portal, and provide links or references to CLI documentation for automation or scripting needs.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-using-spark-query-hbase.md
...rticles/hdinsight/hdinsight-using-spark-query-hbase.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is generally Linux-focused, as HDInsight clusters are Linux-based and all operational examples (SSH, bash, hbase shell, etc.) use Linux conventions. However, there is a minor instance of Windows bias: the SSH command is shown in a Windows Command Prompt (cmd) block (```cmd) before any bash or Linux terminal block, which may suggest a Windows-first approach for remote connection, even though the rest of the workflow is Linux-native.
Recommendations
- Use bash syntax highlighting for SSH commands, or provide both Windows (cmd/PowerShell) and Linux/macOS (bash) SSH command examples side by side.
- Clarify in the prerequisites or first SSH example that the commands are intended for Linux/macOS terminals, but can also be run from Windows using PowerShell or WSL.
- If Windows-specific tools or patterns are not required, default to bash examples, as the clusters themselves are Linux-based.
- If targeting cross-platform users, add a short section or note on how to SSH from Windows (e.g., using PowerShell, Windows Terminal, or PuTTY), and from Linux/macOS (native terminal).