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 626-650 of 867 flagged pages
Hdinsight Python UDF with Apache Hive and Apache Pig - Azure HDInsight ...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both shell (Linux/macOS) and PowerShell (Windows) examples for uploading files and running Hive/Pig jobs. However, PowerShell is given substantial coverage, with full scripts for both upload and job submission, while Linux/macOS equivalents are limited to basic shell commands. Troubleshooting and file encoding issues are discussed primarily in the context of Windows/PowerShell. The troubleshooting section specifically addresses Windows line endings and provides PowerShell solutions, with no mention of Linux/macOS alternatives. PowerShell is presented as the primary remote automation tool, with no mention of Bash scripting or cross-platform CLI alternatives for job submission.
Recommendations
  • Add Bash or cross-platform CLI examples for remote job submission and file upload, equivalent to the PowerShell scripts.
  • Include troubleshooting steps for line ending issues using Linux/macOS tools (e.g., dos2unix, sed).
  • Present shell (Linux/macOS) and PowerShell examples side-by-side, or clearly indicate platform applicability.
  • Mention Azure CLI as a cross-platform alternative for automation, not just PowerShell.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell, to help users on Linux/macOS.
GitHub Create Pull Request
Hdinsight Run Apache Sqoop jobs with Azure HDInsight (Apache Hadoop) .../main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The introduction and description focus on using Azure PowerShell from a workstation, implicitly prioritizing Windows tooling. The walkthroughs and links for running Sqoop jobs highlight Azure PowerShell and .NET SDK (both Windows-centric) before mentioning SSH, which is cross-platform. There are no explicit Linux/macOS command examples or walkthroughs in the main body, and the limitations section only discusses Linux-based HDInsight in terms of feature gaps, not usage instructions.
Recommendations
  • Add explicit Linux/macOS walkthroughs and command-line examples for running Sqoop jobs, ideally in the main body of the documentation.
  • Present SSH (cross-platform) instructions before Windows-specific tools like PowerShell and .NET SDK, or at least give them equal prominence.
  • Clarify that SSH and Sqoop are fully supported on Linux/macOS, and provide direct links or inline examples for those platforms.
  • Balance limitations discussion by also mentioning any Windows-specific caveats, if present.
  • Consider renaming sections or rewording introductions to avoid implying that Windows/PowerShell is the default or preferred method.
GitHub Create Pull Request
Hdinsight Submit Apache Hadoop jobs in HDInsight ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists Windows-centric tools (.NET SDK and PowerShell) before cross-platform options (curl), and provides dedicated sections for PowerShell usage, which is primarily a Windows technology. There is no mention of Linux/macOS-specific tools or shell environments, and examples for Linux users (e.g., Bash scripts) are missing.
Recommendations
  • Add explicit Linux/macOS examples using Bash and native command-line tools.
  • Include references to Linux-friendly SDKs or CLI tools, such as Azure CLI.
  • Reorder sections to present cross-platform options (like curl) before Windows-specific tools.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Provide parity in example depth and coverage for Linux/macOS users.
GitHub Create Pull Request
Hdinsight Use Apache Maven to build a Java HBase client for Azure HDInsight ...hdinsight/hbase/apache-hbase-build-java-maven-linux.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: Windows tools (cmd, Notepad, PowerShell) are used exclusively and presented first, with no equivalent Linux/macOS commands or editor suggestions. The test environment is explicitly Windows 10, and file paths use Windows conventions. PowerShell is given a dedicated section with detailed scripts, while Linux/macOS alternatives (e.g., Bash scripts, Linux editors) are missing. Linux users must adapt commands and workflows themselves.
Recommendations
  • Provide Linux/macOS equivalents for all command-line examples (e.g., use bash, rm, mkdir, nano/vim for editing files).
  • Include Linux/macOS file path conventions alongside Windows paths.
  • Add a 'Test environment' note for Linux/macOS, showing how to adapt commands and tools.
  • Offer a Bash script or CLI workflow for uploading JARs and running jobs, similar to the PowerShell module.
  • Suggest cross-platform editors (e.g., VS Code, nano, vim) instead of Notepad.
  • Present Linux/macOS examples before or alongside Windows examples to avoid 'windows_first' ordering.
