Skip to content

Deprecate psqlgraph (sheepdog) #24

@bwalsh

Description

@bwalsh
  • Introduction: We are announcing the deprecation of the psqlgraph (sheepdog) database, effective [release X]. This decision is based on its low adoption and usage among our user base.

  • Reasoning: After careful review and consideration, it has become evident that the psqlgraph (sheepdog) database has not gained significant traction or usage since its introduction. It is not used by the front-end-framework and is limited in its ability to support deep analysis queries (see replacement with grip)

  • Impact: Deprecating the psqlgraph (sheepdog) database will allow us to streamline our development efforts and allocate resources more efficiently towards enhancing core functionalities that are more widely used and valued by our users.

  • Timeline: The deprecation process will follow a phased approach:

    • Starting [release X], the psqlgraph (sheepdog) database will no longer receive updates or enhancements (loaded with data).
    • Support for the psqlgraph (sheepdog) database will officially end on [release X].
  • Transition Plan: None. No one is using it.

Migration Plan to Deprecate Feature

Verify no calls from front end framework

  • In a development environment, shutdown the peregrine service. Verify portal works as expected.

Changes required for client code (g3t):

  • Deprecate the g3t projects create command. Update documentation.

Modification to aced_submission meta graph load:

  • Deprecate to do nothing for now, eventually this will be replaced with loading a the Grip query engine. Implement Grip #26

Next Steps

  • Testing and Validation: Conduct thorough testing of all modifications and new implementations across various environments to ensure compatibility and functionality.

    • Verify the end to end process of creating a new project, loading data and files, adding users, updating data etc.
  • Monitoring and Support: Implement monitoring mechanisms post-deployment to track performance and user feedback. Provide ongoing support for any issues or questions that arise during the transition period.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions