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

Add job related methods to QiskitRuntimeLocalService #1607

Open
jyu00 opened this issue Apr 11, 2024 · 0 comments · May be fixed by #1854
Open

Add job related methods to QiskitRuntimeLocalService #1607

jyu00 opened this issue Apr 11, 2024 · 0 comments · May be fixed by #1854
Assignees
Labels
enhancement New feature or request

Comments

@jyu00
Copy link
Collaborator

jyu00 commented Apr 11, 2024

What is the expected feature or enhancement?

QiskitRuntimeLocalService was created to support local testing mode and is meant to be similar to QiskitRuntimeService. The initial release of QiskitRuntimeLocalService only has the run() method, and we immediately got feedback asking for the other methods 🙂.

This issue is about adding job related methods to QiskitRuntimeLocalService. This is more involved since job data (e.g. results) would need to be stored locally on disk. So to support this, we'd need a design on

  1. Where to store the data. This should be user-configurable and the default can be current working directory.
  2. When to delete the data. This should be user-configurable and the default can be 30 days.
  3. Job id to data file mapping. For fast query (jobs() call), we probably want to also store job metadata, such as backend name, in a structured way.

Acceptance criteria

Add the following methods to QiskitRuntimeLocalService

  • job
  • jobs
  • delete_job
@jyu00 jyu00 added the enhancement New feature or request label Apr 11, 2024
@jyu00 jyu00 added this to the Local testing mode MVP2 milestone Apr 11, 2024
@kt474 kt474 self-assigned this Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants