Skip to content

[DRAFT] Feat: Add deepchem server datastore service#52

Draft
vsaravind01 wants to merge 37 commits intomainfrom
deepchem-datastore
Draft

[DRAFT] Feat: Add deepchem server datastore service#52
vsaravind01 wants to merge 37 commits intomainfrom
deepchem-datastore

Conversation

@vsaravind01
Copy link
Copy Markdown
Collaborator

Description

Added deepchem-server datastore service.

Type of change

Please check the option that is related to your PR.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • In this case, we recommend to discuss your modification on GitHub issues before creating the PR
  • Documentations (modification for documents)

Checklist

  • Run lint.sh and ensure that it passes (Use ./lint.sh --fix to fix formatting issues automatically)
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New unit tests pass locally with my changes
  • I have checked my code and corrected any misspellings

- Cleaned up import statements across core modules for better readability and organization.
- Introduced a standalone DeepchemDatastore service with a REST API for file storage operations.
- Implemented CRUD operations in the DatastoreService, allowing for efficient data management.
- Added API key authentication for secure access to the datastore service.
- Created a client for interacting with the datastore service, facilitating easy data uploads and retrievals.
- Included Docker support for the datastore service, streamlining deployment and management.
…datastore tests, improving test organization and clarity.
…worker service, and remove `isort` from linting.
Align datastore client/server behaviors (list filtering, directory handling, and move support) and tighten up the service entrypoint reload behavior.
Use datastore list-all filtering for checkpoint discovery and correct checkpoint directory deletion so featurization restart works against the HTTP-backed datastore.
Start a demo datastore service for core tests and wipe its storage between tests to avoid cross-test key collisions (FileExistsError) while keeping the code changes limited to the test suite.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant