> Can we provide a sequence of git commands for folks to run? Or will the
> official guidance be to create new local clones of each repo?
Yes, I will do that in the readme file placed on master branch, once cleaned up.
Don't panic, please. git is a wonderful version control system in that
it
> I am curious as to the status of /solr code being buildable without /lucene.
> The steps above at #2 say for each project to remove the other side. Is Solr
> ready? Where will Solr get the Lucene binaries?
https://issues.apache.org/jira/browse/SOLR-14759
I am pleased to announce the availability of Apache PyLucene 8.8.1.
Apache PyLucene, a subproject of Apache Lucene, is a Python extension for
accessing Apache Lucene Core. Its goal is to allow you to use Lucene's text
indexing and searching capabilities from Python. It is API compatible with
This vote has passed.
Thank you all who voted !
Andi..
On Mon, 8 Mar 2021, Michael McCandless wrote:
+1
I ran my usual smoke test: install JCC, PyLucene, then index and optimize
the first 100K documents from a Wikipedia English snapshot, and run a
couple queries.
Sorry for being late to
Made a branch in my normal repo:
https://github.com/cominvent/lucene-solr/tree/silly-pr and spun it up as a PR
against your solr-only test repo https://github.com/dsmiley/lucene-solr/pull/1
Looks like this won't be a problem :)
I imagine a documentation like this HOWTO I created in the Solr
+1
I ran my usual smoke test: install JCC, PyLucene, then index and optimize
the first 100K documents from a Wikipedia English snapshot, and run a
couple queries.
Sorry for being late to the party too!
Mike McCandless
http://blog.mikemccandless.com
On Mon, Mar 1, 2021 at 9:35 PM Andi Vajda
Answering my own question -- apparently Solr on master now depends on
snapshot builds of Lucene published by ASF Nexus:
https://issues.apache.org/jira/browse/SOLR-14759
Cool!
About PRs: Someone should experiment here to see what's involved before
the split. To get this started, I pushed a
For the Ref Guide a good amount of the traffic is probably the old redirect
rules in Confluence that explicitly went to 6_6 for a good reason *at the
time*. A blanket fix to those rules (it was a discrete list of pages in a text
file) to remove the URL in the path would cause them to be
One of us will get there first and should share. For my part, I intend to
add a new remote, pull the branches from it, then use "git worktree" to add
a new local work tree alongside my existing ones (for lucene_solr master,
lucene_solr branch_8x). I call my current remote "apache" but I might
Can we provide a sequence of git commands for folks to run? Or will the
official guidance be to create new local clones of each repo?
On Mon, Mar 8, 2021 at 12:18 PM David Smiley wrote:
> Yeah, I agree with Jan -- don't rename the GitHub repo. It's going to be
> painful no matter what and a
Yeah, I agree with Jan -- don't rename the GitHub repo. It's going to be
painful no matter what and a rename doesn't seem appropriate.
I am curious as to the status of /solr code being buildable without
/lucene. The steps above at #2 say for each project to remove the other
side. Is Solr
Hi,
There are 324 open PRs. Some numbers:
Number updated last month: 40
Number not touched last 4 months: 249 (77%)
With LUCENE in title: 93
With SOLR in title: 181
It would be nice to auto migrate but some times you just have to face changes
and do some extra work :)
Given how easy it is to
Yep, that's on my plan.
Jan
> 8. mar. 2021 kl. 17:56 skrev Michael Sokolov :
>
> maybe send an email to the list informing anyone who's listening?
>
> On Mon, Mar 8, 2021 at 8:07 AM Jan Høydahl wrote:
>>
>> It's been one week, and there were 5 respondents. Three explicitly in favour
>> of
Hi Dawid,
> My plan is as follows:
>
> 1. DISABLE CI jobs and anything that pulls from current master. (Uwe,
> would you do help me with this?)
Yes, I can do this. I have meetings on Wednesday, but I can already do this
tomorrow evening.
> 2. Branch master to lucene/main and solr/main. Remove
maybe send an email to the list informing anyone who's listening?
On Mon, Mar 8, 2021 at 8:07 AM Jan Høydahl wrote:
>
> It's been one week, and there were 5 respondents. Three explicitly in favour
> of sunsetting the list.
> This was not a VOTE, but I'll interpret the response as lazy
I'd like to commit SOLR-14381 and LUCENE-9302 together before the fork,
please. I'll hopefully wrap up by Tuesday.
On Mon, 8 Mar, 2021, 9:51 pm Uwe Schindler, wrote:
> Hi again,
>
> we can maybe "improve" the situation a bit: On Github you can (with
> Admin/Ownership rights) rename a project.
Hi again,
we can maybe "improve" the situation a bit: On Github you can (with
Admin/Ownership rights) rename a project. So my suggestion:
- Check pull requests and count how many affect solr and how many affect Lucene.
- In cooperation with Infra rename the Github project
Actually my question was more around what happens with PRs that cut across
both Lucene and Solr -- but your answer was helpful in itself, thank you!
On Mon, 8 Mar 2021, 21:46 Uwe Schindler, wrote:
> I think the problem was what happens with the PR in Githubs user
> interface.
>
> This question
I think the problem was what happens with the PR in Githubs user interface.
This question was asked many times, answer is simple: NO you can't move over
Pull requests to different repositories on Github! It's also impossible to
export and reimport them. People have to recreate them.
Dawid is
> What happens to open PRs?
A pull request on github is essentially a diff between two commits.
Existing PRs have to be placed on top of the new development branch.
Note these repositories are (initially) identical with lucene-solr so
if somebody clones the solr repo and the solr-lucene repo,
What happens to open PRs?
On Mon, 8 Mar 2021 at 7:28 PM, Dawid Weiss wrote:
> I think my message got buried among other messages, so starting a new
> thread.
>
> With Solr established, I think we're ready to proceed with forking the
> git repository from:
>
>
I think my message got buried among other messages, so starting a new thread.
With Solr established, I think we're ready to proceed with forking the
git repository from:
https://git-wip-us.apache.org/repos/asf/lucene-solr.git
to:
(Lucene)
https://git-wip-us.apache.org/repos/asf/lucene.git
Hello All,
We have a use case where we want to enable auto-complete for the help manual
in our project.
Currently the documents are created using bunch of xml files which are then
parsed into text version and then this version is indexed in Lucene. This
gives us a workable solution for
It's been one week, and there were 5 respondents. Three explicitly in favour of
sunsetting the list.
This was not a VOTE, but I'll interpret the response as lazy consensus, and
proceed with removing the mention of the list on the website today.
Is there some step to take to shut the list down
24 matches
Mail list logo
