| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds an entirely new implementation of the internal MessageBus
DocumentAPI protocol, which shall be functionally 1-to-1 compatible
with the existing legacy protocol.
New protobuf schemas have been added to the top-level documentapi
module, which are separated into different domains of responsibility:
* CRUD messages
* Visiting messages
* Data inspection messages
As well as a schema for shared, common message types.
Both C++ and Java protocol implementations separate serialization and
deserialization into a codec abstraction per message type, which
hides the boilerplate required for Protobuf buffer management. The
Java version is a tad more verbose due to generics type-erasure.
This protocol does _not_ currently support lazy (de-)serialization
in Java, as the existing mechanisms for doing so are inherently tied
to the legacy protocol version. Performance tests will decide if we
need to introduce such functionality to the new protocol version.
To avoid having the new protocol go live in production, this commit
changes the semantics of how MessageBus version reporting works (at
least for the near future); instead of reporting the current Vespa
_release_ version, it reports the highest supported _protocol_ version.
This lets us conditionally enable the new protocol by reporting a
MessageBus version greater than or equal to the protocol version _iff_
the protocol should be active.
The new protocol is disabled by default.
Other changes:
* Protocol tests have been moved up one package directory level to
be aligned with the actual package of the classes they test. This
allows for using package-protected constructors in the serialization
tests.
* `DocumentDeserializer` now exposes the underlying document type
repo/manager. This is done to detangle `Document`/`DocumentUpdate`
deserialization from the underlying wire buffer management.
* `RemoveLocationMessage` at long last contains a bucket space,
which was forgotten when we initially added this concept to the
other messages, and where the pain of adding it in later was
too big (not so anymore!).
Unit tests for both C++ and Java have been hoisted from the legacy
test suite, cleaned up and extended with additional cases. The C++
tests use the old unit test kit and should receive a good follow-up
washing and GTest-rewrite.
**Important**: due to how MessageBus protocol versioning works, the
final protocol version is _not_ yet decided, as setting it requires
syncing against our build systems. A follow-up commit will assign
the final version as well as include all required binary test files.
|
| | |
|
| |
|
|
| |
* also, use two simple arrays instead of arraylist of tuples
|
| | |
|
| |
|
|
| |
* this matches actual serialization format and C++ implementation
|
| | |
|
| |
|
|
| |
longer relevant.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* even if the serialized datatype ID doesn't match our config,
it's quite possible the payload is OK.
* does it really make sense to "handle it gracefully" and
just ignore the payload? This seems wrong to me, but keep old
behavior for now.
|
| | |
|
| |
|
|
|
| |
* do lazy deserialization in getTensor() and getTensorType()
* avoid re-serializing when forwarding a TensorFieldValue
|
| |
|
|
|
|
|
| |
update JSON parser.
Previously, all the sparse dimensions of the sparse or mixed tensor type (to remove from)
had to be specified in the addresses to remove.
|
| |
|
|
|
| |
- Deprecate public methods using body struct.
- Update expected generated config.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Unify documentid java/cpp
GC old formats v6 and v7
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