GitHub Create Pull Request
Hdinsight Create HBase clusters in a Virtual Network - Azure ...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias in the 'Create a virtual machine' section by exclusively linking to instructions for creating a Windows Server VM, without mentioning or linking to Linux VM creation. This places Windows instructions before any Linux equivalents, and omits Linux-specific guidance. The rest of the documentation is generally OS-neutral or Linux-focused (e.g., cluster creation is for Linux-based HBase), but the VM creation step is notably Windows-centric.
Recommendations
  • Include a link to instructions for creating a Linux VM in Azure, such as Ubuntu or CentOS, alongside the Windows VM link.
  • Explicitly state that either Windows or Linux VMs can be used for connecting to the HBase cluster, depending on user preference.
  • Provide examples or notes for both Windows and Linux users when discussing VM setup and connectivity verification.
  • Ensure parity in guidance for post-setup tasks (e.g., using SSH, installing Java, etc.) on both platforms.
GitHub Create Pull Request
Hdinsight REST API to query Apache HBase in Azure HDInsight ...main/articles/hdinsight/hbase/troubleshoot-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references the IIS Gateway module as the source of a security issue, which is a Windows-specific technology. There are no examples or troubleshooting steps tailored for Linux or macOS environments, nor is there mention of Linux equivalents to IIS Gateway. The mitigation steps are platform-neutral, but the cause and technical details are Windows-centric.
Recommendations
  • Clarify whether the security issue applies only to Windows-based HDInsight clusters or also to Linux-based clusters.
  • If Linux clusters are supported, mention the equivalent gateway technology (if any) and whether the same issue occurs.
  • Provide troubleshooting steps or examples for Linux-based HDInsight clusters.
  • Explicitly state platform applicability (Windows, Linux, macOS) in the documentation.
GitHub Create Pull Request
Hdinsight Manage Apache Hadoop clusters in HDInsight with .NET SDK - Azure ...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Package installation instructions are provided only via PowerShell, and the authentication flow references the PowerShell client GUID. Command-line examples for cluster operations (such as balancing HBase region servers) use Windows-style commands and environment variables. There are no Linux/macOS equivalents or instructions for installing the required .NET SDK packages on those platforms. The order and prominence of Windows tools and patterns may create friction for Linux/macOS users.
Recommendations
  • Add .NET SDK package installation instructions for Linux/macOS (e.g., using dotnet CLI or NuGet on those platforms).
  • Provide Linux/macOS shell equivalents for command-line examples (e.g., use $HBASE_HOME/bin and bash syntax instead of Windows-style commands).
  • Clarify that the .NET SDK is cross-platform and provide guidance for non-Windows environments.
  • Avoid referencing Windows-specific GUIDs or tools unless alternatives are also described.
  • Ensure that examples and instructions are presented in a platform-neutral order or grouped by OS.
GitHub Create Pull Request
Hdinsight Tutorial: Apache Spark Streaming & Apache Kafka - Azure HDInsight ...t/hdinsight-apache-kafka-spark-structured-streaming.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides host information gathering commands explicitly for Windows command prompt, using Windows-specific syntax and file paths (e.g., REM, set, C:\HDI\jq-win64.exe), and notes that 'slight variations will be needed for other environments' without providing Linux/macOS equivalents. No Linux/macOS shell examples are given for this critical step, which may create friction for non-Windows users.
Recommendations
  • Provide equivalent Linux/macOS shell commands for gathering host information, using bash syntax and typical jq installation paths.
  • Explicitly document differences in command syntax and environment variables between Windows CMD and Linux/macOS shells.
  • Ensure all critical steps have cross-platform instructions or examples.
  • Consider listing Linux/macOS examples first or side-by-side with Windows examples to avoid implicit prioritization.
GitHub Create Pull Request
Hdinsight Cluster capacity planning in Azure HDInsight ...main/articles/hdinsight/hdinsight-capacity-planning.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions creating and deleting clusters using PowerShell scripts and scheduling them with Azure Automation, both of which are Windows-centric tools. There are no equivalent examples or references for Linux/macOS users, such as using Bash scripts, Azure CLI, or cron for automation. This creates friction for non-Windows users who may not use PowerShell or Azure Automation.
Recommendations
  • Provide examples for cluster provisioning and deletion using Bash scripts and Azure CLI.
  • Mention Linux/macOS automation options, such as cron jobs, alongside Azure Automation.
  • Clarify that HDInsight clusters run on Linux and that management can be performed from any OS using cross-platform tools.
  • Add links to documentation for Azure CLI and Bash scripting for HDInsight cluster management.
