Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.4
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Improve support for the Trie* fields up to the level of Solr's existing numeric types.

        Issue Links

          Activity

          Yonik Seeley created issue -
          Hide
          Yonik Seeley added a comment -

          At the top of my list is:

          • no toExterna(), etc... this causes toString() to not print out nice values in debugging... this will cause failures in other places

          There are probably others... I haven't checked, but does date faceting work on trie-type dates?

          Should the trie based date subclass DateField so we can have a common base class for all date related classes? Seems like this would make it easier for separate components (like date faceting) to deal with.

          Show
          Yonik Seeley added a comment - At the top of my list is: no toExterna(), etc... this causes toString() to not print out nice values in debugging... this will cause failures in other places There are probably others... I haven't checked, but does date faceting work on trie-type dates? Should the trie based date subclass DateField so we can have a common base class for all date related classes? Seems like this would make it easier for separate components (like date faceting) to deal with.
          Hide
          Shalin Shekhar Mangar added a comment -

          does date faceting work on trie-type dates?

          Faceting itself does not work with any trie fields because of the encoded values in the index. So we need to implement indexedToReadable in TrieField. Also, since trie fields are multi-valued, we need to short-cut faceting on using the highest precision value.

          Show
          Shalin Shekhar Mangar added a comment - does date faceting work on trie-type dates? Faceting itself does not work with any trie fields because of the encoded values in the index. So we need to implement indexedToReadable in TrieField. Also, since trie fields are multi-valued, we need to short-cut faceting on using the highest precision value.
          Yonik Seeley made changes -
          Field Original Value New Value
          Link This issue incorporates SOLR-1289 [ SOLR-1289 ]
          Yonik Seeley made changes -
          Link This issue incorporates SOLR-1290 [ SOLR-1290 ]
          Yonik Seeley made changes -
          Link This issue incorporates SOLR-1291 [ SOLR-1291 ]
          Yonik Seeley made changes -
          Link This issue incorporates SOLR-1322 [ SOLR-1322 ]
          Yonik Seeley made changes -
          Link This issue incorporates SOLR-1329 [ SOLR-1329 ]
          Hide
          Yonik Seeley added a comment -

          Everything easily doable or critical has been done - moving the rest of these tasks out to 1.5

          Show
          Yonik Seeley added a comment - Everything easily doable or critical has been done - moving the rest of these tasks out to 1.5
          Yonik Seeley made changes -
          Fix Version/s 1.5 [ 12313566 ]
          Fix Version/s 1.4 [ 12313351 ]
          Hide
          Hoss Man added a comment -

          Bulk updating 240 Solr issues to set the Fix Version to "next" per the process outlined in this email...

          http://mail-archives.apache.org/mod_mbox/lucene-dev/201005.mbox/%3Calpine.DEB.1.10.1005251052040.24672@radix.cryptio.net%3E

          Selection criteria was "Unresolved" with a Fix Version of 1.5, 1.6, 3.1, or 4.0. email notifications were suppressed.

          A unique token for finding these 240 issues in the future: hossversioncleanup20100527

          Show
          Hoss Man added a comment - Bulk updating 240 Solr issues to set the Fix Version to "next" per the process outlined in this email... http://mail-archives.apache.org/mod_mbox/lucene-dev/201005.mbox/%3Calpine.DEB.1.10.1005251052040.24672@radix.cryptio.net%3E Selection criteria was "Unresolved" with a Fix Version of 1.5, 1.6, 3.1, or 4.0. email notifications were suppressed. A unique token for finding these 240 issues in the future: hossversioncleanup20100527
          Hoss Man made changes -
          Fix Version/s Next [ 12315093 ]
          Fix Version/s 1.5 [ 12313566 ]
          Hoss Man made changes -
          Fix Version/s 3.2 [ 12316172 ]
          Fix Version/s Next [ 12315093 ]
          Hide
          Robert Muir added a comment -

          Bulk move 3.2 -> 3.3

          Show
          Robert Muir added a comment - Bulk move 3.2 -> 3.3
          Robert Muir made changes -
          Fix Version/s 3.3 [ 12316471 ]
          Fix Version/s 3.2 [ 12316172 ]
          Robert Muir made changes -
          Fix Version/s 3.4 [ 12316683 ]
          Fix Version/s 4.0 [ 12314992 ]
          Fix Version/s 3.3 [ 12316471 ]
          Hide
          Robert Muir added a comment -

          3.4 -> 3.5

          Show
          Robert Muir added a comment - 3.4 -> 3.5
          Robert Muir made changes -
          Fix Version/s 3.5 [ 12317876 ]
          Fix Version/s 3.4 [ 12316683 ]
          Simon Willnauer made changes -
          Fix Version/s 3.6 [ 12319065 ]
          Fix Version/s 3.5 [ 12317876 ]
          Hide
          Hoss Man added a comment -

          Bulk changing fixVersion 3.6 to 4.0 for any open issues that are unassigned and have not been updated since March 19.

          Email spam suppressed for this bulk edit; search for hoss20120323nofix36 to identify all issues edited

          Show
          Hoss Man added a comment - Bulk changing fixVersion 3.6 to 4.0 for any open issues that are unassigned and have not been updated since March 19. Email spam suppressed for this bulk edit; search for hoss20120323nofix36 to identify all issues edited
          Hoss Man made changes -
          Fix Version/s 3.6 [ 12319065 ]
          Hide
          Hoss Man added a comment -

          no idea why this issue is still open.

          all of the work in this task (or the sub-tasks) was done a long time ago, and yonik created distinct (related) issues for the remaining work

          Show
          Hoss Man added a comment - no idea why this issue is still open. all of the work in this task (or the sub-tasks) was done a long time ago, and yonik created distinct (related) issues for the remaining work
          Hoss Man made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 4.0 [ 12314992 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Yonik Seeley
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development