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 601-625 of 867 flagged pages
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-14 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 demonstrates a moderate Windows bias. PowerShell is mentioned as a management option, but Linux equivalents (such as Bash or SSH) are not referenced in parallel. The mention of PowerShell comes before any explicit Linux command-line examples. The directory path for script action logs uses backslashes (Windows style), and there is no explicit Linux CLI or SSH example for cluster management or log access. While the Ambari UI is described (which is available on Linux-based clusters), the CLI troubleshooting steps and examples are not balanced between Windows and Linux. The Azure CLI is mentioned, but PowerShell is highlighted as an alternative, with no mention of Bash or SSH for Linux users. Some examples (e.g., curl, netstat) are Linux-friendly, but overall, Windows tools and patterns are referenced first or exclusively in some sections.
Recommendations
  • Provide Linux/Bash/SSH equivalents alongside PowerShell examples for cluster management and troubleshooting.
  • Use forward slashes for directory paths, or clarify the path format for both Windows and Linux.
  • Explicitly mention how Linux/macOS users can access logs, run commands, and manage clusters using native tools.
  • When listing tools (Azure CLI, PowerShell), present them in parallel and clarify platform applicability.
  • Add troubleshooting examples using Bash scripts or Linux command-line utilities where appropriate.
GitHub Create Pull Request
Hdinsight Converting certificate contents to base-64 - Azure HDInsight ...-troubleshoot-converting-service-principal-certificate.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 Missing Linux Example Windows First
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 macOS command-line examples (e.g., using openssl or base64), and Windows tools are mentioned exclusively.
Recommendations
  • Add Linux/macOS command-line examples using openssl and base64 utilities.
  • Explicitly mention that the conversion can be done on any OS, not just Windows.
  • Reorder examples or provide platform-specific tabs for Windows, Linux, and macOS.
  • Reference cross-platform tools (e.g., Python script) that work on all major OSes.
GitHub Create Pull Request
Hdinsight Use Curl to export data with Apache Sqoop in Azure HDInsight ...icles/hdinsight/hadoop/apache-hadoop-use-sqoop-curl.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 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by providing only Windows command prompt examples (using 'set' for environment variables and Windows-style variable substitution), referencing Windows-specific jq executable paths, and omitting equivalent Linux/macOS shell examples. The instructions and examples are tailored to Windows users, leaving Linux/macOS users to infer necessary changes for their environments.
Recommendations
  • Add parallel Linux/macOS shell examples using 'export' for environment variables and '$VAR' for variable substitution.
  • Show how to invoke jq on Linux/macOS (e.g., 'jq .status.state' instead of referencing a Windows path).
  • Explicitly state differences in command syntax and environment setup for Linux/macOS users.
  • Consider presenting Linux/macOS examples first or side-by-side with Windows examples to improve parity.
