Closed alfred-landrum closed 4 years ago
Verified in Brim commit 22604c1
talking to zqd
commit f9a90eb
.
I triggered the creation of a couple Spaces, one via pcap import and one via Zeek log import. I can see the opaque Space names now below my data/
directory.
~/Library/Application Support/Brim/data/spaces$ tree
.
├── sp_1c8HwI2VOUQWlgvIoELq51XrFZG
│ ├── all.zng
│ ├── config.json
│ ├── info.json
│ └── packets.idx.json
└── sp_1c8Hz0OM81fitoUQagFvW0uLKrk
├── all.zng
├── config.json
└── info.json
2 directories, 7 files
Thanks @mattnibs!
Add support for space ids, uuid-like immutable identifiers that will be used instead of space names as the resource id in api calls. The id should be created by zqd when the space is returned, and passed back in the create response struct.
To make the transition easy from the existing name-based calls, I suggest that we continue to treat the directory name under the
spaces
directory as the space's id. So before this work goes in, if there was a directoryspaces/foo
, because space foo was created, we treatfoo
as the id for that space going forward. After this work goes in, though, when a new space is created with namebar
, the fs would look like:space/ae123428d33.../
space/ae123428d33.../config.json
where
config.json
now has an entryname: "bar"
.