>
> > The `Attr` string field and the subsequent fields for the corresponding
> > value of that attribute all appear to be value-related, as opposed to
> > testing the presence of attribute (e.g. `tag`) in the first place.
>
> I think something along the lines of
>
> PermanodeConstraint{
> Attr: "tag",
> ValueMatches: &StringConstraint{
> Empty: true,
> }
> }
>
> might do the trick.
>
Doesn't appear to unfortunately:
$ ./camtool search '{
"permanode": {
"attr": "tag",
"valueMatches": {
"empty": true
}
}
}'
{
"blobs": null,
"description": null
}
I did a positive search test to verify things were generally "working" and
that gave the results expected. So we appear to be out of luck in this case.
> > I can work around this for now by using camput with a tag of
> "unprocessed"
> > (or similar), a tag that will then be removed as part of the later
> workflow.
> > (Happy to still raise an issue if you think this is of broader interest?)
>
> What I think is almost of no relevance. :-)
> If you don't open an issue about it, there's a close to zero chance
> that anyone but you will work on this matter or even discuss it.
>
Ha ha! Ok, I take your point. Will raise an issue on Github now. Just
wanted to make sure this hadn't been covered before by asking a question
here first.
> > ...
>
> I'm at least interested in seeing what you come up with on the UI
> matter. Anything we can reuse for Camlistore's web UI would sure be a
> win for us.
Will certainly be asking for feedback in the near future so will ping back
here too.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Camlistore" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
