[jira] Commented: (SOLR-1154) allow specifying solr configuration file through system property to simplify deployment procedure in certain cases
[
https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708316#action_12708316
]
Noble Paul commented on SOLR-1154:
--
what I am going to say is hack (not at all elegant). but will work
{code}
${diable-master: false}
commit
schema.xml,stopwords.txt
http://localhost:8983/solr/replication
00:00:60
{code}
when you start the server in the master you can pass in -Dslave=disabled and in
the slave pass in -Dmaster=disabled
this will change the tag value and it can become disabled automatically
BTW the root of the problem is that there is no way to include snippets of
configuration from external files . I guess that needs to be addressed
separately
> allow specifying solr configuration file through system property to simplify
> deployment procedure in certain cases
> --
>
> Key: SOLR-1154
> URL: https://issues.apache.org/jira/browse/SOLR-1154
> Project: Solr
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Jianhan
>Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1154.patch, SOLR-1154.patch
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> Hi,
> I wanted to use this parameter to specify different solr configuration files
> for master and slave to simplify deployment procedure. Unfortunately, I can't
> dynamically replace the value of this parameter. Basically, what I want is
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> solrconfig-master.xml
>
>
> for master instance, and
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> solrconfig-slave.xml
>
>
> for slave instance.
> Ideally, if I can use system property for its value like in solrconfig.xml.
> For example,
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> ${solr.config.filename: solrconfig.xml}
>
>
> but I learned that in general we can't use system property in web.xml.
> I realize that I can use replication of config file to achieve this, but I
> thought that creates unnecessary dependencies for slaves on master instance.
> So here is my proposal:
> make SolrDispatchFilter look up another init parameter, say
> 'solrconfig-filename-property', and its value is a system property name, and
> if this property is set, we get the file name, otherwise nothing happens (of
> course, if both exist, 'solrconfig-filename' takes precedence). This will
> give us maximum flexibility of specifying configuration files for different
> instances.
> Your thoughts?
> Thanks,
> Jianhan
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1156) Sort TermsComponent results by frequency
[ https://issues.apache.org/jira/browse/SOLR-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Weber updated SOLR-1156: - Attachment: SOLR-1156.patch Added some unit tests. > Sort TermsComponent results by frequency > > > Key: SOLR-1156 > URL: https://issues.apache.org/jira/browse/SOLR-1156 > Project: Solr > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Matt Weber > Attachments: SOLR-1156.patch, SOLR-1156.patch, SOLR-1156.patch, > SOLR-1156.patch > > > TermsComponent should be able to return results sorted by frequency. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1154) allow specifying solr configuration file through system property to simplify deployment procedure in certain cases
[
https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianhan updated SOLR-1154:
--
Attachment: SOLR-1154.patch
upload a patch
> allow specifying solr configuration file through system property to simplify
> deployment procedure in certain cases
> --
>
> Key: SOLR-1154
> URL: https://issues.apache.org/jira/browse/SOLR-1154
> Project: Solr
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Jianhan
>Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1154.patch, SOLR-1154.patch
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> Hi,
> I wanted to use this parameter to specify different solr configuration files
> for master and slave to simplify deployment procedure. Unfortunately, I can't
> dynamically replace the value of this parameter. Basically, what I want is
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> solrconfig-master.xml
>
>
> for master instance, and
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> solrconfig-slave.xml
>
>
> for slave instance.
> Ideally, if I can use system property for its value like in solrconfig.xml.
> For example,
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> ${solr.config.filename: solrconfig.xml}
>
>
> but I learned that in general we can't use system property in web.xml.
> I realize that I can use replication of config file to achieve this, but I
> thought that creates unnecessary dependencies for slaves on master instance.
> So here is my proposal:
> make SolrDispatchFilter look up another init parameter, say
> 'solrconfig-filename-property', and its value is a system property name, and
> if this property is set, we get the file name, otherwise nothing happens (of
> course, if both exist, 'solrconfig-filename' takes precedence). This will
> give us maximum flexibility of specifying configuration files for different
> instances.
> Your thoughts?
> Thanks,
> Jianhan
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1154) allow specifying solr configuration file through system property to simplify deployment procedure in certain cases
[
https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708266#action_12708266
]
Jianhan commented on SOLR-1154:
---
This is regarding http://markmail.org/message/5kqx3xps3ejwpazu
For particular problem, i.e. allow dynamically determine an instance to be
master or slave, we could have a different solution: add to master/slave
configuration an additional property that can be used to determine an instance
to be a master or slave. Here is how
in solrconfig.xml, include this block
${diable-master: false}
commit
schema.xml,stopwords.txt
${diable-slave: false}
http://localhost:8983/solr/replication
00:00:60
and in ReplicationHandler, in addition to check the existence of "master" or
"slave", we check whether "master" or "slave" is disabled or not
i.e. replace
if (slave != null) {
with
if (slave != null) {
if ( ! "true".equals(slave.get("isDisabled"))) {
> allow specifying solr configuration file through system property to simplify
> deployment procedure in certain cases
> --
>
> Key: SOLR-1154
> URL: https://issues.apache.org/jira/browse/SOLR-1154
> Project: Solr
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Jianhan
>Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1154.patch
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> Hi,
> I wanted to use this parameter to specify different solr configuration files
> for master and slave to simplify deployment procedure. Unfortunately, I can't
> dynamically replace the value of this parameter. Basically, what I want is
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> solrconfig-master.xml
>
>
> for master instance, and
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> solrconfig-slave.xml
>
>
> for slave instance.
> Ideally, if I can use system property for its value like in solrconfig.xml.
> For example,
>
> SolrRequestFilter
> org.apache.solr.servlet.SolrDispatchFilter
>
> solrconfig-filename
> ${solr.config.filename: solrconfig.xml}
>
>
> but I learned that in general we can't use system property in web.xml.
> I realize that I can use replication of config file to achieve this, but I
> thought that creates unnecessary dependencies for slaves on master instance.
> So here is my proposal:
> make SolrDispatchFilter look up another init parameter, say
> 'solrconfig-filename-property', and its value is a system property name, and
> if this property is set, we get the file name, otherwise nothing happens (of
> course, if both exist, 'solrconfig-filename' takes precedence). This will
> give us maximum flexibility of specifying configuration files for different
> instances.
> Your thoughts?
> Thanks,
> Jianhan
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin
Hi Jayson, Thanks, I'll take a look in the next few days. The current patch doesn't guarantee index consistency during post-commit callback hooks, right? This could be a problem for index replication. (Incidentally, I'm rather unfamiliar with the new java-based replication design. Anyone care to comment on the implications?) cheers, -MIke On 10-May-09, at 10:54 AM, jayson.minard wrote: Mike, I revamped the DirectUpdateHandler2 into DirectUpdateHandler3 in SOLR-1155, probably ready enough for your review to see if locking makes sense for current Lucene behavior. https://issues.apache.org/jira/browse/SOLR-1155 --j Mike Klaas wrote: On 7-May-09, at 10:36 AM, jayson.minard wrote: Does every thread really need to notify the update handler of the commit interval/threshold being reached, or really just the first thread that notices should send the signal, or better yet a background commit watching thread so that no "foreground" thread has to pay attention at all. That is assuming they wouldn't need to block like they are now for a reason I'm likely unaware of... This is due to the way Lucene was designed (although recent improvements in Lucene mean we can do better here). See the recent thread "Autocommit blocking adds?" on solr-user for a related discussion. As the person who first wrote the multi-threaded-ness of DUH2, I'd be very happy to promptly review any improvements made to it. -Mike -- View this message in context: http://www.nabble.com/DirectUpdateHandler2-threads-pile-up-behind-scheduleCommitWithin-tp23431691p23472391.html Sent from the Solr - Dev mailing list archive at Nabble.com.
[jira] Commented: (SOLR-1156) Sort TermsComponent results by frequency
[ https://issues.apache.org/jira/browse/SOLR-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708223#action_12708223 ] Matt Weber commented on SOLR-1156: -- The current tests pass: [junit] Running org.apache.solr.handler.component.TermsComponentTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 6.944 sec I will work on some unit tests for the new sorting functionality. > Sort TermsComponent results by frequency > > > Key: SOLR-1156 > URL: https://issues.apache.org/jira/browse/SOLR-1156 > Project: Solr > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Matt Weber > Attachments: SOLR-1156.patch, SOLR-1156.patch, SOLR-1156.patch > > > TermsComponent should be able to return results sorted by frequency. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1156) Sort TermsComponent results by frequency
[ https://issues.apache.org/jira/browse/SOLR-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708212#action_12708212 ] Yonik Seeley commented on SOLR-1156: It would be nice for this to have some tests before it's committed Actually, does this pass the current tests since the default sort order was changed and the tests weren't changed? perhaps if the current tests are small enough and never test for order of results, they do still pass? > Sort TermsComponent results by frequency > > > Key: SOLR-1156 > URL: https://issues.apache.org/jira/browse/SOLR-1156 > Project: Solr > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Matt Weber > Attachments: SOLR-1156.patch, SOLR-1156.patch, SOLR-1156.patch > > > TermsComponent should be able to return results sorted by frequency. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1156) Sort TermsComponent results by frequency
[ https://issues.apache.org/jira/browse/SOLR-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Weber updated SOLR-1156: - Attachment: SOLR-1156.patch Updated to use BoundedTreeSet instead of a regular TreeSet. Don't know why I didn't use this in the first place. > Sort TermsComponent results by frequency > > > Key: SOLR-1156 > URL: https://issues.apache.org/jira/browse/SOLR-1156 > Project: Solr > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Matt Weber > Attachments: SOLR-1156.patch, SOLR-1156.patch, SOLR-1156.patch > > > TermsComponent should be able to return results sorted by frequency. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-196) A PHP response writer for Solr
[ https://issues.apache.org/jira/browse/SOLR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708190#action_12708190 ] Yonik Seeley commented on SOLR-196: --- Perhaps escaping isn't correct for this particular field? Can you post the output from fl=recommended? Is it particular values of that field that cause the problem, or *any* document retrieved with that field? If particular values, perhaps you could narrow it down and just post the problematic value? > A PHP response writer for Solr > -- > > Key: SOLR-196 > URL: https://issues.apache.org/jira/browse/SOLR-196 > Project: Solr > Issue Type: New Feature > Components: clients - php, search >Reporter: Paul Borgermans > Fix For: 1.3 > > Attachments: SOLR-192-php-responsewriter.patch, > SOLR-196-PHPResponseWriter.patch > > > It would be useful to have a PHP response writer that returns an array to be > eval-ed directly. This is especially true for PHP4.x installs, where there is > no built in support for JSON. > This issue attempts to address this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SOLR-196) A PHP response writer for Solr
[ https://issues.apache.org/jira/browse/SOLR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708172#action_12708172 ] Andrew McCombe edited comment on SOLR-196 at 5/11/09 12:57 PM: --- I'm finding occasionally that the return from the php response writer fails to unserialize in PHP5. I have a number of fields in the 'fl=' parameter of my query and it works fine until I add the field name 'recommended'. It then fails. If I remove all other field names and leave fl=recommended it still fails. I can see the output and it contains the results, but fails on unserializing in PHP. Is 'recommended' some sort of reserved word? was (Author: euperia): I'm finding occasionally that the return from the php response writer fails to unserialize in PHP5. > A PHP response writer for Solr > -- > > Key: SOLR-196 > URL: https://issues.apache.org/jira/browse/SOLR-196 > Project: Solr > Issue Type: New Feature > Components: clients - php, search >Reporter: Paul Borgermans > Fix For: 1.3 > > Attachments: SOLR-192-php-responsewriter.patch, > SOLR-196-PHPResponseWriter.patch > > > It would be useful to have a PHP response writer that returns an array to be > eval-ed directly. This is especially true for PHP4.x installs, where there is > no built in support for JSON. > This issue attempts to address this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-196) A PHP response writer for Solr
[ https://issues.apache.org/jira/browse/SOLR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708172#action_12708172 ] Andrew McCombe commented on SOLR-196: - I'm finding occasionally that the return from the php response writer fails to unserialize in PHP5. > A PHP response writer for Solr > -- > > Key: SOLR-196 > URL: https://issues.apache.org/jira/browse/SOLR-196 > Project: Solr > Issue Type: New Feature > Components: clients - php, search >Reporter: Paul Borgermans > Fix For: 1.3 > > Attachments: SOLR-192-php-responsewriter.patch, > SOLR-196-PHPResponseWriter.patch > > > It would be useful to have a PHP response writer that returns an array to be > eval-ed directly. This is especially true for PHP4.x installs, where there is > no built in support for JSON. > This issue attempts to address this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1156) Sort TermsComponent results by frequency
[ https://issues.apache.org/jira/browse/SOLR-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708158#action_12708158 ] Yonik Seeley commented on SOLR-1156: Thanks Matt! This should probably use a BoundedTreeSet or a PriorityQueue to avoid keeping (and ordering) all of the terms in memory? > Sort TermsComponent results by frequency > > > Key: SOLR-1156 > URL: https://issues.apache.org/jira/browse/SOLR-1156 > Project: Solr > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Matt Weber > Attachments: SOLR-1156.patch, SOLR-1156.patch > > > TermsComponent should be able to return results sorted by frequency. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SOLR-1154) allow specifying solr configuration file through system property to simplify deployment procedure in certain cases
I understand. I'd love to see a different way for us to load sections of
solrconfig.xml dynamically so we don't have to modify web.xml. For now what
I need is to be able to include
this part
for my master instance, and this part
for my slave instance, but I don't seem to be able to find a way to do it.
Also, yes, other than solrconfig.xml, everything else is a simple copy. The
way I see it is that once solrconfig.xml/solrconfig-slove.xml is configured,
we will have a lot of changes on schema.xml, synonyms.txt, stopwords.txt
etc, and if we have multiple copies of these files, we have to remember to
copy over every time we make changes. That is what I meant when I said
'potential maintenance problem'.
Thanks,
Jianhan
2009/5/11 Noble Paul നോബിള് नोब्ळ्
> in general , modifying web.xml is discouraged. so, this is the first
> time someone is asking for config to be added into the configuration
> of SolrDispatchFilter.
>
> when you say the whole directory ,other than solrconfig.xml everything
> else is a simple copy , right?
>
> On Mon, May 11, 2009 at 10:20 PM, Jian Han Guo wrote:
> > You are right that keeping directories for solr home can solve this
> problem.
> > The only issue is that you then have to keep two copies of everything in
> the
> > solr home directory, which is a potential maintenance problem. I still
> yet
> > to figure out how to extract the common part of solrconfig.xml and
> > solrconfig-slave.xml, but at least we only duplicate one file instead of
> the
> > whole directory if this feature is available.
> >
> > Thanks,
> >
> > Jianhan
> >
> > On Sun, May 10, 2009 at 10:09 PM, Noble Paul (JIRA)
> wrote:
> >
> >>
> >>[
> >>
> https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707885#action_12707885
> ]
> >>
> >> Noble Paul commented on SOLR-1154:
> >> --
> >>
> >> replying to the mail http://markmail.org/message/52vj7lughfplxmks
> >>
> >> it is still possible to achieve what you want to do by setting a
> different
> >> solr.solr.home from the system property. when you package your war keep
> two
> >> instance directories one for master and another for slave. pass
> different
> >> solr.solr.home as command line param when you start the server
> >>
> >> > allow specifying solr configuration file through system property to
> >> simplify deployment procedure in certain cases
> >> >
> >>
> --
> >> >
> >> > Key: SOLR-1154
> >> > URL: https://issues.apache.org/jira/browse/SOLR-1154
> >> > Project: Solr
> >> > Issue Type: Improvement
> >> >Affects Versions: 1.4
> >> >Reporter: Jianhan
> >> >Priority: Minor
> >> > Fix For: 1.4
> >> >
> >> > Attachments: SOLR-1154.patch
> >> >
> >> > Original Estimate: 5h
> >> > Remaining Estimate: 5h
> >> >
> >> > Hi,
> >> > I wanted to use this parameter to specify different solr configuration
> >> files for master and slave to simplify deployment procedure.
> Unfortunately,
> >> I can't dynamically replace the value of this parameter. Basically, what
> I
> >> want is
> >> >
> >> > SolrRequestFilter
> >> >
> >> org.apache.solr.servlet.SolrDispatchFilter
> >> >
> >> > solrconfig-filename
> >> > solrconfig-master.xml
> >> >
> >> >
> >> > for master instance, and
> >> >
> >> > SolrRequestFilter
> >> >
> >> org.apache.solr.servlet.SolrDispatchFilter
> >> >
> >> > solrconfig-filename
> >> > solrconfig-slave.xml
> >> >
> >> >
> >> > for slave instance.
> >> > Ideally, if I can use system property for its value like in
> >> solrconfig.xml. For example,
> >> >
> >> > SolrRequestFilter
> >> >
> >> org.apache.solr.servlet.SolrDispatchFilter
> >> >
> >> > solrconfig-filename
> >> > ${solr.config.filename:
> solrconfig.xml}
> >> >
> >> >
> >> > but I learned that in general we can't use system property in web.xml.
> >> > I realize that I can use replication of config file to achieve this,
> but
> >> I thought that creates unnecessary dependencies for slaves on master
> >> instance.
> >> > So here is my proposal:
> >> > make SolrDispatchFilter look up another init parameter, say
> >> 'solrconfig-filename-property', and its value is a system property name,
> and
> >> if this property is set, we get the file name, otherwise nothing happens
> (of
> >> course, if both exist, 'solrconfig-filename' takes precedence). This
> will
> >> give us maximum flexibility of specifying configuration files for
> different
> >> instances.
> >> > Your thoughts?
> >> > Thanks,
> >> > Jianhan
> >>
> >> --
> >> This message is automatically generated by JIRA.
> >> -
> >> You can reply to this email to add a comment to the issue online.
> >>
> >>
> >
>
>
>
> -
Re: [jira] Commented: (SOLR-1154) allow specifying solr configuration file through system property to simplify deployment procedure in certain cases
in general , modifying web.xml is discouraged. so, this is the first
time someone is asking for config to be added into the configuration
of SolrDispatchFilter.
when you say the whole directory ,other than solrconfig.xml everything
else is a simple copy , right?
On Mon, May 11, 2009 at 10:20 PM, Jian Han Guo wrote:
> You are right that keeping directories for solr home can solve this problem.
> The only issue is that you then have to keep two copies of everything in the
> solr home directory, which is a potential maintenance problem. I still yet
> to figure out how to extract the common part of solrconfig.xml and
> solrconfig-slave.xml, but at least we only duplicate one file instead of the
> whole directory if this feature is available.
>
> Thanks,
>
> Jianhan
>
> On Sun, May 10, 2009 at 10:09 PM, Noble Paul (JIRA) wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707885#action_12707885]
>>
>> Noble Paul commented on SOLR-1154:
>> --
>>
>> replying to the mail http://markmail.org/message/52vj7lughfplxmks
>>
>> it is still possible to achieve what you want to do by setting a different
>> solr.solr.home from the system property. when you package your war keep two
>> instance directories one for master and another for slave. pass different
>> solr.solr.home as command line param when you start the server
>>
>> > allow specifying solr configuration file through system property to
>> simplify deployment procedure in certain cases
>> >
>> --
>> >
>> > Key: SOLR-1154
>> > URL: https://issues.apache.org/jira/browse/SOLR-1154
>> > Project: Solr
>> > Issue Type: Improvement
>> > Affects Versions: 1.4
>> > Reporter: Jianhan
>> > Priority: Minor
>> > Fix For: 1.4
>> >
>> > Attachments: SOLR-1154.patch
>> >
>> > Original Estimate: 5h
>> > Remaining Estimate: 5h
>> >
>> > Hi,
>> > I wanted to use this parameter to specify different solr configuration
>> files for master and slave to simplify deployment procedure. Unfortunately,
>> I can't dynamically replace the value of this parameter. Basically, what I
>> want is
>> >
>> > SolrRequestFilter
>> >
>> org.apache.solr.servlet.SolrDispatchFilter
>> >
>> > solrconfig-filename
>> > solrconfig-master.xml
>> >
>> >
>> > for master instance, and
>> >
>> > SolrRequestFilter
>> >
>> org.apache.solr.servlet.SolrDispatchFilter
>> >
>> > solrconfig-filename
>> > solrconfig-slave.xml
>> >
>> >
>> > for slave instance.
>> > Ideally, if I can use system property for its value like in
>> solrconfig.xml. For example,
>> >
>> > SolrRequestFilter
>> >
>> org.apache.solr.servlet.SolrDispatchFilter
>> >
>> > solrconfig-filename
>> > ${solr.config.filename: solrconfig.xml}
>> >
>> >
>> > but I learned that in general we can't use system property in web.xml.
>> > I realize that I can use replication of config file to achieve this, but
>> I thought that creates unnecessary dependencies for slaves on master
>> instance.
>> > So here is my proposal:
>> > make SolrDispatchFilter look up another init parameter, say
>> 'solrconfig-filename-property', and its value is a system property name, and
>> if this property is set, we get the file name, otherwise nothing happens (of
>> course, if both exist, 'solrconfig-filename' takes precedence). This will
>> give us maximum flexibility of specifying configuration files for different
>> instances.
>> > Your thoughts?
>> > Thanks,
>> > Jianhan
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
--
-
Noble Paul | Principal Engineer| AOL | http://aol.com
Re: [jira] Commented: (SOLR-1154) allow specifying solr configuration file through system property to simplify deployment procedure in certain cases
You are right that keeping directories for solr home can solve this problem.
The only issue is that you then have to keep two copies of everything in the
solr home directory, which is a potential maintenance problem. I still yet
to figure out how to extract the common part of solrconfig.xml and
solrconfig-slave.xml, but at least we only duplicate one file instead of the
whole directory if this feature is available.
Thanks,
Jianhan
On Sun, May 10, 2009 at 10:09 PM, Noble Paul (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707885#action_12707885]
>
> Noble Paul commented on SOLR-1154:
> --
>
> replying to the mail http://markmail.org/message/52vj7lughfplxmks
>
> it is still possible to achieve what you want to do by setting a different
> solr.solr.home from the system property. when you package your war keep two
> instance directories one for master and another for slave. pass different
> solr.solr.home as command line param when you start the server
>
> > allow specifying solr configuration file through system property to
> simplify deployment procedure in certain cases
> >
> --
> >
> > Key: SOLR-1154
> > URL: https://issues.apache.org/jira/browse/SOLR-1154
> > Project: Solr
> > Issue Type: Improvement
> >Affects Versions: 1.4
> >Reporter: Jianhan
> >Priority: Minor
> > Fix For: 1.4
> >
> > Attachments: SOLR-1154.patch
> >
> > Original Estimate: 5h
> > Remaining Estimate: 5h
> >
> > Hi,
> > I wanted to use this parameter to specify different solr configuration
> files for master and slave to simplify deployment procedure. Unfortunately,
> I can't dynamically replace the value of this parameter. Basically, what I
> want is
> >
> > SolrRequestFilter
> >
> org.apache.solr.servlet.SolrDispatchFilter
> >
> > solrconfig-filename
> > solrconfig-master.xml
> >
> >
> > for master instance, and
> >
> > SolrRequestFilter
> >
> org.apache.solr.servlet.SolrDispatchFilter
> >
> > solrconfig-filename
> > solrconfig-slave.xml
> >
> >
> > for slave instance.
> > Ideally, if I can use system property for its value like in
> solrconfig.xml. For example,
> >
> > SolrRequestFilter
> >
> org.apache.solr.servlet.SolrDispatchFilter
> >
> > solrconfig-filename
> > ${solr.config.filename: solrconfig.xml}
> >
> >
> > but I learned that in general we can't use system property in web.xml.
> > I realize that I can use replication of config file to achieve this, but
> I thought that creates unnecessary dependencies for slaves on master
> instance.
> > So here is my proposal:
> > make SolrDispatchFilter look up another init parameter, say
> 'solrconfig-filename-property', and its value is a system property name, and
> if this property is set, we get the file name, otherwise nothing happens (of
> course, if both exist, 'solrconfig-filename' takes precedence). This will
> give us maximum flexibility of specifying configuration files for different
> instances.
> > Your thoughts?
> > Thanks,
> > Jianhan
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: Solr search PHP
Take a look at this: http://code.google.com/p/solr-php-client/ Thanks, Matt Weber eSr Technologies http://www.esr-technologies.com On May 11, 2009, at 6:12 AM, The Spider wrote: Hi, I want to integrate solr search in my php application. First I want to know that, do solr search provide a way so that we do no need to create any queries for searching? Secondly, Please tell me how to proceed. Thanks in advance -- View this message in context: http://www.nabble.com/Solr-search-PHP-tp23483068p23483068.html Sent from the Solr - Dev mailing list archive at Nabble.com.
[jira] Updated: (SOLR-1139) SolrJ TermsComponent Query and Response Support
[ https://issues.apache.org/jira/browse/SOLR-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Weber updated SOLR-1139: - Attachment: SOLR-1139-WITH_SORT_SUPPORT.patch Here is a patch that adds support for the sort parameters in SOLR-1156. > SolrJ TermsComponent Query and Response Support > --- > > Key: SOLR-1139 > URL: https://issues.apache.org/jira/browse/SOLR-1139 > Project: Solr > Issue Type: New Feature > Components: clients - java >Affects Versions: 1.4 >Reporter: Matt Weber >Priority: Minor > Attachments: SOLR-1139-WITH_SORT_SUPPORT.patch, SOLR-1139.patch, > SOLR-1139.patch, SOLR-1139.patch > > > SolrJ should support the new TermsComponent that was introduced in Solr 1.4. > It should be able to: > - set TermsComponent query parameters via SolrQuery > - parse the TermsComponent response -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1139) SolrJ TermsComponent Query and Response Support
[ https://issues.apache.org/jira/browse/SOLR-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Weber updated SOLR-1139: - Attachment: SOLR-1139.patch Updated to reflect latest changes to TermsComponent in rev. 773447. > SolrJ TermsComponent Query and Response Support > --- > > Key: SOLR-1139 > URL: https://issues.apache.org/jira/browse/SOLR-1139 > Project: Solr > Issue Type: New Feature > Components: clients - java >Affects Versions: 1.4 >Reporter: Matt Weber >Priority: Minor > Attachments: SOLR-1139.patch, SOLR-1139.patch, SOLR-1139.patch > > > SolrJ should support the new TermsComponent that was introduced in Solr 1.4. > It should be able to: > - set TermsComponent query parameters via SolrQuery > - parse the TermsComponent response -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-773) Incorporate Local Lucene/Solr
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708025#action_12708025
]
Chris A. Mattmann commented on SOLR-773:
Hi Guys,
I'm interested in using LocalSOLR and the 4 proposals described by Yonik above
are exactly what I need for an app here to stand up oceans data search here at
work. We need the ability to do bounding box queries and spatial queries of the
following form:
1. Lat, Lon, Radius Template Element
"&lat={geo:lat?}&lon={geo:lon?}&r={geo:radius?}"
With latitude and longitude in decimal degrees in EPSG:4326 format. The radius
parameter is in meters along the surface.
2. Box Template Element
"&bbox={geo:box?}"
Bounding box coordinates in EPSG:4326 format in decimal degrees.
Ordering is "west, south, east, north".
3. Polygon
"&p={geo:polygon?}"
Replaced with the latitude/longitude pairs describing a bounding area to
perform a search within. The polygon is defined in latitude, longitude pairs,
in clockwise order around the polygon, with
I realize that #3 above is probably a ways off, but how close are we to #1 and
#2? I'm trying to push to use SOLR here rather than leverage a custom or COTS
solution, but will need at least support for #1 and #2 to make any headway. I'm
willing to contribute and help out towards this -- I just want to find out
where we are.
Thanks!
Cheers,
Chris
> Incorporate Local Lucene/Solr
> -
>
> Key: SOLR-773
> URL: https://issues.apache.org/jira/browse/SOLR-773
> Project: Solr
> Issue Type: New Feature
>Reporter: Grant Ingersoll
>Assignee: Grant Ingersoll
>Priority: Minor
> Attachments: lucene.tar.gz, SOLR-773-local-lucene.patch,
> SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch,
> SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch, SOLR-773.patch,
> SOLR-773.patch, spatial-solr.tar.gz
>
>
> Local Lucene has been donated to the Lucene project. It has some Solr
> components, but we should evaluate how best to incorporate it into Solr.
> See http://lucene.markmail.org/message/orzro22sqdj3wows?q=LocalLucene
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1155) Change DirectUpdateHandler2 to allow concurrent adds during an autocommit
[ https://issues.apache.org/jira/browse/SOLR-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayson Minard updated SOLR-1155: Attachment: SOLR-1155.patch Changed external commit interface to not have locking, but rather query if a commit/rollback/optimize is already running to accomplish the same goal. Also ensure no locking around waiting for searcher after commit or optimize. > Change DirectUpdateHandler2 to allow concurrent adds during an autocommit > - > > Key: SOLR-1155 > URL: https://issues.apache.org/jira/browse/SOLR-1155 > Project: Solr > Issue Type: Improvement > Components: search >Affects Versions: 1.3 >Reporter: Jayson Minard > Attachments: SOLR-1155.patch, SOLR-1155.patch, SOLR-1155.patch, > SOLR-1155.patch, SOLR-1155.patch, SOLR-1155.patch, SOLR-1155.patch, > SOLR-1155.patch, SOLR-1155.patch, SOLR-1155.patch > > > Currently DirectUpdateHandler2 will block adds during a commit, and it seems > to be possible with recent changes to Lucene to allow them to run > concurrently. > See: > http://www.nabble.com/Autocommit-blocking-adds---AutoCommit-Speedup--td23435224.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Solr search PHP
Hi, I want to integrate solr search in my php application. First I want to know that, do solr search provide a way so that we do no need to create any queries for searching? Secondly, Please tell me how to proceed. Thanks in advance -- View this message in context: http://www.nabble.com/Solr-search-PHP-tp23483068p23483068.html Sent from the Solr - Dev mailing list archive at Nabble.com.
[jira] Updated: (SOLR-1150) OutofMemoryError on enabling highlighting
[ https://issues.apache.org/jira/browse/SOLR-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Gargate updated SOLR-1150: Attachment: SOLR-1150.patch I have attached the patch file with previous suggested code changes.. > OutofMemoryError on enabling highlighting > - > > Key: SOLR-1150 > URL: https://issues.apache.org/jira/browse/SOLR-1150 > Project: Solr > Issue Type: Improvement > Components: highlighter >Affects Versions: 1.4 >Reporter: Siddharth Gargate > Fix For: 1.4 > > Attachments: SOLR-1150.patch > > > Please refer to following mail thread > http://markmail.org/message/5nhkm5h3ongqlput > I am testing with 2MB document size and just 500 documents. Indexing is > working fine even with 128MB heap size. But on searching Solr throws OOM > error. This issue is observed only when we enable highlighting. While > indexing I am storing 1 MB text. While searching Solr reads all the 500 > documents in the memory. It also reads the complete 1 MB stored field in the > memory for all 500 documents. Due to this 500 docs * 1 MB * 2 (2 bytes per > char) = 1000 MB memory is required for searching. > This memory usage can be reduced by reading one document at a time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