GitHub Create Pull Request
Hdinsight Non-interactive authentication .NET application - Azure HDInsight ...ate-non-interactive-authentication-dotnet-applications.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a bias towards Windows environments by providing only C#/.NET examples, referencing NuGet (primarily used in Windows development), and linking to PowerShell-based authentication guides. There are no Linux/macOS-specific instructions, nor are cross-platform alternatives (such as .NET CLI, Bash, or Linux authentication workflows) mentioned. The instructions and tooling are presented in a way that assumes a Windows developer experience.
Recommendations
  • Add examples for developing and running the .NET application on Linux/macOS, including installation steps for .NET SDK and NuGet usage via dotnet CLI.
  • Include authentication instructions using Azure CLI or Bash scripts, which are cross-platform.
  • Reference Linux/macOS equivalents for role assignment and Azure management, such as using Azure CLI instead of PowerShell.
  • Explicitly state platform compatibility and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Hdinsight Authorize users for Ambari Views - Azure HDInsight ...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. The PowerShell method for adding users is presented in full before the Linux-friendly curl/bash example, and the PowerShell script is more detailed and feature-rich. Windows tools (PowerShell) are given prominence and more explanation, while Linux/macOS users are told only that 'slight modifications' are needed for Windows command prompt, not vice versa. There is no parity in scripting depth or troubleshooting for Linux/macOS users.
Recommendations
  • Present Linux/bash (curl) examples before or alongside PowerShell examples.
  • Expand the bash/curl section to match the detail and error handling of the PowerShell script.
  • Explicitly mention macOS compatibility and provide troubleshooting tips for non-Windows platforms.
  • Provide REST API examples using generic tools (curl/httpie) as the primary method, with platform-specific scripts as secondary.
  • Clarify which steps or scripts are platform-agnostic and which require OS-specific tools.
GitHub Create Pull Request
Hdinsight Azure HDInsight configuration settings reference ...main/articles/hdinsight/hdinsight-config-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure HDInsight configuration settings shows evidence of Windows bias. Several configuration properties (e.g., 7z, HADOOP_HOME, JAVA_HOME, SCALA_HOME, SPARK_HOME) provide Windows-specific paths and mention Windows-only tools (e.g., winutils.exe). There are no Linux/macOS equivalents or examples provided, and Windows paths are listed first and exclusively. This may cause confusion or friction for Linux/macOS users trying to configure their environments.
Recommendations
  • Add Linux/macOS equivalent configuration examples for properties like 7z, HADOOP_HOME, JAVA_HOME, SCALA_HOME, and SPARK_HOME.
  • Explicitly note platform differences and provide guidance for Linux/macOS users (e.g., location of binaries, required tools).
  • Where a tool or path is Windows-only (e.g., winutils.exe), clarify its necessity and provide alternatives or workarounds for non-Windows platforms.
  • List examples for all supported platforms side-by-side, or indicate which settings are platform-specific.
GitHub Create Pull Request
Hdinsight Azure HDInsight for Visual Studio Code ...s/blob/main/articles/hdinsight/hdinsight-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., C:\HD\HDexample) as the sole example for file and folder locations, without providing Linux/macOS equivalents. While the prerequisites mention Mono is required for Linux/macOS, and there are a few Linux-specific notes (such as installing xclip), all step-by-step instructions and screenshots use Windows conventions. There are no explicit Linux/macOS command or path examples, which may cause confusion or friction for non-Windows users.
Recommendations
  • Provide parallel examples for Linux/macOS, such as using /home/user/HDexample or ~/HDexample for folder paths.
  • Add screenshots or notes showing the UI on Linux/macOS where it differs.
  • Clarify that steps are identical across platforms except for path syntax, and explicitly show both formats in code blocks or instructions.
  • Include a section or callouts for common Linux/macOS setup issues and solutions (e.g., permissions, Mono installation).
  • Mention keyboard shortcuts for macOS where they differ from Windows.
