Alex Vanderpot 02623e5559 neighbors: seattle->letsmesh region + fix path-edge prefix extraction ...

- Point the seattle region at the letsmesh broker (wss://mqtt-us-v1.letsmesh.net:443,
  topic meshcore/SEA) where Seattle traffic now lives.
- Fix a pre-existing bug in the path-edge extraction: `path` is a hex string of
  1-byte hop prefixes, so use substring(path, 2*i-1, 2) instead of
  hex(substring(path, i, 1)) (which re-hexed a single hex char and never matched
  the 2-char repeater prefixes -> path edges were always empty). Seattle now yields
  path edges again.

Verified on a full prod snapshot: the MV-backed "show all neighbors" query drops
from ~1.6s / 145M rows / 11.8 GiB to ~1ms / 108 rows / 3.8 KiB.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-05-29 03:02:09 -04:00

..

001_create_meshcore_packets.sql

ingest: meshcore MQTT->ClickHouse stack

2026-05-29 01:01:33 -04:00

002_create_unified_nodeinfo_view.sql

ingest: meshcore MQTT->ClickHouse stack

2026-05-29 01:01:33 -04:00

003_neighbor_refreshable_mvs.sql

neighbors: seattle->letsmesh region + fix path-edge prefix extraction

2026-05-29 03:02:09 -04:00