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

Charge for metadata attribute #441

Open
roman-khimov opened this issue Oct 18, 2024 · 2 comments
Open

Charge for metadata attribute #441

roman-khimov opened this issue Oct 18, 2024 · 2 comments
Labels
enhancement Improving existing functionality I3 Minimal impact S3 Minimally significant U2 Seriously planned

Comments

@roman-khimov
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when additional workload is not payed for in NeoFS. nspcc-dev/neofs-api#309 should be a paid for attribute, just like NNS names.

Describe the solution you'd like

Add a configuration option and charge for this attribute.

@roman-khimov roman-khimov added enhancement Improving existing functionality U2 Seriously planned S3 Minimally significant I3 Minimal impact labels Oct 18, 2024
@roman-khimov roman-khimov added this to the v0.21.0 milestone Oct 18, 2024
@roman-khimov
Copy link
Member Author

The problem is, we don't see attributes at the contract level (at least not until we refactor the container structure).

@roman-khimov roman-khimov removed this from the v0.21.0 milestone Nov 14, 2024
@roman-khimov
Copy link
Member Author

We can have a different price for meta-enabled containers though. And it'd be even more fair since the overhead increases per-object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality I3 Minimal impact S3 Minimally significant U2 Seriously planned
Projects
None yet
Development

No branches or pull requests

1 participant