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

Change schema to allow for id or seq_id #2342

Closed
cwschilly opened this issue Sep 5, 2024 · 0 comments · Fixed by #2343
Closed

Change schema to allow for id or seq_id #2342

cwschilly opened this issue Sep 5, 2024 · 0 comments · Fixed by #2343
Assignees

Comments

@cwschilly
Copy link
Contributor

cwschilly commented Sep 5, 2024

What Needs to be Done?

Motivated by #2201 testing

Change the schema to allow either id or seq_id in the JSON. id should be assumed bit-packed, while seq_id is assumed not bit-packed.

@cwschilly cwschilly self-assigned this Sep 5, 2024
cwschilly added a commit that referenced this issue Sep 5, 2024
@cwschilly cwschilly linked a pull request Sep 5, 2024 that will close this issue
cwschilly added a commit that referenced this issue Sep 5, 2024
cwschilly added a commit that referenced this issue Sep 6, 2024
cwschilly added a commit that referenced this issue Sep 6, 2024
cwschilly added a commit that referenced this issue Sep 6, 2024
cwschilly added a commit that referenced this issue Sep 6, 2024
nlslatt added a commit that referenced this issue Sep 9, 2024
…ow-for-id-or-seq_id

#2342: Change schema to allow for `id` or `seq_id`
cwschilly added a commit that referenced this issue Sep 20, 2024
cwschilly added a commit that referenced this issue Sep 20, 2024
cwschilly added a commit that referenced this issue Sep 20, 2024
cwschilly added a commit that referenced this issue Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant