Closed santhosh-challa closed 3 weeks ago
Significant updates have been made to the database schema and Java code used in the PacBot application. The primary change involves replacing the usage of RESOURCE_ID
with DOC_ID
across various components for consistency and improved functionality. New constants were introduced, method implementations were improved for clarity, and a new procedure for updating flags was created.
File Path | Change Summary |
---|---|
installer/resources/pacbot_app/files/DB.sql |
Added _docid to cf_pac_updatable_fields , OmniSearch_Config , and pac_v2_ui_options . Created cf_UpdateFlag table and a procedure for updating based on flags. |
jobs/pacman-rule-engine-2.0/src/main/.../NotificationUtils.java |
Changed setResourceIdLink method to use DOC_ID instead of RESOURCE_ID . |
jobs/recommendation-enricher/src/main/java/.../RecommendationCollector.java |
Added new constants, refactored variable names, and made minor adjustments to method implementations for better readability and maintainability. |
sequenceDiagram
participant DB as Database
participant App as PacBot Application
participant Notify as NotificationUtils
participant Rec as RecommendationCollector
Note over DB, App: Initialization and Setup
DB->>DB: Update `cf_pac_updatable_fields` with `_docid`
DB->>DB: Update `OmniSearch_Config` and `pac_v2_ui_options` with `_docid`
DB->>DB: Create `cf_UpdateFlag` table & procedure
Note over App: Notification Process
Notify->>App: Construct resource link with `DOC_ID`
Note over Rec: Recommendation Process
Rec->>App: Use constants for IDs and doc types
Rec->>App: Improved logging and refactored variable names
Amidst the code where devs abide,
A bunny hops with joy and pride.
DOC_ID reigns over RESOURCE_ID's land,
To make PacBot’s queries ever so grand.
Tables are updated, flags are set,
Code now reads clearer, on that you can bet!
[!TIP]
AI model upgrade
## `gpt-4o` model for reviews and chat is now live OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our [Discord Community](https://discord.com/invite/GsXnASn26c) to provide any feedback or to report any issues.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Failed conditions
1 Security Hotspot
22.2% Duplication on New Code (required ≤ 10%)
Description
Problem
Currently, data is being fetched from Elastic using _resourceid. As _resourceid is not unique for assets globally, this causes data integrity issues
Solution
Migrated the data fetching mechanism to use _docid instead, which is globally unique for assets. This ensures that each asset is uniquely identified and resolves the data integrity issues.
Issues fixed in this PR:
_docid
_docid
for recommendations asset typeType of change
How Has This Been Tested?
It was tested in the saasdev by copying the jars. All the UI screens look good to me.
Checklist:
Other Information:
List any documentation updates that are needed for the Wiki
Summary by CodeRabbit
New Features
_docid
.Improvements
_docid
for better consistency and tracking.Bug Fixes
pac_v2_ui_options
by updating it based on flag status.Chores
_docid
changes.