if i'm understanding you: you're really just suggesting a syntactic
change, correct? true becomes count and false becomes lex ?
Yes. For now, it would be just that. In the future I guess there'll probably be
more ways to sort.
(the slightly tricky thing is making it a string param but
[
https://issues.apache.org/jira/browse/SOLR-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akshay K. Ukey updated SOLR-617:
Attachment: solr-617.patch
Patch with test cases and in sync with trunk.
Allow configurable
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/574/changes
--
started
Building remotely on lucene.zones.apache.org
ERROR: svn: timed out waiting for server
svn: OPTIONS request failed on '/repos/asf/lucene/solr/trunk'
[
https://issues.apache.org/jira/browse/SOLR-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633649#action_12633649
]
akshay edited comment on SOLR-617 at 9/23/08 1:13 AM:
--
This
BUILD FAILED
/tmp/build.xml:38: Cannot find ../build-contrib.xml imported from /tmp/build.xml
Total time: 1 second
refactor in DisMaxQParserPlugin and DismaxQParser to allow extending
DismaxQParser
--
Key: SOLR-786
URL: https://issues.apache.org/jira/browse/SOLR-786
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wojciech Biela updated SOLR-786:
Attachment: dismax-query-parser.patch
the patch
refactor in DisMaxQParserPlugin and DismaxQParser
[
https://issues.apache.org/jira/browse/SOLR-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wojciech Biela updated SOLR-786:
Priority: Minor (was: Major)
refactor in DisMaxQParserPlugin and DismaxQParser to allow extending
[
https://issues.apache.org/jira/browse/SOLR-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wojciech Biela updated SOLR-786:
Attachment: (was: dismax-query-parser.patch)
refactor in DisMaxQParserPlugin and DismaxQParser
[
https://issues.apache.org/jira/browse/SOLR-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wojciech Biela updated SOLR-786:
Attachment: dismax-query-parser.patch
corrected patch (added the ASL 2.0 Licence note)
refactor in
[
https://issues.apache.org/jira/browse/SOLR-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated SOLR-763:
---
Attachment: SOLR-763-PositionFilterFactory.patch
Alternative patch for matching PositionFilter.java
[
https://issues.apache.org/jira/browse/SOLR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-781:
--
Fix Version/s: 1.4
Change facet.sort from boolean to string and specify sort method explicitely
SolrJ POM refers to stax parser
---
Key: SOLR-787
URL: https://issues.apache.org/jira/browse/SOLR-787
Project: Solr
Issue Type: Bug
Affects Versions: 1.3
Reporter: Shalin Shekhar Mangar
[
https://issues.apache.org/jira/browse/SOLR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633848#action_12633848
]
Hoss Man commented on SOLR-781:
---
Note the comment i made in the thread after Lars opend this
[
https://issues.apache.org/jira/browse/SOLR-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-680:
--
Fix Version/s: 1.4
StatsComponent - get min, max, sum, qt, avg of number fields
[
https://issues.apache.org/jira/browse/SOLR-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-657:
--
Priority: Minor (was: Major)
Fix Version/s: 1.4
Replace deprecated calls with the
To whomever developed flattenBooleanQuery:
Why is the dismax query being flattened? It would seem that because of
the limited syntax that DisMaxQParserPlugin employs, all you would ever get
is a one-level boolean query but I am probably missing something.
~ David
--
View this message in
Hi,
When people add new issues to JIRA they most often don't set the Fix Version
field. Would it not be better to have a default value for that field, so that
new entries don't get forgotten when we filter by Fix Version looking for
issues to fix for the next release? If every issue had Fix
When people add new issues to JIRA they most often don't set the Fix Version
field. Would it not be better to have a default value for that field, so that
new entries don't get forgotten when we filter by Fix Version looking for
issues to fix for the next release?
I think that not setting
[
https://issues.apache.org/jira/browse/SOLR-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-780:
---
Fix Version/s: 1.4
Affects Version/s: 1.4
Enhance SpellCheckComponent to
[
https://issues.apache.org/jira/browse/SOLR-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-783:
---
Fix Version/s: 1.4
DIH - Better support for handling delta-imports per entity
runtime error when starting solr 1.3. it appears solr.servlet package is
not in the source code. any idea? thanks
SEVERE: Exception starting filter SolrRequestFilter
java.lang.ClassNotFoundException: org.apache.solr.servlet.SolrDispatchFilter
at
On 23-Sep-08, at 12:33 PM, Otis Gospodnetic wrote:
Hi,
When people add new issues to JIRA they most often don't set the
Fix Version field. Would it not be better to have a default value
for that field, so that new entries don't get forgotten when we
filter by Fix Version looking for
Based on our experience with using Jira in this manner, I would agree
with Mike that you do not want to automatically assign the Fix
Version.
Once you go down this path, you wind up with a steadily growing wave
of deferred issues that are constantly getting pushed out to the next
release.
24 matches
Mail list logo
