Comments (8)
I propose to implicitly add $Object:objectType=REGULAR
to $Object:ROOT
filter then and reflect it in api doc and leave other filters as-is.
from neofs-node.
Well, physically tombstones are root objects. Is there a requirement to exclude tombstones from such a search?
from neofs-node.
Well, physically tombstones are root objects. Is there a requirement to exclude tombstones from such a search?
Yes, in nspcc-dev/neofs-api-go#163 we discussed leaf
and root
objects as a system and user scope. Tombstone is an internal implementation detail and should not be seen in user scope, therefore tombstone is not a root object
. However it is a physically stored object, that can be migrated and replicated, so it is a leaf
.
from neofs-node.
Well, physically tombstones are root objects. Is there a requirement to exclude tombstones from such a search?
Yes, in nspcc-dev/neofs-api-go#163 we discussed
leaf
androot
objects as a system and user scope. Tombstone is an internal implementation detail and should not be seen in user scope, therefore tombstone is not aroot object
. However it is a physically stored object, that can be migrated and replicated, so it is aleaf
.
According to neofs-api tombstones match root filter. Is it a bug in API?
from neofs-node.
According to neofs-api tombstones match root filter. Is it a bug in API?
I would like to say yes, but maybe there are different opinions on that. Neofs-api contains implementation details, but it lacks the meaning behind root and leaf objects (as for me, they should represent user and system scopes)
from neofs-node.
What do you think @realloc?
from neofs-node.
I think Tombstones are a special type of objects, as indicated in ObjectType
. Object Search operations should work with Regular objects by default. If there is need to search for Tombstones or Storage Groups, the one may use $Object:objectType
key.
Tombstone has a list of engraved objects in it's payload, just like Storage Group does. It doesn't participate in split hierarchy directly, it doesn't have split headers and because of that it should not be treated as leaf or root object. I propose to exclude Tombstones and Storage Groups from regular search and reflect that behaviour in documentation.
from neofs-node.
I think Tombstones are a special type of objects, as indicated in
ObjectType
. Object Search operations should work with Regular objects by default. If there is need to search for Tombstones or Storage Groups, the one may use$Object:objectType
key.Tombstone has a list of engraved objects in it's payload, just like Storage Group does. It doesn't participate in split hierarchy directly, it doesn't have split headers and because of that it should not be treated as leaf or root object. I propose to exclude Tombstones and Storage Groups from regular search and reflect that behaviour in documentation.
While I agree that only regular objects should be treated as root object, I cannot agree about leafs. Leafs are designed to return physically stored object. It is useful for system operations like replication because storage groups, tombstone and regular objects should be treated equally.
from neofs-node.
Related Issues (20)
- Upgrade to SDK RC9 HOT 3
- Do not vote for the same node on IR start
- Outdated mainnet/testnet configs and READMEs
- Test failures after update to SDK RC8
- I'm able to find the object that is marked for deletion HOT 8
- docker is intendent to run app not OS HOT 2
- Special exit code for --await CLI commands
- Object PUT, No space left HOT 6
- Static session does not expire in the next epoch HOT 3
- Evaluate timeout CLI parameter against block time HOT 1
- Adapt new NNS contract behavior HOT 1
- Object expiration and lock conflict
- `neofs-cli` default timeouts for `object put`/`object get`/etc are implicit HOT 5
- Why Alphabet nodes vote for the validators on their startup? HOT 2
- panic: missing context
- `neofs-adm` can not generate SN config for testnet
- Adapt Neo account contract groups HOT 1
- Expand linters set HOT 6
- Evacuate test fails sometimes
- Refactor IR HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from neofs-node.