See #1029
Right now in insertElementRecursive(), DocLayer does NOT try to store arrays with null values as sparse arrays, i.e. for null value it still insert a k-v for it, which is kind of against what it attempts to achieve later when doing update (skipping the null values and effectively store those arrays as spars arrays). We should make the behavior consistent and do the same in insertion.
Currently, there are some examples in README.md with Elasticsearch queries and corresponding uptasticsearch code. That code is effectively pseudocode right now, as it references a fictional Elasticsearch cluster.
I think this could lead to a bad experience with the docs and lead people to walk away from the project and not come back.
I would love if someone changed those examples to be r
Add a description, image, and links to the document-database topic page so that developers can more easily learn about it.
To associate your repository with the document-database topic, visit your repo's landing page and select "manage topics."
Is your feature request related to a problem? Please describe.
CSV files produced in different locales have different default separators, a comma-separated file (",") is but one type of CSV.
In Sweden we usually use a semicolon (";") as separator and many CSV files use a tab as separator ("\t"). Importing CSVs requires reformatting them before import, and causes inoperability issues and f