complete, no other steps are required.
References:
https://issues.apache.org/jira/browse/SOLR-11486
https://issues.apache.org/jira/browse/SOLR-10335
https://wiki.apache.org/solr/SolrSecurity
--
Regards,
Shalin Shekhar Mangar.
-
To
tham Digital Science)
References:
https://issues.apache.org/jira/browse/SOLR-11482
https://issues.apache.org/jira/browse/SOLR-11477
https://wiki.apache.org/solr/SolrSecurity
--
Regards,
Shalin Shekhar Mangar.
-
To unsubscribe, e-mail:
, please try another mirror. This also applies to Maven access.
--
Regards,
Shalin Shekhar Mangar.
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
CVE-2017-9803: Security vulnerability in kerberos delegation token functionality
Severity: Important
Vendor:
The Apache Software Foundation
Versions Affected:
Apache Solr 6.2.0 to 6.6.0
Description:
Solr's Kerberos plugin can be configured to use delegation tokens,
which allows an application
CVE-2017-7660: Security Vulnerability in secure inter-node
communication in Apache Solr
Severity: Important
Vendor:
The Apache Software Foundation
Versions Affected:
Solr 5.3 to 5.5.4
Solr 6.0 to 6.5.1
Description:
Solr uses a PKI based mechanism to secure inter-node communication
when securit
istributing releases. It is possible that the mirror you
are using may not have replicated the release yet. If that is the
case, please try another mirror. This also applies to Maven access.
--
Regards,
Shalin Shekhar Mangar.
---
access.
--
Regards,
Shalin Shekhar Mangar.
releases. It is possible that the mirror you
are using may not have replicated the release yet. If that is the
case, please try another mirror. This also goes for Maven access.
Happy searching!
--
Shalin Shekhar Mangar on behalf of the Lucene PMC
---
> > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>
> -------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>
--
Regards,
Shalin Shekhar Mangar.
June 2013, Apache Lucene™ 4.3.1 available
The Lucene PMC is pleased to announce the release of Apache Lucene 4.3.1
Apache Lucene is a high-performance, full-featured text search engine
library written entirely in Java. It is a technology suitable for
nearly any application that requires full-text
a
static snapshot of the index, merging using addIndexes(IndexReader...) is
safe even if the source index has a writer open?
--
Regards,
Shalin Shekhar Mangar.
On Wed, Jul 15, 2009 at 4:49 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> OK I opened & fixed https://issues.apache.org/jira/browse/LUCENE-1744.
>
>
Wow, that was fast! Thanks!
--
Regards,
Shalin Shekhar Mangar.
xed,tokenized>
scores[i] = 0.0
documents[i] = Document
stored/uncompressed,indexed,tokenized>
scores[i] = 0.6085842
documents[i] = Document
stored/uncompressed,indexed,tokenized>
scores[i] = 0.6211337
Sort: new SortField(null, SortField.SCORE, false)
documents[i] = Document
stored/uncompressed,indexed,tokenized>
scores[i] = 1.4054651
documents[i] = Document
stored/uncompressed,indexed,tokenized>
scores[i] = 0.0
documents[i] = Document
stored/uncompressed,indexed,tokenized>
scores[i] = 0.6211337
documents[i] = Document
stored/uncompressed,indexed,tokenized>
scores[i] = 0.6085842
--
Regards,
Shalin Shekhar Mangar.
On Fri, Mar 6, 2009 at 5:01 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
>
> Shalin, did you ever get to the bottom of this?
>
No, I'll try to reproduce this and let you know tomorrow.
--
Regards,
Shalin Shekhar Mangar.
work around this by using IW.commit and
keeping the IW open.
--
Regards,
Shalin Shekhar Mangar.
>>
> >> Welcome Patrick!
> >>
> >> ryan
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: java-user-h...@lucene.apache.org
> >
> >
>
--
Regards,
Shalin Shekhar Mangar.
> Is there an implementation pattern for this use case using lucene? This
> seems like a common feature on various sites and I'm wondering if lucene
> can be used to support this.
>
> Thanks in advance.
>
> Peter Hayes
>
>
>
--
Regards,
Shalin Shekhar Mangar.
as using. However if it is of any help,
it should be one of r707499, r719351, r723985 or r724059.
You can see the original report at
http://markmail.org/message/xybvkcjx5kraqvoh
--
Regards,
Shalin Shekhar Mangar.
t;>
>> Cheers
>> Mark
>>
>>
>> ---------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Regards,
Shalin Shekhar Mangar.
rent system by adding a
dummy document which Solr can read/write -- not very elegant but it can work
:-)
Using the version came to my mind because I didn't see it as very useful by
itself. It is just the current time stamp as a long, incremented for every
commit.
--
Regards,
Shalin Shekhar Mangar.
mpare the
master and slave index with a reference point (log position). If it becomes
possible for us to specify a version number during a commit, we can use the
master's version number on the slave. This can help us compare the two
indices. Not sure if that API change will be generally useful. Thoughts?
--
Regards,
Shalin Shekhar Mangar.
; replicated everytime. But when the optimize happens the transfer
> size
> > >>>>> can be really large. So I am thinking of doing the optimize
> > >>>>> separately on master and slave .
> > >>>>>
> > >>>>> So far, so good. But how can I really know that after the optimize
> > the
> > >>>>> indexes are indeed the same or no documents got added in between.?
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> On Fri, Aug 29, 2008 at 3:13 PM, Karl Wettin <
> [EMAIL PROTECTED]>
> > >>>>> wrote:
> > >>>>>
> > >>>>>>
> > >>>>>> 29 aug 2008 kl. 11.35 skrev Noble Paul നോബിള് नोब्ळ्:
> > >>>>>>
> > >>>>>> hi,
> > >>>>>>>
> > >>>>>>> I wish to know if the contents of two indexes have same data.
> > >>>>>>> will all the files be exactly same if I put same set of documents
> > to
> > >>>>>>>
> > >>>>>> both?
> > >>>>>
> > >>>>>>
> > >>>>>> If you insert the documents in the same order with the same
> settings
> > >>>>>> and
> > >>>>>> both indices are optimized, then the files ought to be
> identitical.
> > >>>>>> I'm
> > >>>>>> however not sure.
> > >>>>>>
> > >>>>>> The instantiated index contrib module contains a test that assert
> > two
> > >>>>>>
> > >>>>> index
> > >>>>>
> > >>>>>> readers are identical. You could use this to be really sure, but
> it
> > it
> > >>>>>> a
> > >>>>>> rather long running process for a large index:
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> >
> http://svn.apache.org/repos/asf/lucene/java/trunk/contrib/instantiated/src/test/org/apache/lucene/store/instantiated/TestIndicesEquals.java
> > >>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Perhaps you should explain why you need to do this.
> > >>>>>>
> > >>>>>>
> > >>>>>> karl
> > >>>>>>
> > -
> > >>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >>>>>> For additional commands, e-mail: [EMAIL PROTECTED]
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> --Noble Paul
> > >>>>>
> > >>>>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >>> For additional commands, e-mail: [EMAIL PROTECTED]
> > >>>
> > >>>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> >
> > --
> > --Noble Paul
> >
>
--
Regards,
Shalin Shekhar Mangar.
Any help is appreciated. We are not using SOLR
> > >> >>
> > >> >> I also interested in knowing what will be the best way so that I
> can
> > >> >> scale
> > >> >> my application adding more boxes for search if our load increases.
> > >> >>
> > >> >> Thanks.
> > >> >>
> > >> >> --
> > >> >> View this message in context:
> > >> >>
> > >>
> >
> http://www.nabble.com/Replicating-Lucene-Index-with-out-SOLR-tp19191752p19191752.html
> > >> >> Sent from the Lucene - General mailing list archive at Nabble.com.
> > >> >
> > >> >
> > >> >
> > >>
> > >> --
> > >> View this message in context:
> > >>
> >
> http://www.nabble.com/Replicating-Lucene-Index-with-out-SOLR-tp19191752p19193670.html
> > >> Sent from the Lucene - General mailing list archive at Nabble.com.
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> >
> http://www.nabble.com/Replicating-Lucene-Index-with-out-SOLR-tp19193696p19194576.html
> > Sent from the Lucene - Java Users mailing list archive at Nabble.com.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Regards,
Shalin Shekhar Mangar.
/solr/trunk/src/java/org/apache/solr/analysis/WordDelimiterFilter.java?revision=684908&view=markup
--
Regards,
Shalin Shekhar Mangar.
> Any comment on this? Efficiency? No need to maintain any intermediate data?
>
> Thanks much,
> -Peng
--
Regards,
Shalin Shekhar Mangar.
scribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Regards,
Shalin Shekhar Mangar.
ck out
> https://issues.apache.org/jira/browse/SOLR-469.
Please note that SOLR-469 a.k.a DataImportHandler is now available in the
Solr nightly builds.
http://wiki.apache.org/solr/DataImportHandler
--
Regards,
Shalin Shekhar Mangar.
tor) should I change? Thank you.
>
> _
> Stay in touch when you're away with Windows Live Messenger.
>
> http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_messenger2_072008
--
Regards,
Shalin Shekhar Mangar.
That's great. Thanks!
On Wed, Jul 2, 2008 at 6:04 PM, Michael McCandless
<[EMAIL PROTECTED]> wrote:
>
> OK I think that makes sense. I'll take it. I'll add an isOptimized() to
> IndexCommit.
>
> Mike
>
> Shalin Shekhar Mangar wrote:
>
>> Ok
ile (pending deletes against the segment) then the index is not optimized.
>
> But in general, Lucene's file format can change from release to release
> (it's not an API), so if something changes in the future you may have to
> revisit this heuristic.
>
> Mike
>
> S
mmit points represent
> "interesting" times to the application would be to call IW.optimize() then
> IW.commit() (if you are using trunk) or just IW.close(), then look at the
> last IndexCommit passed to your deletion policy's onCommit() and record
> yourself that
Hi,
I'm implementing a custom IndexDeletionPolicy. An IndexCommit object
does not have any information whether it's index is optimized or not.
How can a IndexDeletionPolicy know which IndexCommit instances
corresponded to optimized indices?
--
Regards,
Shalin Shek
----------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Regards,
Shalin Shekhar Mangar.
gt; Thanks and Regards
>प्रशांत सराफ
> (Prashant Saraf)
> SE-II
> Cross Country Infotech
> Ext : 72543
> www.crosscountry.in
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional
http://www.nabble.com/indexing-database-tp15832696p15832696.html
> > Sent from the Nutch - User mailing list archive at Nabble.com.
> >
> >
> > ------------
ion. Also read about an index server.
>
> -- Jan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Regards,
Shalin Shekhar Mangar.
---
36 matches
Mail list logo
