Solr
  1. Solr
  2. SOLR-1337

Spans and Payloads Query Support

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 4.4
    • Component/s: None
    • Labels:
      None

      Description

      It would be really nice to have query side support for: Spans and Payloads. The main ingredient missing at this point is QueryParser support and a output format for the spans and the payload spans.

        Issue Links

          Activity

          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
          Hide
          Jan Høydahl added a comment -

          It would be great to see explicit proximity operators using ordered SpanNearQuery. I believe we already have unordered span query support through "foo bar"~100

          Perhaps this syntax could be extended to express ordered proximity, e.g. "foo bar"~>100

          Show
          Jan Høydahl added a comment - It would be great to see explicit proximity operators using ordered SpanNearQuery. I believe we already have unordered span query support through "foo bar"~100 Perhaps this syntax could be extended to express ordered proximity, e.g. "foo bar"~>100
          Hide
          Robert Muir added a comment -

          Bulk move 3.2 -> 3.3

          Show
          Robert Muir added a comment - Bulk move 3.2 -> 3.3
          Hide
          Robert Muir added a comment -

          3.4 -> 3.5

          Show
          Robert Muir added a comment - 3.4 -> 3.5
          Hide
          Hoss Man added a comment -

          bulk fixing the version info for 4.0-ALPHA and 4.0 all affected issues have "hoss20120711-bulk-40-change" in comment

          Show
          Hoss Man added a comment - bulk fixing the version info for 4.0-ALPHA and 4.0 all affected issues have "hoss20120711-bulk-40-change" in comment
          Hide
          Robert Muir added a comment -

          rmuir20120906-bulk-40-change

          Show
          Robert Muir added a comment - rmuir20120906-bulk-40-change
          Hide
          Robert Muir added a comment -

          moving all 4.0 issues not touched in a month to 4.1

          Show
          Robert Muir added a comment - moving all 4.0 issues not touched in a month to 4.1
          Hide
          Dmitry Kan added a comment -

          Jan Høydahl Jan: we implemented a new operator for Lucene / SOLR 3.4 that does exactly what you say, see: https://issues.apache.org/jira/browse/LUCENE-3758?focusedCommentId=13207710&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13207710

          if you or anyone else needs a patch, just let me know.

          Show
          Dmitry Kan added a comment - Jan Høydahl Jan: we implemented a new operator for Lucene / SOLR 3.4 that does exactly what you say, see: https://issues.apache.org/jira/browse/LUCENE-3758?focusedCommentId=13207710&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13207710 if you or anyone else needs a patch, just let me know.
          Hide
          Jan Høydahl added a comment -

          Dmitry Kan, where is your code implemented? At Lucene query parser level?

          Show
          Jan Høydahl added a comment - Dmitry Kan , where is your code implemented? At Lucene query parser level?
          Hide
          Dmitry Kan added a comment -

          [Jan Høydahl] at Lucene query parser level. New token FUZZY_SLOP_SHARP (name isn't probably the best sound, but can be changed) has been introduced in the QueryParser.jj and supportive code implemented. The syntax is same as that of ~ operator, i.e. "term1 term2 ... termn" #slope.

          Show
          Dmitry Kan added a comment - [Jan Høydahl] at Lucene query parser level. New token FUZZY_SLOP_SHARP (name isn't probably the best sound, but can be changed) has been introduced in the QueryParser.jj and supportive code implemented. The syntax is same as that of ~ operator, i.e. "term1 term2 ... termn" #slope.
          Hide
          Otis Gospodnetic added a comment -

          My impression was that Span queries and Payloads are kind of pase in Luceneland.... no?
          If yes, should we Won't Fix this patchless 4 years old issue?

          Show
          Otis Gospodnetic added a comment - My impression was that Span queries and Payloads are kind of pase in Luceneland.... no? If yes, should we Won't Fix this patchless 4 years old issue?
          Hide
          Grant Ingersoll added a comment -

          I wouldn't say payloads are, unless you are telling me there is a better solution, but we can handle that separately.

          Show
          Grant Ingersoll added a comment - I wouldn't say payloads are, unless you are telling me there is a better solution, but we can handle that separately.
          Hide
          Steve Rowe added a comment -

          Bulk close resolved 4.4 issues

          Show
          Steve Rowe added a comment - Bulk close resolved 4.4 issues

            People

            • Assignee:
              Grant Ingersoll
              Reporter:
              Grant Ingersoll
            • Votes:
              11 Vote for this issue
              Watchers:
              21 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development