[SUPPORT]

[Sheth-G]

Tips before filing an issue

• Have you gone through our FAQs?

• Join the mailing list to engage in conversations and get faster support at dev-subscribe@hudi.apache.org.

• If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced

A clear and concise description of the problem.

To Reproduce

Steps to reproduce the behavior:

1. 2. 3. 4.

Expected behavior

A clear and concise description of what you expected to happen.

Environment Description

• Hudi version :

• Spark version :

• Hive version :

• Hadoop version :

• Storage (HDFS/S3/GCS..) :

• Running on Docker? (yes/no) :

Additional context

Add any other context about the problem here.

Stacktrace

Add the stacktrace of the error.

[torvalds-dev[bot]]

torvalds.dev is analyzing the ticket

[torvalds-dev-testbot[bot]]

torvalds.dev is analyzing the ticket

[torvalds-dev[bot]]

The task you've provided is to understand the issue template and suggest relevant actions that should be taken, as well as provide the names of files that are relevant to the issue.

The issue template you've provided is a standard one used in many open-source projects. It's designed to help contributors provide all the necessary information when they encounter a problem.

Here's a breakdown of the sections in the issue template:

1. Describe the problem you faced: This is where the user should provide a detailed explanation of the problem they encountered. The more specific they can be, the easier it will be for others to understand and help solve the problem.

2. To Reproduce: This section is for providing a step-by-step guide on how to reproduce the issue. This is crucial for others to understand and replicate the problem.

3. Expected behavior: Here, the user should describe what they expected to happen, which helps others understand what the user thinks is going wrong.

4. Environment Description: This section is for providing details about the user's environment, such as the versions of Hudi, Spark, Hive, Hadoop they're using, the type of storage they're using (HDFS/S3/GCS..), and whether they're running on Docker. This information can be very helpful in diagnosing the problem.

5. Additional context: Any other information that the user thinks might be helpful can go here.

6. Stacktrace: If there's an error message, it should be included here.

The file you've mentioned, .github/PULL_REQUEST_TEMPLATE.md, is a template for pull requests, not issues. It's used when someone wants to contribute code to the project. It includes sections for describing the changes made, the impact of those changes, the risk level, any necessary documentation updates, and a checklist for the contributor to ensure they've met all the requirements for contributing.

Based on the information provided, the actions that should be taken are:

1. If you're facing an issue, fill out the issue template with as much detail as possible and submit it to the project's issue tracker.

2. If you're contributing code, fill out the pull request template and submit it along with your code.

The relevant files are the issue template (which is usually found in the project's root directory or in a .github directory) and the pull request template (which is usually found in the same places).