Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document routingKey interpolation somewhere more prominently #1938

Open
jaley opened this issue Jun 26, 2023 · 1 comment
Open

Document routingKey interpolation somewhere more prominently #1938

jaley opened this issue Jun 26, 2023 · 1 comment
Labels
priority-p1 Need to completed ASAP

Comments

@jaley
Copy link

jaley commented Jun 26, 2023

The only docs I can find for the interpolation string support in Firehose routing keys is this FAQ.

This is really hard to discover, and it's a real shame because this a great feature. I think it's actually a really important part of the learning journey for developers to picture how they can fan-out or fan-in as a function of their own data using Ably integrations. Personally, I think it should at least have a place on the main docs site and be linked from the various integration docs that support it, but it may be useful to include it in examples or other places where we're trying to get the value of integrations across.

┆Issue is synchronized with this Jira Task by Unito

@mattheworiordan mattheworiordan added the priority-p1 Need to completed ASAP label Oct 18, 2024
@mattheworiordan
Copy link
Member

I am bubbling this up as high priority for a number of reasons:

  1. This is going to be used in our new LiveSync MongoDB connector to route data from change stream queries to channels.
  2. Interpolation format is also used in batching, but not for routingKey but for a conflation key. So we have a conceptual model that needs explaining for our interpolation format. I assume we'd then explain on the interpolation format page where it's usde.
  3. Do a search in Slack for interpolation and in support tickets and you will see customers are asking about this a lot. The fact that this is not discoverable is a problem that has not changed and is more relevant now than ever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-p1 Need to completed ASAP
Development

No branches or pull requests

2 participants