Impose geodiff push limits

Open
#245 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reading geodiff issue 224, which is identified as a prerequisite for splitting the workload, then trace the push implementation in this Python API client. Done means enforcing both per-push limits—10,000 changes across GPKG files and 10 MB of GPKG-diff files—and splitting oversized work into multiple pushes.

Written by the indexing model from the issue text.

Description

enhancement

Let's limit the size of single push by imposing:

  • 10 000 changes in all gpkg files / per push
  • 10 MB as max size of all gpkg-diff files / per push

And split the work into multiple pushes. For splitting the workload we need https://github.com/MerginMaps/geodiff/issues/224

Dominant language
Python
Stars
23
Forks
12
Avg merge
2d 13h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

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.

More from MerginMaps/python-api-client

All issues in MerginMaps/python-api-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.