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

[WIP][PIP-404] Introduce per ledger properties #23837

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dao-jun
Copy link
Member

@dao-jun dao-jun commented Jan 10, 2025

Motivation

PIP doc

Modifications

Verifying this change

  • Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

@dao-jun dao-jun self-assigned this Jan 10, 2025
@dao-jun dao-jun changed the title [PIP-XYZ] Introduce per ledger properties [WIP][PIP-XYZ] Introduce per ledger properties Jan 10, 2025
@github-actions github-actions bot added the doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. label Jan 10, 2025
@dao-jun dao-jun changed the title [WIP][PIP-XYZ] Introduce per ledger properties [WIP][PIP-401] Introduce per ledger properties Jan 10, 2025
@lhotari
Copy link
Member

lhotari commented Jan 10, 2025

@dao-jun PIP-401 is already taken. Please always search the mailing list and Pulsar issues to find the next unused PIP number. The first one to start a discussion with a PIP number on the dev mailing list wins when there are conflicts.

@dao-jun dao-jun changed the title [WIP][PIP-401] Introduce per ledger properties [WIP][PIP-404] Introduce per ledger properties Jan 11, 2025
@dao-jun
Copy link
Member Author

dao-jun commented Jan 11, 2025

@dao-jun PIP-401 is already taken. Please always search the mailing list and Pulsar issues to find the next unused PIP number. The first one to start a discussion with a PIP number on the dev mailing list wins when there are conflicts.

Thanks for your reminder, I didn't noticed.

@thetumbled
Copy link
Member

Good idea, could we support constructing general index for users to facilitate sql-like query? In such way, we don't need to consume pulsar to aggegrate data into database like hive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/broker area/ML category/performance Performance issues fix or improvements doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. PIP ready-to-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants