hpcc-systems / hpcc-systems/DataPatterns
Request: Easy method for analyzing different profiling results
Nobody has claimed this yet.
- Dominant language
- ECL
- Stars
- 5
- Forks
- 5
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Satisfy this scenario: Profiling is used to analyze new data that will be ingested. Profiling results are saved as a logical file. Then, a new batch of data arrives and is profiled. The new method should compare the new profiling results with the old and output a summary of any differences.
The end goal is to highlight significant differences between the two profiles, which could indicate a significant or unexpected change in the incoming data stream.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing data-profiling functionality and how profiling results are saved as logical files; no specific file, test, or entry point is named. Done means a new profiling result can be compared with the saved result and a summary of significant differences is produced.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100