Flink Dataset: Fine-Grained Code Changes (Diff-Level) Linked to Issue Descriptions for Software Traceability Analysis

Dataset: Apache Flink Commit–Task TraceabilityProject: apache/flink | Organization: Apache Software Foundation | Language: Java (.java .xml) 1. CONTEXT AND MOTIVATIONThis dataset supports research into traceability between task descriptions and code changes instateful stream-processing infrastructure. Apache Flink is a high-throughput, low-latencydistributed streaming and batch processing engine written primarily in Java. Its Apache Jiratracker uses structured identifiers (FLINK-NNNN) that are reliably referenced in commit messages.The project is notable for its strong European academic and industrial contributor base, offeringa different community dynamic compared to other Apache projects in this collection. This datasetwas previously analyzed in a related experiment (exp2) in its flink.db form. 2. COLLECTION METHODOLOGYSource: GitHub repository — https://github.com/apache/flinkCommits: Extracted via the GitHub API (all branches, full history)Task linking: Jira ticket references extracted from commit messages using the pattern FLINK-[0-9]+ ; each reference was resolved via the Apache Jira APIIssue content: Title, description, and comment thread fetched via Apache Jira REST API (https://issues.apache.org/jira/projects/FLINK) for each referenced ticketTime range: 2010-12-15 to 2024-10-31Anonymization: Author names and e-mail addresses replaced with sequential pseudonyms (User1, User2, …) prior to publication 3. DATASET STRUCTURETable COMMITS — one row per commit ID INTEGER Primary key SHA TEXT Full commit hash AUTHOR_NAME TEXT Anonymized author pseudonym (e.g. User42) AUTHOR_EMAIL TEXT Anonymized e-mail (e.g. [e-mail]) CMT_DATE TEXT Commit timestamp (ISO-8601 with timezone) MESSAGE BLOB Full commit message text PATH BLOB List of file paths changed in this commit DIFF BLOB Unified diff of the commit TASK_NAME TEXT Linked Jira ticket ID, e.g. FLINK-12345 (NULL if no link detected) Table TASK — one row per unique linked Jira ticket ID INTEGER Primary key (autoincrement) NAME TEXT Jira ticket ID (matches TASK_NAME in COMMITS) TITLE TEXT Issue summary as fetched from Jira DESCRIPTION TEXT Issue description body COMMENTS TEXT Serialized comment thread 4. BASIC STATISTICSTotal commits: 372,550Commits with linked task: 232,132 (62.3 %)Commits without linked task: 140,418 (37.7 %)Unique linked issues: 17,073Issues with description text: 14,977 (87.7 %)Unique authors (anonymized): 1,200Date range: 2010-12-15 — 2024-10-31