The doc on https://docs.janusgraph.org/basics/schema/#automatic-schema-maker says automatically created property key has data type Object.class

By default, implicitly created edge labels have multiplicity MULTI and implicitly created property keys have cardinality SINGLE and data type Object.class.

However, my testing shows that Default Schema Maker automatically infers the type of propert

I am unclear about the difference between :field_list and :fields options.

Could someone please give me some clues.

The example here also appears to be missing some comments for the second part that might clarify this a bit.

https://github.com/sunspot/sunspot#restrictions-and-field-list
I'd be happy to PR the explanation to the README once I get some clarity

@serggl @markmcdonal

I don't know exactly if it is a documentation or implementation bug:

In the documentation you run at the end $buffer->flush(). In this case I would expect some documents in my index, but no documents are indexed. If I add a $this->updateQuery->addCommit(); inside of the flush method, then documents are indexed. The example should be work if flush method will be replaced by commit.

So

My question is when I index a document with update/extract, if solr automatically create a "field" with the content of tika parser.

can someone point me to the documentation or implementation of query load balancing? I am trying to run some benchmarks and am curious how this API load balances across the replicas/shards in a solrcloud cluster.
Thank you

https://github.com/rsolr/rsolr/blob/master/README.rdoc#retry-503s

A 503 is usually a temporary error which RSolr may retry if requested. You may specify the number of retry attempts with the :retry_503 option.

Yet the only reference in the code is at https://github.com/rsolr/rsolr/blob/master/lib/rsolr/client.rb#L287-L289 where it serves as a flag and not a count.

Issue Description

It would be cool to override the config file as a whole on the cmd line so that lots of options could be updated in one place.

How to reproduce it

Environment and Version Information

All environments.

An external links for reference

Contributing

I'll fix this.

Daniel has created a docker to generate T3 sphinx documentation.

https://github.com/DanielSiepmann/t3-sphinx

I think this would complete TYPO3-docker-boilerplate, if we could render the documentation without additional configuration to HTML, PDF and JSON. (JSON is the format needed by the extension restdoc to render Sphinx to TYPO3 pages.)

As there is already a Makefile:

• make html extension_k

In Search-As-You-Type, Completion, and Suggestion (Elasticsearch).ipynb, in the "Post-Search Suggest" section, suggest_body contains a small typo:

suggest_body = { 
    "title_comp