Right now we are only able to search for the content of ledger additional metadata (such as the "component"). In some cases the content of the metadata can be very broad and mean nothing without the actual name of the metadata.
Here an example of Ledger data:
Ledger 137324957
Age: 342543 hours
Created at: Thu Aug 22 2019 12:29:58 GMT+0200 (Central European Summer Time)
State: OPEN
Ensemble size: 2 (number of bookies)
WriteQuorumSize: 2 (number of copies)
AckQuorumSize: 2
Size: 0 Bytes
LastEntryId: -1
Password: mn
DigestType: CRC32
Closed: false
MetadataFormatVersion: 2
iddelivery: 4933
component: delivery-sprint
idsprint: 597
application: magnews
idc: 4921
If we need to search for all the ledger with "iddelivery: 4933" we can only search for "4933", but as you can see from the ledger above we have other additional metadata with the same "data structure", so we risk finding out ledger with "idc: 4933" and "iddelivery: 4933".
We need to be able to search for entry containing spaces and we need to be able to specify the metadata name (eg. we need to be able to search for "iddelivery: 4933")
Right now we are only able to search for the content of ledger additional metadata (such as the "component"). In some cases the content of the metadata can be very broad and mean nothing without the actual name of the metadata.
Here an example of Ledger data:
If we need to search for all the ledger with "iddelivery: 4933" we can only search for "4933", but as you can see from the ledger above we have other additional metadata with the same "data structure", so we risk finding out ledger with "idc: 4933" and "iddelivery: 4933".
We need to be able to search for entry containing spaces and we need to be able to specify the metadata name (eg. we need to be able to search for "iddelivery: 4933")