GitHub Create Pull Request
Hdinsight Apache Hive libraries during cluster creation - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows moderate Windows bias: the main script action is a PowerShell (.ps1) script, with its location given first and most prominently. Windows tools (Azure Storage Explorer) are mentioned for uploading files, and PowerShell/.NET SDK are referenced as cluster creation options before Linux alternatives. Bash script is provided for Linux, but is less emphasized.
Recommendations
  • Present Linux (bash) and Windows (PowerShell) script options equally, listing both script URIs side by side.
  • Include explicit Linux CLI examples for uploading files to Azure Blob Storage (e.g., using azcopy or Azure CLI), not just Azure Storage Explorer.
  • When listing cluster creation methods, mention Linux-friendly tools (Azure CLI, REST API) before or alongside PowerShell/.NET SDK.
  • Clarify which steps/scripts apply to which OS, and ensure Linux instructions are as detailed as Windows ones.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight cluster configurations using bootstrap ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased toward Windows and PowerShell. All code samples and walkthroughs use Azure PowerShell, with no equivalent Bash, CLI, or Linux-native examples. The .NET SDK is mentioned but not demonstrated. The Resource Manager template section is platform-neutral, but the practical, step-by-step instructions and the appendix are exclusively PowerShell-focused. There is no guidance for Linux/macOS users on how to perform these tasks using Azure CLI, Bash, or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for customizing HDInsight cluster configurations.
  • Provide Bash script samples for Linux/macOS users.
  • Include .NET SDK code samples, not just a link.
  • Clearly indicate which steps are platform-neutral and which are Windows-specific.
  • Reorder sections so platform-neutral methods (ARM templates) are presented before Windows-specific ones.
  • Reference and link to Linux/macOS documentation where appropriate.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight clusters by using script actions .../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples and instructions for both Azure PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is consistently presented before CLI examples. PowerShell code samples are more detailed and highlighted, while CLI instructions are less emphasized and appear later. There are no Linux-specific shell examples for interacting with HDInsight beyond Bash script actions themselves. The documentation does not mention macOS or Linux desktop tooling for cluster management, and REST API usage is only briefly referenced.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Expand Azure CLI code samples to match the detail and coverage of PowerShell examples.
  • Explicitly mention that Azure CLI is available on Linux and macOS, and provide installation instructions or links.
  • Include examples of using Bash or other Linux-native tools for cluster management where possible.
  • Add notes or sections for macOS/Linux users regarding tool compatibility and usage.
GitHub Create Pull Request
Hdinsight Use .NET with Hadoop MapReduce on Linux-based HDInsight - Azure .../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (Visual Studio, .NET Portability Analyzer as a Visual Studio extension) and providing step-by-step instructions only for Windows environments. There are no Linux-native alternatives or examples for portability analysis, building, or testing .NET applications on Linux. The guidance assumes access to Visual Studio and does not mention cross-platform .NET tooling or Linux-based development workflows.
Recommendations
  • Include instructions for running portability analysis using command-line tools or cross-platform .NET CLI tools, if available.
  • Provide examples for building and testing .NET applications using Mono and .NET CLI on Linux (e.g., using 'mono', 'dotnet build', etc.).
  • Mention Linux-native editors (such as VS Code) and workflows for .NET development.
  • Add explicit guidance for handling file paths and other platform-specific issues, with Linux examples.
  • Reorder sections or provide parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight Set up clusters in HDInsight with Hadoop, Spark, and Kafka ...hdinsight/hdinsight-hadoop-provision-linux-clusters.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation references Azure PowerShell and Windows PowerShell cmdlets as setup and customization options, and includes a link to 'Work in Apache Hadoop on HDInsight from a Windows PC' in the related content. Script actions are described as available via Azure portal, HDInsight Windows PowerShell cmdlets, or .NET SDK, with no mention of Linux CLI or Bash alternatives in that section. Although the page is generally Linux-focused (HDInsight clusters are Linux-based), Windows tools and patterns are mentioned explicitly and sometimes first, which may create friction for Linux/macOS users.
Recommendations
  • Ensure all examples and tool references include Linux/Bash/Azure CLI equivalents alongside PowerShell and Windows tools.
  • In the 'Script actions' section, explicitly mention how to invoke script actions from Linux/macOS (e.g., Azure CLI, Bash, REST API), not just PowerShell/.NET SDK.
  • In related content, add links for working with HDInsight from Linux/macOS clients, not just Windows.
  • Where Windows tools are referenced, provide parity by listing Linux alternatives in equal prominence and order.
GitHub Create Pull Request
Hdinsight Tutorial: On-demand clusters in Azure HDInsight with Data Factory ...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial relies exclusively on Azure PowerShell scripts for critical setup steps (creating resource groups, storage accounts, and copying files), with no mention of equivalent Bash/CLI commands or Linux/macOS workflows. All code examples are in PowerShell, and the prerequisites only mention installing the Az PowerShell module. This creates friction for Linux/macOS users who typically use Bash and Azure CLI, and may not have PowerShell installed or prefer not to use it.
Recommendations
  • Provide equivalent Azure CLI (az) and Bash script examples for all PowerShell commands, especially for resource creation and file copying.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation guides for each.
  • Clearly indicate that all steps can be performed from Linux/macOS using Azure CLI and Bash, and provide guidance for those platforms.
  • Where possible, use platform-neutral terminology (e.g., 'run the following command in your terminal') and avoid assuming PowerShell is the default shell.
  • Add notes or callouts for Linux/macOS users if any step requires adaptation.
GitHub Create Pull Request
Hdinsight Develop script actions to customize Azure HDInsight clusters ...les/hdinsight/hdinsight-hadoop-script-actions-linux.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation mentions Windows-centric tools (Azure PowerShell, .NET SDK) as primary methods for applying script actions, often listing them before Linux-friendly alternatives. While the script development and troubleshooting guidance is strongly Linux-oriented (Bash, Ubuntu, Linux utilities), the orchestration and management examples are biased toward Windows tools, with little mention of Linux-native equivalents (e.g., Azure CLI, Bash scripting for orchestration). This may create friction for Linux/macOS users managing HDInsight clusters.
Recommendations
  • Add explicit examples and instructions for using Azure CLI to apply script actions, including command-line syntax and workflow.
  • List Linux-friendly management tools (Azure CLI, Bash, REST API) before or alongside Windows tools in tables and instructions.
  • Provide parity in orchestration examples, such as Bash scripts or CLI commands for deploying script actions, not just PowerShell or .NET SDK.
  • Clarify that all management operations can be performed from Linux/macOS environments, and link to relevant cross-platform documentation.
  • Where PowerShell is mentioned, include equivalent Azure CLI commands.
GitHub Create Pull Request
Hdinsight Query data from HDFS-compatible Azure storage - Azure HDInsight ...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page lists Microsoft tools for accessing Azure Storage, including Azure PowerShell and AzCopy, with PowerShell being Windows-only and AzCopy supporting Windows and Linux but not macOS. The tools table lists Windows-specific tools (PowerShell) and places them after cross-platform tools, but does not provide Linux/macOS-specific alternatives or parity for PowerShell. There are no explicit Linux/macOS command-line examples for storage access outside the cluster, and the documentation does not mention Linux-native tools (e.g., s3cmd, rclone) or provide parity for PowerShell functionality. However, all in-cluster examples use bash and HDFS commands, which are platform-neutral and Linux-centric.
Recommendations
  • Provide Linux/macOS equivalents for Azure PowerShell tasks, such as Azure CLI or REST API commands.
  • Clarify AzCopy support for macOS and update the table if support exists.
  • List cross-platform tools first in the table, and clearly indicate platform limitations for each tool.
  • Include examples using Linux-native tools (e.g., rclone, s3cmd) for accessing Azure Storage outside the cluster.
  • Add explicit instructions or links for Linux/macOS users to perform tasks currently described only for Windows/PowerShell.
GitHub Create Pull Request
Hdinsight Manage logs for an HDInsight cluster - Azure HDInsight ...ob/main/articles/hdinsight/hdinsight-log-management.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. PowerShell and .NET SDKs are frequently mentioned for log management and job submission, often before or instead of Linux alternatives. Windows-centric tools like Visual Studio, Power Query for Excel, and Azure Storage Explorer are referenced for log analysis and management, while Linux-native tools and workflows (e.g., Bash scripting, Linux file utilities) are rarely mentioned or only referenced in passing. Some sections, such as scripting log archiving and accessing Azure Storage, provide PowerShell examples but lack equivalent Bash/CLI examples. Although Ambari and SSH access are covered for Linux-based clusters, overall, Linux/macOS users may need to infer or adapt instructions.
Recommendations
  • Provide Bash and Azure CLI examples alongside PowerShell for all scripting and automation tasks.
  • List Linux-native tools (e.g., grep, awk, sed, logrotate, cron) for log management and analysis, with usage examples.
  • Mention cross-platform tools first or equally (e.g., Azure CLI, AzCopy) before Windows-specific tools.
  • Include explicit instructions for Linux/macOS users for tasks currently described only with Windows tools (e.g., using Bash scripts for log archiving, accessing Azure Storage via CLI).
  • Add references to Linux/macOS compatible IDEs and utilities (e.g., VS Code, Jupyter, K9s) where appropriate.
GitHub Create Pull Request
Hdinsight Granular role-based access Azure HDInsight cluster configurations ...insight-migrate-granular-access-cluster-configurations.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio, PowerShell) are mentioned and described in detail, with PowerShell migration steps included as a dedicated section. Windows tools are listed before Linux/macOS alternatives (e.g., Azure CLI, SDKs), and PowerShell is the only shell scripting example provided. There are no Linux/macOS-specific command-line examples (e.g., Bash, shell scripts), nor is there mention of Linux-native management tools. However, the Azure CLI is documented, which is cross-platform, and SDKs for Python, Java, and Go are covered, mitigating the bias somewhat.
Recommendations
  • Add explicit Linux/macOS parity by including Bash or shell script examples for cluster management tasks.
  • Mention and document Linux-native tools (e.g., Azure CLI in Bash, cloud-init, or REST API usage from curl) where appropriate.
  • Reorder tool sections so cross-platform or Linux-first tools (Azure CLI, REST API, SDKs) are listed before Windows-only tools.
  • Provide migration steps and troubleshooting for Linux/macOS users, not just PowerShell/Windows users.
  • Clarify which tools and commands are cross-platform, and highlight any platform-specific limitations.
GitHub Create Pull Request
Hdinsight Azure HDInsight supported node configurations ...es/hdinsight/hdinsight-supported-node-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as a primary scripting tool for deploying HDInsight clusters and provides instructions for obtaining VM SKU identifiers specifically for use in PowerShell and scripts. There are no explicit Linux or Bash examples or mentions, and Windows-centric tools are referenced before any cross-platform alternatives.
Recommendations
  • Include examples and instructions for Bash/Azure CLI usage alongside PowerShell references.
  • Clarify that Azure CLI works on Linux/macOS and provide equivalent Linux/macOS command examples for obtaining SKU identifiers and deploying clusters.
  • Avoid presenting Windows/PowerShell tools as the default or only option; mention cross-platform alternatives first or equally.
  • Add a note or section for Linux/macOS users outlining any differences or considerations.
GitHub Create Pull Request
Hdinsight Troubleshoot a slow or failing job on Azure HDInsight cluster ...les/hdinsight/hdinsight-troubleshoot-failed-cluster.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While many troubleshooting steps are platform-neutral or reference Linux-based HDInsight clusters and Ambari UI (which is only available on Linux clusters), the initial guidance for gathering cluster details lists PowerShell as an option and references it before Linux equivalents. The mention of PowerShell and Azure CLI is present, but no explicit Linux shell or Bash examples are provided for cluster management tasks (other than troubleshooting WebHCat with curl and netstat). Additionally, the directory path for script action logs uses Windows-style backslashes, which may confuse Linux users. There is a lack of parity in examples for Linux users, especially for cluster management and log access outside of Ambari.
Recommendations
  • Provide explicit Bash or Linux shell examples for cluster management tasks, such as using Azure CLI from Bash or connecting via SSH to nodes.
  • Reference Linux tools and workflows (e.g., SSH, SCP, Bash scripts) alongside or before Windows/PowerShell equivalents.
  • Use platform-appropriate path separators (forward slashes for Linux) when describing file locations.
  • Clarify when instructions or tools are platform-specific, and offer alternatives for Linux/macOS users.
  • Add examples for accessing logs and managing clusters directly from Linux/macOS terminals.
GitHub Create Pull Request
← Previous Page 26 of 35 Next →