Restore Changes to load_mongodump.sh and Sync with em-public-dashboard
#158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Please add details of the testing done. |
**Overview**
Enhances the user profile data retrieval process by incorporating newly
stored statistics (`pipeline_range`, `total_trips`, `labeled_trips`, and
`last_call`) into the existing `with` block. These statistics are now
seamlessly integrated into the `user` dictionary, providing a more
comprehensive set of user metrics for further analysis and dashboard
visualization.
1. **Enhanced Profile Data Retrieval**
- **Existing Functionality**:
- The `with` block previously retrieved basic profile information such as `platform`, `manufacturer`, `app_version`, `os_version`, and `phone_lang` from the database and assigned them to the `user` dictionary.
- **New Enhancements**:
- **Pipeline Range**:
- Retrieved `pipeline_range` data, including `start_ts` and `end_ts`, to understand the timeframe of the user's activity pipeline.
- **Trip Counts**:
- Extracted `total_trips` and `labeled_trips` to provide insights into the user's trip data and the extent of trip labeling.
- **Last API Call Timestamp**:
- Obtained `last_call` to track the most recent API interaction by the user.
- **Optional Formatting**:
- Included a formatted version of the `last_call` timestamp for better readability in reports and dashboards.
2. **Updated `with` Block Structure**
- **Integration of New Statistics**:
- The `with` block now not only fetches and assigns basic profile attributes but also retrieves and assigns the newly stored statistics from the database.
Additional commits squashed into this:
- Accidentally removed the process loop
- Simplified else block for user data
- Merge
- Addressed comment, modified else if block
- Updated COLS to be uniform like the other constants. Updated ADD USER STATS
…ose.dev.yml from EM-Dash; Restore previous load_mongodump script that was purged from commit cleaning
TeachMeTW
force-pushed
the
Restore-Load-Dump
branch
from
7a34aee to
fb105c9
Compare
|
@shankari Addressed and added testing procedure |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Restores the changes made to the
docker/load_mongodump.shfile that seem to have been overwritten during a rebase.Additionally, this PR incorporates the necessary changes from e-mission/em-public-dashboard#163, ensuring consistency across repositories and minimizing the need for manual edits in the future.
Changes
load_mongodump.sh.em-public-dashboardto address op-admin-dashboard#122 (comment).Related Issues
Testing
Example
Loaded a script via
./load_mongodump.sh <file>, for example:./load_mongodump.sh ~/Downloads/openpath_prod_stm_commute.tar.gzThe script loaded properly with no errors and displayed:
Database restore complete.The docker-compose file was also updated.
