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

LCFS - Fix Missing Organizations in NiFi ETL (TFRS to LCFS) #1572

Open
5 tasks
AlexZorkin opened this issue Dec 31, 2024 · 1 comment
Open
5 tasks

LCFS - Fix Missing Organizations in NiFi ETL (TFRS to LCFS) #1572

AlexZorkin opened this issue Dec 31, 2024 · 1 comment
Assignees
Labels
High High priority ticket but not critical at this time Task Work that does not directly impact the user

Comments

@AlexZorkin
Copy link
Collaborator

Description:
The NiFi-based ETL process, which relies on a Groovy script to handle schema migration, failed to include all organizations from TFRS to LCFS. Several organizations did not appear in LCFS after running the pipeline. This ticket addresses the debugging, resolution, and verification of the issue to ensure complete data transfer.

Purpose and benefit to user:
Ensuring that LCFS accurately reflects the organizations contained in TFRS maintains data consistency and reliability across the system.

Acceptance Criteria:

  • Given the user is an ETL operator, when the pipeline runs, then all organizations from TFRS appear in LCFS.
  • Given the user is an ETL operator, when the fix is applied, then logs and verification reports confirm that no organizations remain missing in LCFS.

Development Checklist:

  • Identify the root cause of the missing organizations in the NiFi Groovy file.
  • Apply a fix to the Groovy script to capture all organizations from TFRS.
  • Test the updated pipeline with sample and production data to validate successful transfers.

Notes:
Validate any logs related to the NiFi process and confirm the presence of all expected organization records in LCFS.

@AlexZorkin AlexZorkin added High High priority ticket but not critical at this time Task Work that does not directly impact the user labels Dec 31, 2024
@prv-proton prv-proton self-assigned this Jan 2, 2025
@prv-proton
Copy link
Collaborator

When tested on local all organizations were loaded. May require re-implementation after clearing all data in the database. Based on it further work can be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High High priority ticket but not critical at this time Task Work that does not directly impact the user
Projects
None yet
Development

No branches or pull requests

2 participants