This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] swapping a v1 for a v3
- Previous message (by thread): [atlas] swapping a v1 for a v3
- Next message (by thread): [atlas] RIPE Atlas VM Anchors IPv6 only support?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Fri Dec 10 15:51:23 CET 2021
On 2021/12/10 15:46 , Sander Steffann wrote: >> Data is firmly associated with a probe ID. And hardware probes all have their own unique IDs. > > So… How do we get someone to do "UPDATE data SET probe_id=25898 WHERE probe_id=2285 ;) Simple, download the data dumps, import them into Google Bigtable, run the update and convince the RIPE NCC to drop the hadoop cluster. :-)
- Previous message (by thread): [atlas] swapping a v1 for a v3
- Next message (by thread): [atlas] RIPE Atlas VM Anchors IPv6 only support?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]