See http://hudson.zones.apache.org/hudson/job/Solr-trunk/558/changes
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628613#action_12628613
]
Jason Rutherglen commented on SOLR-567:
---
Without looking at the code, what has changed?
CoreDescriptor holds wrong instance dir for single core
---
Key: SOLR-753
URL: https://issues.apache.org/jira/browse/SOLR-753
Project: Solr
Issue Type: Bug
Affects Versions: 1.3
[
https://issues.apache.org/jira/browse/SOLR-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-753:
Attachment: SOLR-753.patch
the fix
CoreDescriptor holds wrong instance dir for single core
MultiCore.java is renamed to CoreContainer
and SolrCore is changed a lot
On Fri, Sep 5, 2008 at 4:27 PM, Jason Rutherglen (JIRA) [EMAIL PROTECTED]
wrote:
[
I would like to have a higher level discussion about the integration
before mucking about in the SOLR code again. This way work invested
is work that will not have to be changed too much later on. Do folks
have ideas about how they would want to do this?
On Fri, Sep 5, 2008 at 7:03 AM, Noble
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628624#action_12628624
]
Noble Paul commented on SOLR-567:
-
As a general approach , A pluggable SolrCore does not look
Ocean integration should really be targeted at solr 2 I think, so API
compatibility shouldn't be a large barrier.
Noble Paul (JIRA) wrote:
[
Ok, SOLR 2 can be a from the ground up rewrite? That would make
things much easier. Otherwise Noble you are correct the integration
from my perspective is messy and there would be a lot of things that
are currently in SOLR that are unnecessary.
On Fri, Sep 5, 2008 at 9:00 AM, Mark Miller [EMAIL
On Fri, Sep 5, 2008 at 9:03 AM, Jason Rutherglen
[EMAIL PROTECTED] wrote:
Ok, SOLR 2 can be a from the ground up rewrite?
Sort-of... I think that's up for discussion at this point, but enough
should change that keeping Java APIs back compatible is not a priority
(just my opinion of course).
Postponing Ocean Integration towards 2.0 is not a good idea. First of
all we do not know when 2.0 is going to happen. delaying such a good
feature till 2.0 is wasting time.
My assumption was that Actually realtime search may have nothing to do
with the core itself . It may be fine with a
On Fri, Sep 5, 2008 at 9:40 AM, Noble Paul നോബിള് नोब्ळ्
[EMAIL PROTECTED] wrote:
If with a few changes we can start the integration, that is
the best way forward.
That's a good point too... I think collecting all the requirements for
Solr2 will help from a design perspective, but if people
IMO, you are underestimating the difficulty of integrating Ocean with
Solr's current API's.
Also, Jason has already mentioned that Ocean is much more than just
realtime search. Adding realtime search to something like solr 1.5 is a
different goal than possibly integrating the Ocean work that
Ok... Well I did try that. I think that can be done as well. IMO
schemas should be avoided with realtime. Otherwise there is a
nightmare with schema versions. The current config files would not be
used. How do you propose the non-integration of those things? It
would seem to create a strange
On Fri, Sep 5, 2008 at 7:23 PM, Mark Miller [EMAIL PROTECTED] wrote:
IMO, you are underestimating the difficulty of integrating Ocean with Solr's
current API's.
OK. you are right. Actually ,I did not mean the ocean integration. I
am mostly interested in the Realtime search part. If we take one
Solr logo on admin pages should always link back to main admin page
---
Key: SOLR-754
URL: https://issues.apache.org/jira/browse/SOLR-754
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Timm updated SOLR-754:
---
Attachment: SOLR-754.patch
Solr logo on admin pages should always link back to main admin page
That may be the way to go, however there are many issues that you will
probably run into, the same ones I ran into that made the integration
difficult as mentioned. I could be wrong however. Most realtime
search is something on the order of a 5-10 second delay and there is
no transaction log. I
These all sound like good ideas for solr2. The ability to handle changes
on the fly easily across many machines would be an awesome place to
reach. Dynamically changing field schema/stopword stuff is also a great
feature to have.
I think the key to reaching those goals is to really join the
On Fri, Sep 5, 2008 at 7:59 PM, Mark Miller [EMAIL PROTECTED] wrote:
These all sound like good ideas for solr2. The ability to handle changes on
the fly easily across many machines would be an awesome place to reach.
Dynamically changing field schema/stopword stuff is also a great feature to
On Fri, Sep 5, 2008 at 10:45 AM, Shalin Shekhar Mangar
[EMAIL PROTECTED] wrote:
Cloud computing cluster having hundreds of servers is a niche area
limited to few (and they already have their systems in place without Solr).
Any efforts of integration must keep in mind our users and their needs.
[
https://issues.apache.org/jira/browse/SOLR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628650#action_12628650
]
Francisco Sanmartín commented on SOLR-42:
-
The patch is for solr 1.3?
I tried to
Yonik Seeley wrote:
On Fri, Sep 5, 2008 at 10:45 AM, Shalin Shekhar Mangar
[EMAIL PROTECTED] wrote:
Cloud computing cluster having hundreds of servers is a niche area
limited to few (and they already have their systems in place without Solr).
Any efforts of integration must keep in mind our
I've noticed a NullPointerException being thrown in the FacetComponent's
countFacets method when I specify duplicate shards in the URL (e.g.
...shards=localhost:8983/solr,localhost:8983/solr...facet=on). Should I
create a JIRA issue for this, or is it just user error?
--
View this message in
facet.limit=-1 does not work in distributed search
--
Key: SOLR-755
URL: https://issues.apache.org/jira/browse/SOLR-755
Project: Solr
Issue Type: Bug
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley reassigned SOLR-755:
-
Assignee: Yonik Seeley
facet.limit=-1 does not work in distributed search
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628670#action_12628670
]
Wojtek Piaseczny commented on SOLR-755:
---
Hi Yonik,
I submitted a patch for SOLR 748
On Fri, Sep 5, 2008 at 8:26 PM, Yonik Seeley [EMAIL PROTECTED] wrote:
We all scratch our own itch in open-source... good, practical
scalability to high levels is an interest of mine :-)
Many will choose their solution based on it's ability to scale to
their most optimistic projections... so
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628704#action_12628704
]
Yonik Seeley commented on SOLR-755:
---
I also just found and fixed a bug in
Make DisjunctionMaxQueryParser generally useful by supporting all query types.
--
Key: SOLR-756
URL: https://issues.apache.org/jira/browse/SOLR-756
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Harris updated SOLR-284:
--
Attachment: rich.patch
THIS IS A BREAKING CHANGE TO RICH.PATCH! CLIENT URLs NEED TO BE UPDATED!
All
[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-756:
--
Attachment: SolrPluginUtilsDisMax.patch
The patch file is only to be applied on SolrPluginUtils.java.
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Kotthoff updated SOLR-755:
---
Attachment: SOLR-755.patch
I could swear that this was working for me a while back before I abandoned
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-755:
--
Attachment: SOLR-755.patch
patch attached
facet.limit=-1 does not work in distributed search
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628716#action_12628716
]
Yonik Seeley commented on SOLR-755:
---
Whoops, you snuck in first... thanks Lars.
Although, I
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628719#action_12628719
]
Lars Kotthoff commented on SOLR-755:
Ah, good point. I was testing with facet.mincount=1.
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628725#action_12628725
]
Lars Kotthoff commented on SOLR-755:
bq. Back compatibility.
Right. What's going to
SolrQueryParser should support escaping of characters in lieu of analysis for
prefix wildcard fuzzy searches.
-
Key: SOLR-757
URL:
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628728#action_12628728
]
Lars Kotthoff commented on SOLR-755:
bq. So... the only question left is if this should
Enhance DisMaxQParserPlugin to support full-Solr syntax and to support
alternate escaping strategies.
-
Key: SOLR-758
URL:
[
https://issues.apache.org/jira/browse/SOLR-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-758:
--
Attachment: AdvancedQParserPlugin.java
DisMaxQParserPlugin.java
[
https://issues.apache.org/jira/browse/SOLR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-755.
---
Resolution: Fixed
Fix Version/s: 1.3
ASL for this patch granted, and patch committed to trunk
It looks like all of the client directory is now included...
This is true after SOLR-510 was resolved.
including python which we don't even know works with trunk. Also,
If we need to remove python client from release,
we could reopen SOLR-510 and test the patch:
-
[
https://issues.apache.org/jira/browse/SOLR-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-646:
---
Affects Version/s: (was: 1.3)
1.4
Assignee:
44 matches
Mail list logo
