Just another piece of gem that I know if is that if your feature branch
name is in lowercase, commits there don't generate jira comments.
On Wed, 20 Nov, 2019, 3:02 AM Michael Sokolov, wrote:
> got it, thanks!
>
> On Tue, Nov 19, 2019 at 4:10 PM Dawid Weiss wrote:
> >
> > > Hoss said branches
Ok, solved. Solr 8.2 accepted this statement:
select(search(testcollection,q="test",df="Default",defType="edismax",fl="id",
qt="/export", sort="id asc"),id,if(eq(1,1),Y,N) as found)
and return to me the expected results. Note that around Y and N there is no
". Solr 8.3 requires the following
Could it be that Solr 8.3 is more strict on the if statement?
the statement if(eq(1,1),Y,N)
is supposed to return the character Y (not the field). In Solr 8.2 it
returns the character Y, but in Solr 8.3 not.
On Tue, Nov 19, 2019 at 11:21 PM Jörn Franke wrote:
> thanks i will find another
thanks i will find another installation of Solr, but last time the
underlying queries to the export handler were correct. What was wrong was
the generated field "found" based on the if statement based NOT on any data
in the collectioj. As said, in Solr 8.3 the id fields are returned, but
not the
Welcome Houston,
Looking forward to working with you
On Tue, Nov 19, 2019 at 12:58 AM Martin Gainty wrote:
>
> welcome Houston!
> martin-
>
> From: Michael McCandless
> Sent: Sunday, November 17, 2019 10:32 AM
> To: dev@lucene.apache.org
> Cc: Houston Putman
>
got it, thanks!
On Tue, Nov 19, 2019 at 4:10 PM Dawid Weiss wrote:
>
> > Hoss said branches must be named starting jira/, but I'm not familiar
> > with this convention.
>
> This convention is merely so that when you do "git branch -r" the
> branches displayed are sorted and presented in some
> Hoss said branches must be named starting jira/, but I'm not familiar
> with this convention.
This convention is merely so that when you do "git branch -r" the
branches displayed are sorted and presented in some sane order
(because of prefixes).
> If we follow that, can we use github to
Hi, can someone point me to how-to for feature branches? Recently,
Hoss said branches must be named starting jira/, but I'm not familiar
with this convention. Is it written down somewhere? If we follow that,
can we use github to coordinate PR's against a feature branch among
multiple developers?
> it's already been addressed - by you - in LUCENE-8920 (Erick's note was
about it's overall success rate for the past 7 days)
Yeah, thanks. Brain caught up with hands and I realized that must be
it shortly after posting.
On Tue, Nov 19, 2019 at 1:33 AM Ishan Chattopadhyaya
wrote:
>
> Thanks
