Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty "merged" fields in github2_pull_request index #587

Open
canasdiaz opened this issue Apr 14, 2023 · 2 comments
Open

Empty "merged" fields in github2_pull_request index #587

canasdiaz opened this issue Apr 14, 2023 · 2 comments

Comments

@canasdiaz
Copy link
Contributor

canasdiaz commented Apr 14, 2023

The github2_pull_request index (which an alias) is not coherent, so it is not possible to show all the data for pull requests. As an example, the following fields are not filled for all the documents:

  • pull_merged
  • pull_merged_at

So, when using the index, it is not possible to show all the comments (both general and line comments) for merged pull requests. Find below an example of the analysis of this pull request

Screenshot 2023-04-14 1 51 54 PM

This behavior has been seen in grimoirelab/grimoirelab:0.7.1

@canasdiaz canasdiaz changed the title Empty merged fields in `github2_pull_request index Empty "merged" fields in github2_pull_request index Apr 14, 2023
@zhquan
Copy link
Member

zhquan commented Apr 14, 2023

@canasdiaz the alias github2_pull_request contains two indexes github2_issue (with filter issue_pull_request: true) and github2_pull_request. So only the comment from github2_pull_request will have the pull_merged_at field.

We need both of them because for GitHub only a review comment is a pull request comment but a simple comment is an issue comment even if it is in a pull request (remember that for GitHub a pull request is also an issue).

@canasdiaz
Copy link
Contributor Author

I understand what you say about the API. We should not forward the issues we have with the API to the customers. This is a wrong design decision, and it adds an unwanted limitation to the data analysis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants