[ 
https://issues.apache.org/jira/browse/SOLR-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Varun Thacker updated SOLR-6127:
--------------------------------

    Attachment: README.txt
                LICENSE.txt
                freebase_film_dump.py

You need to put in your API Key to run the script. It runs with python3.

I created a README which helps get started with loading the data in and start 
searching.

The License for the data is present in the LICENSE.txt file. I have not 
attached the generated output in any format in this patch.

Couple of points to note when I was creating the Readme - 

1. I am assuming that our new default will be schemaless mode which means we 
can use managed schema to index the documents.
2. Can we change the /select handler to default to json with indent on?

Having an example with nested documents in a separate example is a better 
approach I feel. We should not complicate the experience for new users who 
don't care for such data

> Improve Solr's exampledocs data
> -------------------------------
>
>                 Key: SOLR-6127
>                 URL: https://issues.apache.org/jira/browse/SOLR-6127
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Varun Thacker
>            Priority: Minor
>             Fix For: 5.0
>
>         Attachments: LICENSE.txt, README.txt, film.csv, film.json, film.xml, 
> freebase_film_dump.py, freebase_film_dump.py, freebase_film_dump.py, 
> freebase_film_dump.py, freebase_film_dump.py, freebase_film_dump.py
>
>
> Currently 
> - The CSV example has 10 documents.
> - The JSON example has 4 documents.
> - The XML example has 32 documents.
> 1. We should have equal number of documents and the same documents in all the 
> example formats
> 2. A data set which is slightly more comprehensive.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to