Jon Bratseth

1.: Separating by language instead of by functional module at the top level seems a step in the wrong direction to me. We have lots of modules with multiple languages...

> I do think the package name for external use should be vespa though. Agreed, and ensuring that is more important than our internal structure. By "vespa modules" (as opposed...

Thanks, I like these suggestions! We hope to be able to start working on this in our next sprint starting February 9.

We can divide errors into there kinds, perhaps: 1. Wrong input so no document operations can be issued. 2. Wrong config parameters such that no operations can even succeed. 3....

But if you feed a million documents and one fail I don't think we should exit with 1. We only want to do it if the input can't be parsed.

That error is in the Result, which represents the response from the server side. If the input can't be parsed we don't create requests and there is no response.

Ok, I read the original description now, you are right: If we only do it when an option is set we can exit with 1 on server-side parse issues (or...

If you care about whether operations are applied successfully you *must* implement error handling on the level of individual operations, by handling the Replies (typically counting the failures and alerting...

This is work in progress.

> Also IMHO the error message is too vague. Agree. I just fixed that. @geirst will have to answer the rest.