Vespa Product Updates, January 2019: Parent/Child, Large File Config Download, and a Simplified Feeding Interface
<p>In <a href="http://blog.vespa.ai/post/181105335071/vespa-product-updates-december-2018-onnx-import">last month’s Vespa update</a>, we mentioned ONNX integration, precise transaction log pruning, grouping on maps, and improvements to streaming search performance. Largely developed by Yahoo engineers, <a href="https://github.com/vespa-engine/vespa">Vespa</a> is an open source big data processing and serving engine. It’s in use by many products, such as Yahoo News, Yahoo Sports, Yahoo Finance, and Oath Ads Platforms. Thanks to feedback and contributions from the community, Vespa continues to evolve.<b><br/></b></p><p>This month, we’re excited to share the following updates with you:</p><p><b>Parent/Child</b></p><p>We’ve added support for multiple levels of parent-child document references. Documents with references to parent documents can now import fields, with minimal impact on performance. This simplifies updates to parent data as no denormalization is needed and supports use cases with many-to-many relationships, like Product Search. Read more in <a href="https://docs.vespa.ai/documentation/parent-child.html">parent-child</a>.</p><p><b>File URL references in application packages</b></p><p>Serving nodes sometimes require data files which are so large that it doesn’t make sense for them to be stored and deployed in the application package. Such files can now be included in application packages by using the <a href="https://docs.vespa.ai/documentation/cloudconfig/application-packages.html">URL reference</a>. When the application is redeployed, the files are automatically downloaded and injected into the components who depend on them. </p><p><b>Batch feed in java client</b></p><p>The new <a href="https://github.com/vespa-engine/vespa/blob/master/vespa-http-client/src/main/java/com/yahoo/vespa/http/client/SyncFeedClient.java">SyncFeedClient</a> provides a simplified API for feeding batches of data with high performance using the Java HTTP client. This is convenient when feeding from systems without full streaming support such as Kafka and DynamoDB.</p><p><br/></p><p>We welcome your contributions and feedback (tweet or email) about any of these new features or future improvements you’d like to see.</p>