Jon Bratseth

Query profiles must use the full name, [ranking.features](https://docs.vespa.ai/en/reference/query-api-reference.html#ranking.features), aliases like `input` are only supported in queries. The assumption behind this is that brevity matters more in requests and structure more...

Yes, that is on our roadmap for this autumn.

We'll get to it this year!

... 1st of January 😅 We're still working on it. Should be Real Soon Now.

Yes, we'll support some additional ones, maybe not right away. This will still be some weeks - I can't be more specific sorry.

Sorry, not yet!

Thanks for the clear description. Assigning to the right person. Note that you can skip the get_field instruction and just to `input one_adress.address_id | summary | attribute`

A percentage of the *matched* docs?

Yes, you are right it should be counted after any phase 1 dropping. We also want to make it global, not per node, to simplify scaling. But second phase may...

Yes, what you are saying makes sense, I just think we need something a bit more complicated which clamps the cost increase with many matches and the quality decrease with...