fsspec / fsspec/kerchunk

inline_threshold not encoding time value?

Open
#468 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
366
Forks
96
Avg merge
24m
Merged PRs (30d)
1

Description

In the example below I was expecting that time would get encoded because inline_threshold=400 and time is only 8 bytes long.

Below we see that depth is encoded (it's 332 bytes long), but time is not.

Is this expected behavior?

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the example described in the issue and inspect how inline_threshold treats the 8-byte time value versus the 332-byte depth value. Done means determining whether this behavior is expected and, if not, adding a regression test and correcting the encoding behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.