GitHub Create Pull Request
Hdinsight C#, Apache Hive & Apache Pig on Apache Hadoop - Azure HDInsight ...ght/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio, for building C# UDFs. All project creation, build, and upload steps are described using Visual Studio UI and features, with no guidance for Linux/macOS users or command-line alternatives. While the cluster itself is Linux-based, the development workflow assumes Windows and Visual Studio, creating friction for non-Windows users.
Recommendations
  • Provide instructions for building C# projects using cross-platform tools such as the 'dotnet' CLI and MonoDevelop, including command-line build steps.
  • Include examples for uploading .exe files using Azure CLI, PowerShell, or direct web portal, not just Visual Studio.
  • Mention alternative IDEs (e.g., JetBrains Rider, VS Code with C# extensions) and clarify that Visual Studio is optional.
  • Reorder or parallelize instructions so that Linux/macOS development workflows are presented alongside Windows/Visual Studio steps.
  • Add explicit notes or sections for Linux/macOS users, including any required Mono compatibility steps.
GitHub Create Pull Request
Hdinsight Install third-party applications on Azure HDInsight ...icles/hdinsight/hdinsight-apps-install-applications.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 page exclusively describes installing third-party applications on Azure HDInsight using the Azure portal, with references to Azure PowerShell and Azure Classic CLI for template deployment, but does not provide Linux-specific CLI examples or mention cross-platform tools (e.g., Azure CLI). The instructions and screenshots are portal-centric, which is more familiar to Windows users. There is no explicit guidance for Linux/macOS users on how to perform these tasks using their native tools or environments.
Recommendations
  • Add Azure CLI examples for installing and managing HDInsight applications, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Include instructions for using SSH and scripting (e.g., Bash) to interact with HDInsight clusters, especially for application installation and management.
  • Clarify that the Azure portal and PowerShell are available on all platforms, but highlight cross-platform alternatives where possible.
  • Provide side-by-side examples for common operations (install, list, delete) using both PowerShell and Azure CLI.
  • Mention and link to documentation for Linux/macOS-specific workflows, such as using Bash scripts or automation tools.
GitHub Create Pull Request
Hdinsight Add additional Azure Storage accounts to HDInsight ...ain/articles/hdinsight/hdinsight-hadoop-add-storage.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 documentation provides a detailed PowerShell script for verifying storage account addition, but does not offer equivalent Linux/macOS CLI or shell examples. PowerShell is presented as the primary verification method, with no Bash, Azure CLI, or Linux-native alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell.
Recommendations
  • Add equivalent verification steps using Bash and Azure CLI, suitable for Linux/macOS environments.
  • Present cross-platform examples side-by-side or in parallel sections, rather than PowerShell-first.
  • Clarify that PowerShell is optional and provide guidance for users on other operating systems.
  • Include sample commands for inspecting core-site.xml directly on the cluster via SSH (Linux shell).
GitHub Create Pull Request
Hdinsight Use Livy Spark to submit jobs to Spark cluster on Azure HDInsight ...es/hdinsight/spark/apache-spark-livy-rest-interface.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 page demonstrates a Windows bias by providing environment variable setup and input file usage examples specifically for Windows (e.g., using 'set' and 'C:\Temp\input.txt'), with no equivalent Linux/macOS instructions. The examples and guidance assume a Windows environment, and Linux/macOS users are left to infer necessary changes. While the core curl commands are cross-platform, critical setup steps are Windows-centric.
Recommendations
  • Provide parallel examples for Linux/macOS, such as using 'export' for environment variables and '~/input.txt' for file paths.
  • Explicitly state cross-platform differences in sections that currently mention only Windows (e.g., input file usage, environment variable setup).
  • Add a note or table summarizing command differences between Windows and Linux/macOS.
  • Ensure that instructions do not recommend Windows-specific approaches (like input files at C:\Temp) as the default without alternatives.
GitHub Create Pull Request
Hdinsight Azure Monitor Agent (AMA) migration guide for Azure HDInsight clusters ...cs/blob/main/articles/hdinsight/azure-monitor-agent.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 page demonstrates a moderate Windows bias. The PowerShell approach is presented before the Azure CLI approach, and all scripting examples for PowerShell use Windows-centric tools and cmdlets. The only explicit mention of a required tool is 'azcopy', which is cross-platform, but the PowerShell examples dominate and are shown before CLI. There is no mention of Linux-specific shell scripting, nor are there Bash or Linux-native examples for enabling the agent or managing DCRs. The CLI approach does use Bash syntax and references 'jq', but the overall flow and examples are still more Windows/PowerShell oriented.
Recommendations
  • Present Azure CLI (Bash/Linux) examples before or alongside PowerShell examples to promote parity.
  • Include explicit Bash/Linux shell script examples for all major steps, especially for enabling MSI, creating DCRs, and associating DCRs.
  • Clarify that all CLI commands work on Linux/macOS and provide troubleshooting notes for common Linux issues (e.g., permissions, jq installation).
  • Mention Linux-native tools (e.g., curl, wget) as alternatives to azcopy for downloading files.
  • Add a table or section comparing PowerShell and Bash/CLI workflows for each major migration step.
GitHub Create Pull Request
Hdinsight Reboot VMs for Azure HDInsight clusters ...docs/blob/main/articles/hdinsight/cluster-reboot-vm.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 documentation page provides detailed instructions for rebooting HDInsight cluster VMs using PowerShell, which is a Windows-centric tool, and lists this method before the REST API approach. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or other cross-platform tools. The REST API section is more neutral, but the absence of Linux-specific instructions or parity for command-line usage creates friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for listing and restarting HDInsight cluster nodes, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for interacting with the REST API, demonstrating how Linux/macOS users can perform the same operations.
  • Explicitly mention platform compatibility for each method, and recommend cross-platform tools where possible.
  • Reorder sections so that cross-platform or platform-neutral methods (like REST API or Azure CLI) are presented before Windows-specific tools like PowerShell.
GitHub Create Pull Request
Hdinsight Double encryption for data at rest ...e-docs/blob/main/articles/hdinsight/disk-encryption.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 moderate Windows bias. PowerShell is used for several key examples (ARM template deployment, enabling encryption at host), and Windows-centric tools (PowerShell cmdlets) are referenced for recovery and operations. Linux/macOS equivalents (e.g., Bash, shell scripting) are missing for ARM template deployment and disk encryption operations. Windows/PowerShell examples are often presented before or instead of Linux alternatives, and there is no explicit parity for Linux command-line workflows.
Recommendations
  • Provide Bash or shell script examples for ARM template deployment and disk encryption operations, especially for Linux/macOS users.
  • Include explicit instructions or examples using Azure CLI or REST API for all operations currently shown only in PowerShell.
  • Reference Linux-native tools and workflows where possible (e.g., az CLI, curl, jq) and clarify cross-platform compatibility.
  • Ensure that recovery operations (e.g., key recovery) include both PowerShell and CLI commands, with equal prominence.
  • Where UI screenshots are shown, clarify that the Azure portal is OS-agnostic.
GitHub Create Pull Request
Hdinsight Use C# with MapReduce on Hadoop in HDInsight - Azure ...oop/apache-hadoop-dotnet-csharp-mapreduce-streaming.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 exhibits a moderate Windows bias. Visual Studio (Windows-centric) is the only development environment mentioned for building C# applications, and the upload instructions rely on Data Lake Tools for Visual Studio. PowerShell is featured as the only scripted automation example. Linux parity is present in the job submission section, which uses SSH and Bash commands, but the overall workflow assumes Windows tools and patterns first.
Recommendations
  • Include instructions for building C# applications using cross-platform tools such as dotnet CLI and MonoDevelop, targeting Linux/macOS users.
  • Provide alternative upload methods (e.g., Azure CLI, azcopy, or Hadoop fs commands) for transferring files to HDInsight storage from Linux/macOS.
  • Add a Bash or Python example for automating job submission and result retrieval, alongside the PowerShell script.
  • Clarify that Visual Studio is optional and suggest cross-platform alternatives for development and deployment.
GitHub Create Pull Request
Hdinsight Azure HDInsight architecture with Enterprise Security Package ...ght/domain-joined/apache-domain-joined-architecture.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples are provided exclusively in PowerShell, with no Linux/macOS shell equivalents. The instructions assume the use of Windows-centric tools (PowerShell modules, Active Directory, Microsoft Entra Domain Services), and do not mention or provide guidance for Linux-native approaches or tooling. The documentation also presents Windows/Active Directory concepts first and exclusively, without discussing alternatives or parity for Linux environments.
Recommendations
  • Provide equivalent command-line instructions using Bash/CLI for Linux/macOS users, especially for authentication and service principal management.
  • Clarify whether tasks (such as setting HRD policies) can be performed using Azure CLI or REST API, and provide those examples.
  • Explicitly state platform requirements and limitations, and offer guidance for Linux users where possible.
  • Add notes or sections addressing how Linux/macOS administrators can interact with HDInsight and Microsoft Entra Domain Services, including any required tools or workarounds.
GitHub Create Pull Request
Hdinsight Apache Hive policies in Apache Ranger - Azure HDInsight ...insight/domain-joined/apache-domain-joined-run-hive.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 notable Windows bias by focusing exclusively on connecting to Hive via Excel and the Microsoft Hive ODBC driver, both of which are Windows-centric tools. All example workflows and screenshots are based on Excel, with no mention of Linux/macOS alternatives (such as using Beeline, DBeaver, or other cross-platform database clients). The instructions for data import and policy testing are tailored for Windows environments, and Linux/macOS users are not provided with equivalent steps or guidance.
Recommendations
  • Add instructions and examples for connecting to Hive from Linux/macOS using common tools such as Beeline, DBeaver, or SquirrelSQL.
  • Include sample workflows for testing Ranger policies using command-line Hive clients (e.g., Beeline or Hive CLI) on Linux/macOS.
  • Provide parity in screenshots and step-by-step guides for at least one cross-platform tool.
  • Clarify in prerequisites and throughout the document which steps are Windows-specific, and offer alternatives for other platforms.
GitHub Create Pull Request
Hdinsight Configure clusters for Microsoft Entra integration ...ned/apache-domain-joined-configure-using-azure-adds.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 only command-line example for creating a self-signed certificate uses PowerShell, with no Linux or cross-platform alternative. Network validation steps recommend joining a Windows VM to the domain and using Windows-specific tools (ldp.exe) for testing, without mentioning Linux/macOS equivalents. The guidance for domain joining and troubleshooting is Windows-centric, and Windows tools are mentioned before any Linux options. There are no Linux/macOS command-line examples for certificate creation, domain validation, or network testing.
Recommendations
  • Provide equivalent Linux/macOS commands for creating self-signed certificates (e.g., using openssl).
  • Include instructions for domain validation and network testing using Linux tools (e.g., ldapsearch, dig, nslookup).
  • Mention cross-platform alternatives to ldp.exe and clarify how Linux/macOS users can perform required checks.
  • Ensure examples and troubleshooting steps are presented for both Windows and Linux/macOS environments, or at least reference external guides for non-Windows users.
  • Where possible, present platform-neutral steps first, or in parallel, rather than defaulting to Windows.
GitHub Create Pull Request
Hdinsight Manage Enterprise Security Package clusters - Azure HDInsight ...hdinsight/domain-joined/apache-domain-joined-manage.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 moderate Windows bias by referencing Windows-centric tools (Visual Studio Code, Visual Studio Tools, Power BI, Excel), and listing them before or instead of Linux/macOS alternatives. There are no explicit Linux/macOS-specific instructions or examples, and some tools mentioned (e.g., Visual Studio Tools, Power BI) are primarily Windows-based. No PowerShell commands are shown, but the lack of Linux/macOS parity in tooling and examples creates friction for non-Windows users.
Recommendations
  • Include Linux/macOS-specific instructions or notes for connecting to clusters using common tools available on those platforms (e.g., VS Code on Linux/macOS, DataGrip, DBeaver, or other cross-platform SQL clients).
  • When mentioning tools like Visual Studio Tools or Power BI, clarify their platform support and suggest cross-platform alternatives where possible.
  • Provide explicit command-line examples (e.g., using Beeline, curl, or SSH) that work on Linux/macOS, not just GUI-based or Windows-centric tools.
  • Ensure that any references to prerequisites or linked guides also include Linux/macOS setup steps.
  • Consider reordering lists or tables so that cross-platform or Linux-native tools are not always listed after Windows tools.
GitHub Create Pull Request
Hdinsight LDAP sync in Ranger and Apache Ambari in Azure HDInsight ...lob/main/articles/hdinsight/domain-joined/ldap-sync.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 exhibits Windows bias by referencing Windows-specific tools (e.g., ldp.exe, sAMAccountName, Samba/Winbind) and suggesting their use for LDAP filter testing. There are no Linux-specific examples or equivalent Linux tools mentioned for LDAP filter testing, and Windows terminology is used throughout. The guidance assumes familiarity with Windows-centric patterns and does not provide parity for Linux/macOS users.
Recommendations
  • Include Linux command-line examples for LDAP filter testing, such as using ldapsearch or other open-source LDAP clients.
  • Mention Linux equivalents for Windows tools like ldp.exe (e.g., ldapsearch, Apache Directory Studio).
  • Clarify the role of Samba/Winbind and provide guidance for clusters where these may not be present or for non-Windows environments.
  • Present examples and instructions for both Windows and Linux environments in parallel, rather than defaulting to Windows terminology and tools.
  • Add notes or sections addressing macOS users where relevant.
GitHub Create Pull Request
Hdinsight Apache Ambari heartbeat issues in Azure HDInsight .../hadoop/apache-ambari-troubleshoot-heartbeat-issues.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 provides troubleshooting steps for Apache Ambari heartbeat issues in Azure HDInsight. While most examples use Linux-style commands (bash, service, ps, top), the section on disabling Azure Monitor logging only references the Windows PowerShell cmdlet (Disable-AzHDInsightMonitoring) and does not mention an equivalent Linux/CLI method. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI tools.
Recommendations
  • Include Azure CLI or REST API equivalents for disabling Azure Monitor logging, alongside the PowerShell cmdlet.
  • Explicitly state whether the PowerShell cmdlet is available cross-platform, or provide instructions for Linux/macOS users.
  • Present cross-platform solutions in parallel, or list Linux/CLI methods first if the majority of users are on Linux.
  • Add notes clarifying platform-specific steps and alternatives.
GitHub Create Pull Request
Hdinsight Overview of enterprise security in Azure HDInsight ...hdinsight/domain-joined/hdinsight-security-overview.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 page demonstrates a moderate Windows bias. It references Active Directory and Microsoft Entra Domain Services as the primary authentication mechanism, which are Windows-centric technologies. PowerShell is mentioned as a client tool for cluster authentication, but no equivalent Linux/macOS command-line tools (such as SSH, curl, or Linux-specific CLI examples) are provided. The documentation does not explicitly mention Linux authentication patterns or tools, nor does it provide examples for Linux/macOS users. The focus on Windows-based enterprise security patterns (Active Directory, PowerShell) may create friction for Linux/macOS users seeking parity.
Recommendations
  • Include authentication examples using Linux/macOS tools (e.g., SSH, curl, REST API via curl, JDBC/ODBC from Linux clients).
  • Mention and provide guidance for integrating with non-Windows identity providers or LDAP, if supported.
  • List Linux/macOS equivalents alongside PowerShell in client tool references.
  • Clarify whether all features (such as ESP, Ranger, Ambari) are fully supported and documented for Linux/macOS users.
  • Add explicit notes or sections for Linux/macOS users where workflows differ from Windows.
GitHub Create Pull Request
Hdinsight Extract, transform, and load (ETL) at scale - Azure HDInsight ...rticles/hdinsight/hadoop/apache-hadoop-etl-at-scale.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, particularly in the 'Ingest file storage and result storage' section. Data ingestion into Azure Storage is described as typically done via PowerShell, Azure Storage SDK, or AzCopy, with no mention of Linux/macOS equivalents or CLI tools (e.g., Bash, Azure CLI, REST API). Windows tools and patterns (PowerShell, AzCopy) are mentioned first and exclusively in some places, while Linux-friendly alternatives are only referenced for Data Lake Storage (DistCp, Sqoop) and not for Blob Storage. This may create friction for Linux/macOS users who need to ingest data into Azure Blob Storage.
Recommendations
  • Include Linux/macOS-friendly ingestion methods for Azure Blob Storage, such as Azure CLI, Bash scripts, REST API, or third-party tools.
  • Present ingestion options for both Windows and Linux/macOS platforms side-by-side, rather than listing Windows tools first or exclusively.
  • Clarify which tools are cross-platform (e.g., AzCopy is available for Linux/macOS) and provide installation/use instructions for those platforms.
  • Add explicit examples for Linux/macOS users, especially for common ingestion scenarios.
  • Review other sections for similar patterns and ensure parity in tool recommendations and examples.
GitHub Create Pull Request
Hdinsight Java user-defined function (UDF) with Apache Hive Azure HDInsight ...ticles/hdinsight/hadoop/apache-hadoop-hive-java-udf.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 demonstrates a notable Windows bias: all initial setup, file creation, and editing commands use Windows-specific tools (cmd.exe, Notepad, PowerShell). The test environment is explicitly Windows 10, and Linux/macOS equivalents for directory creation, file editing, and line ending fixes are not provided. Linux commands only appear after the user has already SSHed into the cluster.
Recommendations
  • Provide parallel Linux/macOS shell commands (e.g., mkdir, cd, rm -rf, nano/vim) alongside Windows cmd.exe commands.
  • Mention cross-platform editors (e.g., VS Code, nano, vim) instead of only Notepad.
  • Offer Linux/macOS solutions for line ending conversion (e.g., dos2unix, sed) instead of only PowerShell.
  • Clarify that the instructions are cross-platform and provide explicit notes or tabs for Windows and Linux/macOS users.
  • Consider using a neutral test environment or at least mention both Windows and Linux/macOS as supported environments.
GitHub Create Pull Request
Hdinsight Infrastructure: On-premises Apache Hadoop to Azure HDInsight ...op-on-premises-migration-best-practices-infrastructure.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 documentation page exhibits Windows bias primarily in the 'Customize HDInsight configs using Bootstrap' section, where only PowerShell (Windows-centric) examples are provided for cluster configuration. There are no equivalent Bash, CLI, or Linux-native examples, and the PowerShell approach is presented as the default method. Other sections are generally platform-neutral or reference Linux edge nodes, but the lack of Linux/macOS command-line examples for critical configuration tasks creates friction for non-Windows users.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for customizing HDInsight configs, especially for tasks currently shown only in PowerShell.
  • Explicitly mention platform support and alternatives (e.g., CLI, REST API) for all major operations.
  • Ensure that Linux/macOS instructions are presented alongside or before Windows/PowerShell instructions for parity.
  • Add links to official Azure CLI documentation for HDInsight management.
GitHub Create Pull Request
Hdinsight Use MapReduce and Curl with Apache Hadoop in HDInsight - Azure ...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.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 demonstrates a notable Windows bias: command examples use Windows-specific syntax (cmd 'set' commands, caret '^' line continuations, Windows paths for jq), and PowerShell is presented as a primary alternative. There are no explicit Linux/macOS shell examples, and instructions for adapting commands to Unix environments are minimal or absent. The use of Windows tools and patterns (e.g., C:\HDI\jq-win64.exe, PowerShell) may confuse or hinder Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS shell examples for all curl commands, using export for environment variables, backslash '\' for line continuation, and typical Unix jq paths (e.g., /usr/bin/jq).
  • Add a dedicated section for Bash/Zsh usage, including variable setting, command syntax, and output parsing.
  • Mention Linux/macOS alternatives before or alongside Windows tools, not after.
  • Clarify any platform-specific differences in command syntax and tool usage.
  • Include notes or tables summarizing differences between Windows and Linux/macOS command-line environments.
GitHub Create Pull Request
Hdinsight Using Apache Hive as an ETL Tool - Azure HDInsight ...doop/apache-hadoop-using-apache-hive-as-an-etl-tool.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 Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (SQL Server Integration Services, Excel, PowerShell) and patterns (ODBC driver for Excel/C#) before mentioning Linux-friendly alternatives. Linux/macOS equivalents (e.g., Sqoop, Oozie) are mentioned but not emphasized or exemplified. There are no explicit Linux command-line examples, and automation is suggested via PowerShell and Logic Apps, with no mention of Bash, cron, or Linux-native scheduling/orchestration. This may create friction for Linux/macOS users seeking parity.
Recommendations
  • Provide Linux/macOS command-line examples for Hive ETL tasks (e.g., Bash scripts, hive CLI usage).
  • Mention and exemplify Linux-native orchestration tools (e.g., cron, Airflow, Oozie) alongside PowerShell and Logic Apps.
  • List Linux-friendly data loading tools (e.g., Sqoop, Python scripts) before or alongside Windows tools like SSIS.
  • Include examples for connecting to Hive from Linux/macOS clients (e.g., Python, JDBC, shell).
  • Balance references to Excel/ODBC/C# with open-source or cross-platform alternatives.
GitHub Create Pull Request
Hdinsight Unable to access Data Lake storage files in Azure HDInsight ...sight/hadoop/hdinsight-troubleshoot-data-lake-files.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 Missing Linux Example Windows First
Summary
The documentation provides a detailed PowerShell script for certificate management, which is a Windows-centric tool, without offering equivalent Linux/macOS instructions. There are no Bash, Azure CLI, or cross-platform alternatives for certificate creation, management, or cluster update. The guidance assumes access to PowerShell and Windows tools, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent instructions using Azure CLI or Bash scripts for certificate creation and management.
  • Include examples for updating cluster identity certificate using cross-platform tools.
  • Explicitly mention platform requirements for each method and suggest alternatives for non-Windows users.
  • Reorder examples to present cross-platform or Linux/macOS options before or alongside Windows/PowerShell solutions.
GitHub Create Pull Request
Hdinsight What is Apache Hive and HiveQL - Azure HDInsight ...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.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 lists several ways to use Hive with HDInsight, including Windows-specific tools (Visual Studio, PowerShell) and mentions them explicitly. Windows tools are given dedicated rows in the usage table, and PowerShell is listed as a method for batch processing, but there is no equivalent Linux shell example. The UDF section includes a C# example, which is Windows-centric. The scheduling section gives prominence to SQL Server Integration Services (SSIS), a Windows-only tool, before mentioning Apache Oozie, which is cross-platform. While Linux/macOS options are present (VS Code, Beeline, REST API, Oozie), Windows-specific tools are highlighted and sometimes listed before cross-platform alternatives.
Recommendations
  • Add explicit Linux shell (bash) examples for running Hive queries, similar to the PowerShell example.
  • Provide parity in tooling examples, such as mentioning IntelliJ IDEA or Eclipse for Hive development on Linux/macOS alongside Visual Studio.
  • Reorder sections so that cross-platform or browser-based tools (VS Code, Beeline, Hive View) are listed before Windows-only tools.
  • Include Linux/macOS alternatives for scheduling (e.g., cron jobs, Airflow) alongside SSIS.
  • Add more examples using Python or Java UDFs, which are cross-platform, and avoid highlighting C#/.NET as the primary example.
GitHub Create Pull Request
← Previous Page 25 of 35 Next →