ng content using the Knowledge Graph entities.
>
>
> *Your help will be appreciated highly.*
>
> Many thanks
> Gautam Kanaujia
> India
>
--
*Doug Turnbull **| CTO* | OpenSource Connections
<http://opensourceconnections.com>, LLC | 240.476.9983
Author: Relevant Search
-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
> This e-mail and all contents, including attachments, is considered to be
> Company Confidential unless explicitly stated otherwise, regardless
> of whether attachments are marked as such.
&g
> > projects (downstream from Lucene).
>> >
>> > The situation we find ourselves now is different to what it was
>> > before: recent and ongoing development for the most part falls within
>> > Solr or Lucene exclusively.
>> >
>> >
>> > This e-mail is for discussing the idea and presentin
tion, but it's likely to cause some
> confusion for existing users.
> >
> > 2) Complementary relationship
> > When Lucene and Solr are built together, Solr can always maintain the
> latest Lucene.
> > In my personal opinion, it's a great advantage of Solr.
>
ested consumer.
> >>
> >> Erik
> >>
> >
> >
> > --
> > Regards,
> >
> > Atri
> > Apache Concerted
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@luc
mm, just to clarify, this is not an "again" sort of situation: Solr was
> not a top-level project before. It was and still is a sub-project of
> Apache Lucene.
>
> And the proposal is to now split it out as its own (new) top-level
> project, Apache Solr.
>
> Mike Mc
o join David
>> Smiley as co-author on the first Solr book, we went on and did a total of
>> three editions of that book. Phew!
>>
>> Once I got to sit on stage as a judge for Stump the Chump, it was Erick,
>> Erik, and Eric ;-)
>>
>> After doing Solr for a g
ile and text format. What do you guys think about making all the
>>>> readmes to markdown file rather than text files, and a standard template?
>>>> >
>>>> >
>>>> > --
>>>> > Regards:
>>>> > Pinkesh Sharma
>>>
iley
>>>> wrote:
>>>>
>>>>>
>>>>> Rob wrote:
>>>>>
>>>>>> Why should I wait weeks/months for some explicit review
>>>>>>
>>>>> Ask for a review, which as this document says is
> >> The level of effort involved would be considerable, whether it happens
>> >> quickly or slowly. It might be the kind of thing we just don't want to
>> >> try and do.
>> >>
>> >> I'm not opposed to the idea, and I might even b
g
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
>
>
> --
> --
[
https://issues.apache.org/jira/browse/LUCENE-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859165#comment-16859165
]
Doug Turnbull commented on LUCENE-8841:
---
Big +1, though I suspect it woul
-
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
> --
> Lucene/Solr Search Committer (PMC), Developer, Author, Speaker
> LinkedIn: http://linkedin.com/in/davidwsmiley
>
;
> >
> > Is there a way to store numerical vectors (vector based index) and
> perform search based on Approximate Nearest Neighbor class of algorithms in
> Lucene?
> >
> >
> >
> > If not, has there been any interests in the topic so far?
> >
> >
> >
I like that idea Alan. The trick is for QueryBuilder's 'newSynonymQuery' to
be useful in that context, you need to pass terms with metadata down to the
subclass. This is what I started working on a few weeks ago:
https://github.com/o19s/lucene-solr/commit/0fc3930671ef002cfbb5e3d52b6f8edc3715bf14
), but some of it
is just defining practices / patterns / tools that enable these things in
Lucene-based search. Some may require no work, or some may require
supporting functionality.
-Doug
On Wed, Nov 21, 2018 at 9:23 AM Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> I agree t
> already have a TermFrequencyAttribute to alter the frequency of a term
> when
> > indexing so we could have the same mechanism for query term boosting ?
> >
> > Le dim. 18 nov. 2018 à 02:24, Doug Turnbull <
> > dturnb...@opensourceconnections.com> a écrit :
> &
e doc
freq of each concept recreates the priority ordering you guys came up with.
That's pretty neat!
-Doug
On Wed, Nov 21, 2018 at 7:20 AM Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> Great thoughts Jim - +1 to your idea
>
> One brainstorm I had, is taxonomies ha
n the QueryBuilder. It could
>> be a new attribute that token filters would use when they produce stacked
>> tokens and that the QueryBuilder checks when he builds the SynonymQuery. We
>> already have a TermFrequencyAttribute to alter the frequency of a term when
>&g
add the complexity you want in a
> subclass.
> However I think there is another area we need to fix, the scoring of
> multi-terms synonyms is broken (compared to the SynonymQuery) and could be
> improved so we need something similar than the SynonymQuery that handles
> multi
t would go on the roadmap...
On Sat, Nov 17, 2018 at 1:15 AM J. Delgado
wrote:
> What about the use of word embeddings (see
>
> https://towardsdatascience.com/introduction-to-word-embedding-and-word2vec-652d0c2060fa)
> to compute word similarity?
>
> On Sat, Nov 17, 2018 at 5:52
Hey folks,
I wanted to open up a discussion about a change to the usage of
SynonymQuery. The goal here is to have a broader library of queries that
can address other cases where related terms occupy the same position but
don't have the same meaning (such as hypernyms, hyponyms, meronyms,
ambiguous
[
https://issues.apache.org/jira/browse/LUCENE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688424#comment-16688424
]
Doug Turnbull commented on LUCENE-8563:
---
Ah... I assumed "Adrie
[
https://issues.apache.org/jira/browse/LUCENE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688382#comment-16688382
]
Doug Turnbull commented on LUCENE-8563:
---
Thanks [~jpountz] - My feeling i
[
https://issues.apache.org/jira/browse/LUCENE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687268#comment-16687268
]
Doug Turnbull commented on LUCENE-8563:
---
I feel perhaps one way forward i
[
https://issues.apache.org/jira/browse/LUCENE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684091#comment-16684091
]
Doug Turnbull commented on LUCENE-8563:
---
For the sake of this discussion, he
[
https://issues.apache.org/jira/browse/LUCENE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684080#comment-16684080
]
Doug Turnbull edited comment on LUCENE-8563 at 11/12/18 5:0
[
https://issues.apache.org/jira/browse/LUCENE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684080#comment-16684080
]
Doug Turnbull commented on LUCENE-8563:
---
It would modify ordering when dea
[
https://issues.apache.org/jira/browse/SOLR-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682427#comment-16682427
]
Doug Turnbull commented on SOLR-12238:
--
What can we do to get this functiona
[
https://issues.apache.org/jira/browse/SOLR-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463830#comment-16463830
]
Doug Turnbull commented on SOLR-12238:
--
Just want to say I've been watc
[
https://issues.apache.org/jira/browse/LUCENE-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278893#comment-16278893
]
Doug Turnbull commented on LUCENE-7996:
---
Just FYI for upstream impact, LTR mo
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277462#comment-16277462
]
Doug Turnbull commented on SOLR-11662:
--
Thanks for helping with the change David
[
https://issues.apache.org/jira/browse/SOLR-11698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275741#comment-16275741
]
Doug Turnbull commented on SOLR-11698:
--
I'm considering adding query time
ppendix, etc.)
> [asciidoctor:convert] asciidoctor: ERROR: solr-glossary.adoc: line 1:
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
>
>
> On Sat, Dec 2, 2017 at 11:42 PM, Doug Turnbull <
> dturnb...@opensourceconnections.com> wrote:
>
>>
e:
>
> MG>see below
>
>
> --
> *From:* Doug Turnbull
> *Sent:* Friday, December 1, 2017 9:17 PM
> *To:* dev@lucene.apache.org
> *Subject:* Solr Ref Guide not building
>
> Hello!
>
> I'm trying to update the Solr Ref guide
re's anything obvious I'm doing wrong, please let me know
A more complete log can be found here
https://gist.github.com/softwaredoug/36fe87f0d63403e7be22d5a2ff8af073
Thanks for any help
-Doug
--
Consultant, OpenSource Connections. Contact info at
http://o19s.com/about-us/doug-turnbull/; Free/Busy (http://bit.ly/dougs_cal)
[
https://issues.apache.org/jira/browse/SOLR-11698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Turnbull updated SOLR-11698:
-
Summary: Query-time per-field query settings (ie analyzers,
autoGeneratePhraseQueries, etc) (was
Doug Turnbull created SOLR-11698:
Summary: Query-time fieldType query settings (ie analyzers,
autoGeneratePhraseQueries, etc)
Key: SOLR-11698
URL: https://issues.apache.org/jira/browse/SOLR-11698
-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
> --
Consultant, OpenSource Connections. Contact info at
http://o19s.com/about-us/doug-turnbull/; Free/Busy (http://bit.ly/dougs_cal)
t; one chain, with some qualifier on each element to say to which named chains
> it applies to (if not all)? I dunno; trade-offs, trade-offs.
> >
> > ~ David
> >
> > On Thu, Nov 23, 2017 at 11:03 AM Doug Turnbull <
> dturnb...@opensourceconnections.com> wrote:
>
r_nosyn title text&defType=edismax
On Thu, Nov 23, 2017 at 10:50 AM Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> I wonder if there's been any thought by the community to refactoring
> fieldTypes to allow multiple query-time analyzers per indexed field?
>
d=actor&qf.actor_syn.analyzer=with_synonyms&qf.actorNoSyn.autoGeneratePhraseQueries=false
I think this could be a pretty powerful syntax, but would require
refactoring of the field type and edismax (and possibly other query
parsers) quite a bit
Any thoughts?
Best
-Doug
--
Consultant, OpenS
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263377#comment-16263377
]
Doug Turnbull edited comment on SOLR-11662 at 11/22/17 9:3
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263377#comment-16263377
]
Doug Turnbull commented on SOLR-11662:
--
PR updated, patch can be viewed here
h
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262567#comment-16262567
]
Doug Turnbull commented on SOLR-11662:
--
Great! And that would actually let me su
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262468#comment-16262468
]
Doug Turnbull commented on SOLR-11662:
--
Thanks Adrien! Yes, it could be move
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Turnbull updated SOLR-11662:
-
Description:
This patch customizes the query-time behavior when query terms overlap
positions
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261549#comment-16261549
]
Doug Turnbull commented on SOLR-11662:
--
Associated pull request https://github
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Turnbull updated SOLR-11662:
-
Summary: Make overlapping query term scoring configurable per field type
(was: More than
[
https://issues.apache.org/jira/browse/SOLR-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Turnbull updated SOLR-11662:
-
Description:
This patch customizes the query-time behavior when query terms overlap
positions
Doug Turnbull created SOLR-11662:
Summary: More than SynonymQuery: Let overlapping query terms model
hypernym/hyponym relationships
Key: SOLR-11662
URL: https://issues.apache.org/jira/browse/SOLR-11662
Something I found helpful was to go back to very early Lucene versions.
That let's you see the essential functionality in relatively
straightforward Java code. You can get a sense for how Lucene is
structured. Functionality has been built around this since. The Java has
been battle tested, refactor
Sounds great. I agree!
I can imagine there might be really old client libraries/integrations that
assume XML without sending a wt, but I think it's ok to break those sorts
of things in a major release. And those folks can learn to send wt=xml
-Doug
On Fri, Apr 14, 2017 at 2:53 PM Trey Grainger
Definitely start with Solr unless you have some specialized use case.
Lucene skills can come up in a Solr context (ie if you wanted to write
plugins)
I would also recommend:
- Solr in Action
- Lucene in Action (out of date, but many concepts still valid)
- Apache Solr Ref Guide (
https://cwiki.apa
As an aside, I'm pretty sure if anyone wanted to write a new edition of
Lucene in Action, and you're masochistic enough to write a book for a top
tier tech book publisher, I'd be happy to introduce you to someone at
Manning :)
And Lucene In Action is a very good read, will help you get the big ide
[
https://issues.apache.org/jira/browse/SOLR-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591921#comment-15591921
]
Doug Turnbull commented on SOLR-9418:
-
Looking at your patch (I'm not a commi
[
https://issues.apache.org/jira/browse/LUCENE-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467891#comment-15467891
]
Doug Turnbull commented on LUCENE-7436:
---
Fix is here https://github.com/ap
Doug Turnbull created LUCENE-7436:
-
Summary: MinHashFilter has package-local constructor and constants
Key: LUCENE-7436
URL: https://issues.apache.org/jira/browse/LUCENE-7436
Project: Lucene - Core
I see it more of a performance tweak than a relevance thing. matches on
stopwords introduce the potential for many more documents to be scored.
Large collections usually should have a high min-should-match, so more than
likely queries with at least one or two non-stopwords that dramatically
limit
Hi Archit, I would make a strong argument for using Solr unless you have
some exotic requirements.
- Solr has distributed indexing and search built in, building your own
distributed system is non-trivial, just as Mark Miller :)
- Solr comes prebaked with an HTTP API for non search experts to inter
Is there anyway to maintain inbound links to confluence pages with the new
system? I'm just thinking about all the user group questions, stackoverflow
Qs, and the like that link to cwiki pages.
Is it possible to setup the right redirects for cwiki pages into the new
system?
Doug
On Thu, Aug 18, 2
[
https://issues.apache.org/jira/browse/SOLR-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413994#comment-15413994
]
Doug Turnbull commented on SOLR-9395:
-
Hmm that won't work, nm as you'd
[
https://issues.apache.org/jira/browse/SOLR-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413459#comment-15413459
]
Doug Turnbull edited comment on SOLR-9395 at 8/9/16 12:4
[
https://issues.apache.org/jira/browse/SOLR-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413459#comment-15413459
]
Doug Turnbull edited comment on SOLR-9395 at 8/9/16 12:4
[
https://issues.apache.org/jira/browse/SOLR-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413459#comment-15413459
]
Doug Turnbull commented on SOLR-9395:
-
Thanks [~hossman] and [~dsmiley]
Lots of
Doug Turnbull created SOLR-9395:
---
Summary: Add ceil/floor bounding to stats calculations
Key: SOLR-9395
URL: https://issues.apache.org/jira/browse/SOLR-9395
Project: Solr
Issue Type
[
https://issues.apache.org/jira/browse/SOLR-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397636#comment-15397636
]
Doug Turnbull commented on SOLR-9279:
-
+1
> Add greater than, less than, etc
olr
> > Issue Type: New Feature
> > Security Level: Public(Default Security Level. Issues are Public)
> > Components: search
> >Reporter: Doug Turnbull
> > Fix For: master (7.0)
> >
> > Attachments: SOLR
[
https://issues.apache.org/jira/browse/SOLR-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396118#comment-15396118
]
Doug Turnbull commented on SOLR-9279:
-
Looks great [~dsmiley]! Definitely a
[
https://issues.apache.org/jira/browse/SOLR-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394521#comment-15394521
]
Doug Turnbull commented on SOLR-9279:
-
[~hossman] Thanks for your help! Great po
[
https://issues.apache.org/jira/browse/SOLR-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Turnbull updated SOLR-9279:
Description:
If you use the "if" function query, you'll often expect to be able to us
[
https://issues.apache.org/jira/browse/SOLR-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363563#comment-15363563
]
Doug Turnbull commented on SOLR-9279:
-
Associated Pull request https://github
Doug Turnbull created SOLR-9279:
---
Summary: Add greater than, less than, etc in Solr function queries
Key: SOLR-9279
URL: https://issues.apache.org/jira/browse/SOLR-9279
Project: Solr
Issue
an entirely different
> repository and chew up bandwidth/disk resourcesto obtain it, and I do
> not care whether it is git or svn. As time marches on, fewer people
> will have reasons to look at the historical record.
>
> Thanks,
> Shawn
>
>
> --
re:
>> http://goo.gl/m6q3J8
>>
>> Dawid
>>
>> On Tue, Dec 8, 2015 at 10:49 PM, Upayavira wrote:
>> > You can't avoid having the history in SVN. The ASF has one large repo,
>> and
>> > won't be deleting that repo, so the history will su
ck what
> > it actually was.
> >
> > Will keep you posted.
> >
> > D.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.
that the svn-git bridge seems to have (both
>> memory leaks + history), perhaps the sooner we switch to git, the
>> better.
>>
>> -Yonik
>>
>> -----
>> To unsubscribe, e-mail: dev-unsubscr...@luce
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
>
> >
> >
> >
[
https://issues.apache.org/jira/browse/SOLR-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972743#comment-14972743
]
Doug Turnbull commented on SOLR-8201:
-
+1!
These little hints in the admin UI
[
https://issues.apache.org/jira/browse/SOLR-7341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959677#comment-14959677
]
Doug Turnbull commented on SOLR-7341:
-
I am really looking forward to this patch
gt;> - "External Configuration via XML” does perhaps not impress much
> anymore.
> >> - "Extensible Plugin Architecture” is almost a duplicate of "Powerful
> Extensions"
> >>
> >> --
> >> Jan Høydahl, search solution architect
> >> Cominvent AS - www.cominvent.com
> >
>
> --
e a Lucene or Solr issue?
> >
> > Thanks,
> > Ahmet
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
> >
>
> --
too if we can get it, but I don't know if it is really legal.
>
> The sourceforge CVS works, see IndexWriter:
>
> http://lucene.cvs.sourceforge.net/viewvc/lucene/lucene/com/lucene/index/IndexWriter.java?view=log
>
>
> On Sun, May 31, 2015 at 3:10 PM, Doug Turnbull
> wrote:
>
I have no dog in the svn vs git debate honestly.
I want to say how important it is to keep healthy history. I recently went
on a bit of code archeology dig recently to figure out why something in
Lucene was done the way it was. It was handy that the history went as far
back as it did, but I had to
oach for
> real-life response prediction/bidding problems in advertising and its very
> powerful. Of course, this is not the panacea, as there are still some
> issues with the approach, specially on the operational side. Let's keep
> the conversation going as I think we are on to
ding of systems that can do computational advertising,
> recommendations and specialized search systems, applicable to many domains.
>
> Code to support it (only elastic search for now):
> https://github.com/sdhu/elasticsearch-prediction
>
> -- J
>
>
>
>
>
[
https://issues.apache.org/jira/browse/SOLR-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931319#comment-13931319
]
Doug Turnbull commented on SOLR-5800:
-
Thanks for the patch Stefan. Will thi
[
https://issues.apache.org/jira/browse/SOLR-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Turnbull updated SOLR-5256:
Description:
There's been several times when I wish I could specify multiple queries through
[
https://issues.apache.org/jira/browse/SOLR-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Turnbull updated SOLR-5256:
Attachment: Solr-5256.patch
Patch to add hl.addlq
> Send multiple queries thro
Doug Turnbull created SOLR-5256:
---
Summary: Send multiple queries through highlighter
Key: SOLR-5256
URL: https://issues.apache.org/jira/browse/SOLR-5256
Project: Solr
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/SOLR-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772151#comment-13772151
]
Doug Turnbull commented on SOLR-4812:
-
+1 I've also been able to recr
91 matches
Mail list logo
