Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.8, 6.0
    • Component/s: Schema and Analysis
    • Labels:
      None

      Description

      The DIH example schemas should be modified to include trie numeric/date fields, and add comments about the non-trie numeric/date fields being deprecated and removed in 5.0.

      The DIH example solrconfig.xml files are also showing their age - they should be copied from the main example solrconfig.xml and have the config they need added back.

        Activity

        Hide
        Shawn Heisey added a comment -

        Big +1. I've wanted to do it myself, but tuits (especially the round kind) have been in short supply lately. I get a grand idea, perhaps go as far as filing an issue, and then find I have no time to work on it.

        Related but requires its own issue: I've been wondering if the multicore example is overkill. It's certainly far out of date. The DIH example illustrates multicore well. We can include README.multicore or something like it in the example directory.

        Something that's been in the back of my mind for discussion is adding 'collection2' to the standard example with the same config/schema as collection1. I can't decide whether it's a good or bad idea.

        Show
        Shawn Heisey added a comment - Big +1. I've wanted to do it myself, but tuits (especially the round kind) have been in short supply lately. I get a grand idea, perhaps go as far as filing an issue, and then find I have no time to work on it. Related but requires its own issue: I've been wondering if the multicore example is overkill. It's certainly far out of date. The DIH example illustrates multicore well. We can include README.multicore or something like it in the example directory. Something that's been in the back of my mind for discussion is adding 'collection2' to the standard example with the same config/schema as collection1. I can't decide whether it's a good or bad idea.
        Hide
        Steve Rowe added a comment -

        4.x patch.

        Config sets for all of the example-DIH cores except tika are upgraded to the latest main example config set, with changes required for each.

        As previously, the tika config set is minimal. I started with the main example config set and then cut everything out of tika/conf/schema.xml that refers to resources that aren't there.

        Run the following svn script before applying the patch:

        svn mv solr/example/example-DIH/solr/mail/conf/{,mail-}data-config.xml
        for a in mail solr rss db tika ; do 
            for b in solrconfig.xml schema.xml admin-extra*.html ; do
                (svn rm solr/example/example-DIH/solr/$a/conf/$b &&
                 svn cp solr/example/solr/collection1/conf/$b solr/example/example-DIH/solr/$a/conf/) 
            done
        done
        for a in solr rss db ; do
            svn rm solr/example/example-DIH/solr/$a/conf/elevate.xml
        done
        for a in mail solr rss db ; do
            for b in stopwords.txt synonyms.txt ; do 
                svn rm solr/example/example-DIH/solr/$a/conf/$b
            done
        done
        for a in mail solr rss db ; do
            for b in elevate.xml stopwords.txt synonyms.txt currency.xml ; do 
                svn cp solr/example/solr/collection1/conf/$b solr/example/example-DIH/solr/$a/conf/
            done
        done
        svn cp solr/example/solr/collection1/conf/scripts.conf solr/example/example-DIH/solr/mail/conf/
        svn rm solr/example/example-DIH/solr/db/conf/xslt
        for a in mail solr rss db ; do
            for b in clustering lang velocity xslt mapping-*.txt update-script.js spellings.txt ; do
                svn cp solr/example/solr/collection1/conf/$b solr/example/example-DIH/solr/$a/conf/
            done
        done
        
        Show
        Steve Rowe added a comment - 4.x patch. Config sets for all of the example-DIH cores except tika are upgraded to the latest main example config set, with changes required for each. As previously, the tika config set is minimal. I started with the main example config set and then cut everything out of tika/conf/schema.xml that refers to resources that aren't there. Run the following svn script before applying the patch: svn mv solr/example/example-DIH/solr/mail/conf/{,mail-}data-config.xml for a in mail solr rss db tika ; do for b in solrconfig.xml schema.xml admin-extra*.html ; do (svn rm solr/example/example-DIH/solr/$a/conf/$b && svn cp solr/example/solr/collection1/conf/$b solr/example/example-DIH/solr/$a/conf/) done done for a in solr rss db ; do svn rm solr/example/example-DIH/solr/$a/conf/elevate.xml done for a in mail solr rss db ; do for b in stopwords.txt synonyms.txt ; do svn rm solr/example/example-DIH/solr/$a/conf/$b done done for a in mail solr rss db ; do for b in elevate.xml stopwords.txt synonyms.txt currency.xml ; do svn cp solr/example/solr/collection1/conf/$b solr/example/example-DIH/solr/$a/conf/ done done svn cp solr/example/solr/collection1/conf/scripts.conf solr/example/example-DIH/solr/mail/conf/ svn rm solr/example/example-DIH/solr/db/conf/xslt for a in mail solr rss db ; do for b in clustering lang velocity xslt mapping-*.txt update-script.js spellings.txt ; do svn cp solr/example/solr/collection1/conf/$b solr/example/example-DIH/solr/$a/conf/ done done
        Hide
        Steve Rowe added a comment -

        Something that's been in the back of my mind for discussion is adding 'collection2' to the standard example with the same config/schema as collection1. I can't decide whether it's a good or bad idea.

        I wonder if we could make 'ant example' create the non-main examples on the fly? The changes I did here made it clear that the config required for the example DIH cores is very minor, and could maybe be stored as a small patch that 'ant example' applies after copying the main example over, or something similar. The same could go for 'collection2', I guess?

        Show
        Steve Rowe added a comment - Something that's been in the back of my mind for discussion is adding 'collection2' to the standard example with the same config/schema as collection1. I can't decide whether it's a good or bad idea. I wonder if we could make 'ant example' create the non-main examples on the fly? The changes I did here made it clear that the config required for the example DIH cores is very minor, and could maybe be stored as a small patch that 'ant example' applies after copying the main example over, or something similar. The same could go for 'collection2', I guess?
        Hide
        Steve Rowe added a comment -

        I'm going to commit the 4.x patch shortly.

        Show
        Steve Rowe added a comment - I'm going to commit the 4.x patch shortly.
        Hide
        ASF subversion and git services added a comment -

        Commit 1583501 from Steve Rowe in branch 'dev/branches/branch_4x'
        [ https://svn.apache.org/r1583501 ]

        SOLR-5937: Modernize the DIH example config sets

        Show
        ASF subversion and git services added a comment - Commit 1583501 from Steve Rowe in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1583501 ] SOLR-5937 : Modernize the DIH example config sets
        Hide
        ASF subversion and git services added a comment -

        Commit 1586120 from sarowe@apache.org in branch 'dev/trunk'
        [ https://svn.apache.org/r1586120 ]

        SOLR-5937: Modernize the DIH example config sets

        Show
        ASF subversion and git services added a comment - Commit 1586120 from sarowe@apache.org in branch 'dev/trunk' [ https://svn.apache.org/r1586120 ] SOLR-5937 : Modernize the DIH example config sets
        Hide
        Steve Rowe added a comment -

        Committed to branch_4x, then ran the same bash script and applied the branch_4x patch to trunk, then committed to trunk.

        Show
        Steve Rowe added a comment - Committed to branch_4x, then ran the same bash script and applied the branch_4x patch to trunk, then committed to trunk.
        Hide
        Uwe Schindler added a comment -

        Close issue after release of 4.8.0

        Show
        Uwe Schindler added a comment - Close issue after release of 4.8.0

          People

          • Assignee:
            Steve Rowe
            Reporter:
            Steve Rowe
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development