Re: Lucene Solr 3.1 RC1

the homebrew CMS soon. My impression from watching folks use it is that, while the (internal) interface isn't pretty, it simply does the job. That is, once people start using it, I don't hear any complaints. And for a relatively new piece of software, that strikes me as a success. Upayavira

Re: How to fetch title and content using Solr

Saif, you should ask your question on the solr-user email list, as this one is for those developing Lucene/Solr itself. Regards, Upayavira On Fri, 18 Mar 2011 04:19 -0700, saifahmad imsaifah...@gmail.com wrote: Hi, I am having a question-answer based data structure where I need to store

Re: svn commit: r1086678 - /lucene/dev/misc/announcements/solr-3.1.txt

). Upayavira --- Enterprise Search Consultant at Sourcesense UK, Making Sense of Open Source - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Brainstorming on Improving the Release Process

. Upayavira --- Enterprise Search Consultant at Sourcesense UK, Making Sense of Open Source - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Brainstorming on Improving the Release Process

On Thu, 31 Mar 2011 09:51 -0400, Robert Muir rcm...@gmail.com wrote: On Thu, Mar 31, 2011 at 9:40 AM, Upayavira u...@odoko.co.uk wrote: Are you willing to say more? I have a little time, and have done a lot of work with Ant. Maybe I could help. Upayavira Thanks, there is some

Re: Does solr support secure enterprise search?

security features. Upayavira On Fri, 01 Apr 2011 16:37 +0800, michong900617 michong900...@xmu.edu.cn wrote: Hello, Does solr support secure enterprise search? That's to say, person can only visit to the concerns of the information within their authorities. If I wanna meet the goal, what can I do

LogLevelSelection servlet

=WARNING The current logging servlet allows us to change many logging settings at once, however this URL would only allow one at a time - use multiple calls to change multiple entries. Thoughts? Oh, and should this be in a Jira ticket? Upayavira --- Enterprise Search Consultant at Sourcesense UK

Re: [VOTE] Release Lucene/Solr 3.2.0

on those releases, following the above process. This would give folks warning to get code in that is 'nearly' finished, yet prevent the release waiting on 'nearly finished' code. It would also put most of the power to make the release into the hands of the release manager. Thoughts? Upayavira

Re: Lucene SOLR WIKI - can't receive alerts

This is down to the upgrade from moin 1.8.4 to 1.8.8. Your ticket has been noted by the right person, hopefully we just now need to wait. Upayavira On Tue, 31 May 2011 11:27 -0400, Michael McCandless luc...@mikemccandless.com wrote: I also haven't received emails after May 19. I think

Re: repo doesn't like me this morning.

Is the EU one getting updates? I've seen a suggestion that commits from the US aren't getting to it. Upayavira On Mon, 13 Jun 2011 10:05 -0400, Robert Muir rcm...@gmail.com wrote: Yeah, but you can svn update/checkout/make patches etc until the main one comes back online, then switch back

Re: Wiki non-migration

On Fri, 2010-07-30 at 12:16 -0700, Marvin Humphrey wrote: On Fri, Jul 30, 2010 at 10:08:28AM +0100, Upayavira wrote: Moin can do access rights. Well, what do you know! http://wiki.apache.org/lucy/HelpOnAccessControlLists http://wiki.apache.org/lucy/HelpIndex Apparently

Re: Congratulations Yonik

On Wed, 2010-09-22 at 11:40 -0400, Yonik Seeley wrote: On Wed, Sep 22, 2010 at 11:08 AM, Upayavira u...@odoko.co.uk wrote: On nabbing the 1,000,000th commit at Apache! Thanks! And there were a lot of people watching to see who got it! Whew, good thing it wasn't something totally lame

Splitting indexes

to know (a) whether it is possible and (b) approximately what you'd need to do. Thanks in advance! Upayavira [1] http://www.slideshare.net/abial/eurocon2010 - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org

Re: possible to filter the output to commits@ list????

the kind of filtering you are talking about, but there's no harm looking! Upayavira On Tue, 19 Oct 2010 06:45 -0400, Michael McCandless luc...@mikemccandless.com wrote: On Mon, Oct 18, 2010 at 3:03 PM, Grant Ingersoll gsing...@apache.org wrote:  It was just a bit of a shocker for me the first

Re: Newbie question on distributed writes onto SolrCloud

does a MOD shard_count on the document ID. Also, it would have to split incoming posts and distrubute amongst shards (an incoming block of 500 documents would maybe end up as 5 posts of 100 if we had five shards). Upayavira

Re: Distributed Indexing

to the UpdateRequestHandler, and forward them to whichever shards the ShardPolicy suggested. 3. We plan to test our results by acceptance testing (we run Solr and see if it works ourselves) and writing a test class. Sounds great. Upayavira --- Enterprise Search Consultant at Sourcesense UK, Making Sense of Open

Re: Distributed Indexing

amongst shards. If you don't, it goes directly to the host you are posting to. Control remains in the hand of the person accessing Solr. Upayavira --- Enterprise Search Consultant at Sourcesense UK, Making Sense of Open Source

Re: Distributed Indexing

and repost everything. All documents would be re-indexed across all shards, but in the long run, there's no big issue with that. Upayavira On Fri, 28 Jan 2011 12:24 +, Upayavira u...@odoko.co.uk wrote: Hi Soheb, On Wed, 26 Jan 2011 16:29 +, Soheb Mahmood soheb.luc...@gmail.com wrote

Re: Distributed Indexing

who got this far - please chip in if you see better ways of doing this. Upayavira All the best William On Sat, Jan 29, 2011 at 11:56 PM, Upayavira u...@odoko.co.uk wrote: Lance, Firstly, we're proposing a ShardDistributionPolicy interface for which there is a default (mod

Re: Distributed Indexing

, and Solr doesn't need to know about it? I.e. your indexers are deciding what goes in what shard, not Solr? Upayavira On Tue, Feb 1, 2011 at 12:38 PM, Upayavira u...@odoko.co.uk wrote: On Tue, 01 Feb 2011 19:04 +, Alex Cowell alxc...@gmail.com wrote: I noticed there is a comment

Re: wind down for 3.1?

Just to be clear, are you proposing to release 3.1 of Lucene, Solr, or both? Upayavira On Thu, 03 Feb 2011 11:00 -0500, Robert Muir rcm...@gmail.com wrote: Hello, Per Shai's previous note, we decided we wanted to work towards a 3.1 release (he mentioned a target date of march 1, don't think

Re: Distributed Indexing

indexing? You are right, these will likely be lower for distributed indexing, however I'd suggest not worrying about it for now, as it is easy to tweak later. Upayavira --- Enterprise Search Consultant at Sourcesense UK, Making Sense of Open Source

Re: wind down for 3.1?

On Thu, 03 Feb 2011 16:43 -0500, Robert Muir rcm...@gmail.com wrote: On Thu, Feb 3, 2011 at 11:37 AM, Upayavira u...@odoko.co.uk wrote: Just to be clear, are you proposing to release 3.1 of Lucene, Solr, or both? Both: because our development is merged, I think it makes sense to merge

Re: Distributed Indexing

I'm saying that deterministic policies are a requirement that *some* people will want. Others might want a random spread. Thus, I'd have deterministic based on ID and random as the two initial implementations. Upayavira NB. In case folks haven't worked it out already, I have been tasked to mentor

Re: Distributed Indexing

). Upayavira On Sun, 06 Feb 2011 23:08 +, Alex Cowell alxc...@gmail.com wrote: Hey, We're making good progress, but our DistributedUpdateRequestHandler is having a bit of an identity crisis, so we thought we'd ask what other people's opinions are. The current situation is as follows

Load balancing within distributed search

after a pre-defined interval. Any thoughts? Upayavira --- Enterprise Search Consultant at Sourcesense UK, Making Sense of Open Source - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail

Re: Load balancing within distributed search

On Tue, 01 Mar 2011 13:18 +, Alex Cowell alxc...@gmail.com wrote: Hi Upayavira, I believe there is a basic implementation of load balancing for distributed search. The submit() method in the HttpCommComponent class within SearchHandler contains code which splits a pipe character

Re: Solrconfig in zookeeper

to make the changes take effect. Which is much the same as changing the file on disk and reloading the core in a non-SolrCloud setup. So not sure what the benefit might be that you're after. Upayavira On Thu, Sep 12, 2013, at 06:54 PM, Kranti Parisa wrote: Cool, thanks for the info. I am not using

Re: Help to unsubscribe

I have added a comment to that wiki page about not using HTML, as that can get caught in the spam filters. Upayavira On Mon, Apr 15, 2013, at 11:57 AM, Erick Erickson wrote: It's all automated, there's no manual intervention. You have to use the _exact_ e-mail you subscribed with. Here's

Re: Solr faceting vs. Lucene faceting

for hierarchical facets. It doesn't support depth prefixes at present, but that would be trivial to add. Upayavira On Thu, Dec 13, 2012, at 09:44 PM, Adrien Grand wrote: Hi Shai, Thanks for your answers! On Thu, Dec 13, 2012 at 5:05 PM, Shai Erera ser...@gmail.com wrote: the lucene module

Re: 4.1 release notes: please review

A lot of stuff in a short time! I know it is a Lucene feature, but the fact that Solr now compresses stored fields is significant to Solr users, and IMO should be included in the Solr release notes. Upayavira On Thu, Jan 17, 2013, at 07:40 AM, Shai Erera wrote: +1 Shai On Thu, Jan

Re: Suggestions about writing / extending QueryParsers

powerful, perhaps we can work together. Upayavira On Thu, Mar 6, 2014, at 11:23 AM, Tommaso Teofili wrote: Hi all, I'm thinking about writing/extending a QueryParser for MLT queries; I've never really looked into that code too much, while I'm doing that now, I'm wondering if anyone has

Re: Adding Collections to Admin UI

). If anyone has ideas about how to get Angular and Sammy to co-exist for a while, I'm all ears. Upayavira On Sat, Mar 1, 2014, at 06:26 PM, Stefan Matheis wrote: i think the rest was long enough (: sometimes i need an additional kick in the butt .. erm i mean, motivation! =] will give it another

Re: What's the purpose of scripts.conf in the release?

Scripts.conf was for configuring rsync based replication scripts, in the Solr 1.3 timeframe. It is long since redundant, and should be removed, as far as I can see. Upayavira On Sat, Dec 20, 2014, at 04:18 PM, Alexandre Rafalovitch wrote: I just found that DIH and techproducts examples ship

Re: jhighlight-1.0 contains LGPL-only files

You are right -both projects need to remove it, although it might be easier to work with Tika to fix that and then upgrade again. Upayavira On Fri, Mar 20, 2015, at 05:26 AM, Shai Erera wrote: Sorry for the spam, just wanted to note that this dependency was added by Steve in SOLR-6130

Re: jhighlight-1.0 contains LGPL-only files

We should remove it. It would not be a good thing to knowingly release incompatible code. Then, upgrade to the latest Tika when we can. Upayavira On Thu, Mar 26, 2015, at 04:41 PM, Steve Rowe wrote: +1 to remove. On Mar 26, 2015, at 4:43 AM, Shai Erera ser...@gmail.com wrote: Looks

Using RAT

license is acceptable? I suspect I'm missing something obvious. Many thanks! Upayavira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Using RAT

their copyright strings to that file, as you say in the right section, and then rerun 'ant rat-sources'. Thanks! Upayavira On Fri, Jan 30, 2015, at 02:37 AM, Robert Muir wrote: You are correct the main logic is in lucene/common-build, I dont see why you think that is confusing. Do you think

AngularJS Admin UI first pass complete

this solidified and tested. *Then* we can get on with things like a collections API page, an explains viewer, etc, etc, etc. Any suggestions/proposals as to what approach to take now? Thx, Upayavira - To unsubscribe, e-mail: dev-unsubscr

Re: AngularJS Admin UI first pass complete

via http://localhost:8983/solr/admin.html for as long as we decide to leave it there. Otherwise, your plan looks good. I'll have until 5.2 is feature-frozen to hunt for bugs/etc. Upayavira - To unsubscribe, e-mail: dev-unsubscr

Re: 5.2 release planning

and the release? Upayavira On Mon, May 18, 2015, at 06:47 PM, Anshum Gupta wrote: Hi, Seems like there's enough features + improvements + fixes and it'd be good to release a 5.2. To name just a few, there's the new faceting API, rule-based replica placement, Solr security framework, Solr streaming

Re: 5.2 release planning

advantage of AngularJS to make that clearer. Thus, any migration to AngularJS 2.0 should be simpler because of this work. The lines of Javascript has approximately halved in this new impl, which should make it all-round easier to maintain, in whichever way we choose to take it. Upayavira On Thu, May

Re: 5.2 release planning

Actually, a Monday/Tuesday deadline is no bad thing. I'd be happy for the admin UI to go out in 5.2 in the form it is now, although there might be a further tweak or two that could make it by then. Thanks! On Wed, May 20, 2015, at 06:11 PM, Anshum Gupta wrote: Hi Upayavira, Sorry

Re: Looks like I broke Solr 5.2.0 - do we need a 5.2.1?

If there was enough time, I'd like to fix the Cloud tab in the angular admin UI, which I discovered is broken after the release went out. Upayavira On Mon, Jun 8, 2015, at 06:52 PM, Uwe Schindler wrote: I am ready to commit the backport of the classloader deadlock to 5.2.1 branch Just

Re: Refactoring language detection in Solr and a minor bug in maxTotalChars param

Derek, Make your own JIRA, and link it to the one you mention below. Then this issue can potentially be tracked through to a commit if it goes that far. Thx! Upayavira On Tue, Jun 9, 2015, at 08:14 AM, Derek Wood wrote: I found a bug in the LangDetect implementation of language detection

Re: Looks like I broke Solr 5.2.0 - do we need a 5.2.1?

I've completed work on the cloud tab for the AngularJS UI. I'm now making final checks and preparing a patch that I hope someone will commit for me :-) Thanks! Upayavira On Tue, Jun 9, 2015, at 11:55 AM, Shalin Shekhar Mangar wrote: Go ahead Adrien. I'll cut the RC when you're done. On Tue

Re: Looks like I broke Solr 5.2.0 - do we need a 5.2.1?

I'd say, let's get this release out - I'm happy with either patch getting in. Then, let's see the flow of bug reports we get. That'll help us understand how stable (or otherwise) it is, and thus whether we should be shooting for 5.3 or 5.4. Upayavira On Tue, Jun 9, 2015, at 07:07 PM, Erick

Re: Looks like I broke Solr 5.2.0 - do we need a 5.2.1?

functioning. Upayavira On Tue, Jun 9, 2015, at 12:20 PM, Upayavira wrote: I've completed work on the cloud tab for the AngularJS UI. I'm now making final checks and preparing a patch that I hope someone will commit for me :-) Thanks! Upayavira On Tue, Jun 9, 2015, at 11:55 AM, Shalin Shekhar

Re: Welcome Upayavira as Lucene/Solr committer

your welcomes! Upayavira On Mon, Jun 22, 2015, at 05:14 PM, Shawn Heisey wrote: On 6/22/2015 1:02 PM, Steve Rowe wrote: I'm pleased to announce that Upayavira has accepted the PMC's invitation to become a committer. Congratulations and welcome to the group

Uploading configs via the Solr Admin UI

a risk also. With this feature, the UI would look in some preconfigured place for configurations and allow the user to upload some standard configs to Zookeeper. They would only be able to modify those configs via the schema API or via editing the files on disk. Risk or acceptable? Thx, Upayavira

Re: Moving to git?

Regarding history, if we switch to git, our history will remain in svn, even if the branches are deleted, the history and old revisions are still there. Upayavira On Sun 2015, at 10:48 PM, Mark Miller wrote: Having to agree on mechanics certainly is a downside of Git. There is only one good

[GitHub] lucene-solr pull request: SOLR-7223: Make tooltips consistent on a...

Github user upayavira commented on the pull request: https://github.com/apache/lucene-solr/pull/151#issuecomment-118139818 Hi Fengtan, please make this change to the solr/webapp/web/partials/query.html version - i.e. the angularJS one, then I will commit it. I'd be very pleased

Re: A post on the user's list made me wonder about a replace node utility/collections API call

that UI to allow a known bad node to be decommissioned easily, by looking at the cloud graph. Upayavira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Unit testing our UIs

On Thu, Aug 20, 2015, at 04:19 PM, Upayavira wrote: On Thu, Aug 20, 2015, at 03:06 PM, Jan Høydahl wrote: Hi We’re adding more and more UIs to Solr, and they have no unit tests (as far as I know). I could not find any discussions on this topic in the list archives, so thought

Re: Unit testing our UIs

it a different kind of test to the rest of our test suite. I'm game for working on it. If we can get a single test that works, I can start using it more widely across the UI. Upayavira - To unsubscribe, e-mail: dev-unsubscr

Re: 5.3 release

I need to update CHANGES.txt to account for a number of bug fixes to the angular UI. I'll add a single entry to account for them all. Upayavira On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote: I can work on setting up 5.3 release branch jobs on ASF Jenkins later today if Uwe doesn’t beat me

Re: 5.3 release

: E175013: Your commit message was left in a temporary file: svn: E175013:'/Users/upayavira/apache/solr-5.3/svn-commit.tmp' Any idea what's up? Anyone able to copy my SOLR-7666 line from either of the other CHANGES.txt to the one in lucene_solr_5_3? Thanks! Upayavira On Wed, Aug 5, 2015

Re: 5.3 release

Eeeks. Cause is obvious actually. The checkout I made of 5.3 was http, not https. Will make my commit now. Upayavira On Thu, Aug 6, 2015, at 12:29 PM, Upayavira wrote: Yes, it *should* work. Hopefully someone'll make the commit whilst I ask on infra@ to understand why this is breaking. Thx

Re: 5.3 release

:49:25 MESZ, schrieb Upayavira u...@odoko.co.uk: I just committed this to trunk and the lucene_5x branch. However, when I attempted to commit it to the lucene/dev/branches/lucene_solr_5_3 branch, I got this error: svn: E175013: Commit failed (details follow): svn: E175013: POST

Re: Welcome Christine Poerschke as Lucene/Solr committer

Congrats Christine - great to have another UK committer! Upayavira On Sun, Jul 26, 2015, at 07:12 PM, Anshum Gupta wrote: Congratulations and welcome Christine ! On Sun, Jul 26, 2015 at 6:43 AM, Alan Woodward a...@flax.co.uk wrote: Congratulations, and welcome! Alan Woodward

Re: FunctionQuery of FloatFieldSource (Lucene 5.0)

You should ask this question on the java-u...@lucene.apache.org mailing list - you will likely find more people there who can help you. Also note, I don't think that you can use doc values on triefields. Upayavira On Tue, Jul 14, 2015, at 08:06 AM, Peyman Faratin wrote: Hi I am having

Re: Refactor JapaneseTokenizer to take a dictionary as a parameter

). Follow the resource loading patterns that Lucene provides for maximum usability. Are the Kuromoji tools something new that you want to include into Solr? In which case, can their maintainer push them to Maven for Lucene to consume via Ant/Ivy? Upayavira On Mon, Jul 13, 2015, at 10:28 PM, Hayden

Re: Any clue why I'm being asked to moderate these messages from the build system?

Due to my (long ago) history with infra, I still have apmail privileges. I have subscribed bu...@elastic.co to the dev@lucene.apache.org allow list which should solve this. I could see that it wasn't there before I did so. Upayavira On Sun, Jul 12, 2015, at 07:06 PM, Michael McCandless wrote

Re: Welcome Mikhail Khludnev as Lucene/Solr committer

Welcome Mikhail! On Tue, Jul 21, 2015, at 02:47 PM, Han Jiang wrote: Welcome, Mikhail! On Tue, Jul 21, 2015 at 3:21 PM, Adrien Grand jpou...@gmail.com wrote: I'm pleased to announce that Mikhail Khludnev has accepted the PMC's invitation to become a committer. Mikhail, it's tradition

Re: [JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk1.9.0-ea-b85) - Build # 14644 - Failure!

Apologies, looking. I (clearly incorrectly) assumed that the issues would come with the change to LoadAdminUIServlet (which Mark did) not with the changes to web.xml. Pah. Seeing if I can run the test now. Upayavira On Sat, Oct 24, 2015, at 10:55 AM, Shalin Shekhar Mangar wrote: > This is

Re: Next release...

to carry it all the way. Upayavira On Mon, Nov 9, 2015, at 04:10 PM, Erick Erickson wrote: > Adrien: > > I can certainly wait for a while to commit CDCR to 5.4, there's no > huge need to rush 5.4 out the door, particularly not just to > accommodate me! After all, let's just say it

A 5.4 release?

Hi, I'm volunteering to make a 5.4 release. If there are no objections, I will create a release branch next Monday/Tuesday and a release candidate a week later. Anyone see any issues with this? Tasks that must be completed first? Upayavira

Re: Welcome Joel Bernstein to the PMC

Congrats Joel! On Fri, Nov 6, 2015, at 02:49 PM, Dennis Gove wrote: > Congrats Joel! > > On Fri, Nov 6, 2015 at 9:26 AM, Yonik Seeley > wrote: >> I'm pleased to announce that Joel as accepted the PMC's invitation >> to join. >> >> Welcome Joel! >> >> -Yonik >> >>

Re: Welcome Tomás Fernández Löbbe to the PMC

Congrats Tomás! On Fri, Nov 6, 2015, at 12:47 PM, Adrien Grand wrote: > Welcome Tomás!

Re: Is solrconfig.xml a potentially misleading filename?

Then make it accept two names, and start shipping examples with the new name. Old stuff works, new stuff makes sense. Upayavira On Thu, Jul 9, 2015, at 08:47 PM, Mark Miller wrote: It is the wrong name - mostly because it came from a single core solution. We could change it, but you have

Re: Any clue why I'm being asked to moderate these messages from the build system?

I'm sure that's something I could easily bring about, if it helps! On Sun, Jul 12, 2015, at 08:32 PM, Michael McCandless wrote: Thanks Upayavira! Now we wait for a build failure :) Mike McCandless http://blog.mikemccandless.com On Sun, Jul 12, 2015 at 3:21 PM, Upayavira u

Re: Permission to create cwiki page?

e to > create a page?  My username on the cwiki is "gchanan" if someone is > able to do that. > > Thanks, Greg Not that I have anything immediate to update, but could I be added also? My username should be just "upayavira". Thanks! Upayavira

Re: Could we merge solr logo into our logo?

This would be for the Lucene PMC to discuss. If they cannot decide, they can ask for help from the ASF trademarks list, or from the ASF VP Brand who's role is to help resolve these issues. Upayavira On Sat, Sep 5, 2015, at 02:51 PM, Shawn Heisey wrote: > On 9/5/2015 7:08 AM, Shi Jinghai wr

Re: Any clue why I'm being asked to moderate these messages from the build system?

bu...@elastic.co *is* on the allow list for dev, so dunno why it is in the moderation queue. If people are okay with it, I'll add myself as a list moderator and see if I can make anything of the moderation messages. Any objections? Upayavira On Wed, Sep 9, 2015, at 01:58 PM, Michael McCandless

Re: Any clue why I'm being asked to moderate these messages from the build system?

Thx Hoss! Seems it is already in hand (or understood at least) On Wed, Sep 9, 2015, at 03:38 PM, Chris Hostetter wrote: > > : Every individual email "From: bu...@elastic.co" is usually a completley > : distinct "Return-Path" header... > ... > : ...these addresses are what get compared

Re: License in Solr

it comes from the Apache Ant project. Provide links to the license file you are taking issue with, and perhaps we can help you understand it better. Upayavira

Re: Switching AngularUI to default

As shown on SOLR-7858, I've added links to the top right, but the idea of adding a distinctive grey tint to the whole page on the old UI is an intersting idea! Upayavira https://issues.apache.org/jira/browse/SOLR-7858 On Tue, Sep 15, 2015, at 06:54 PM, david.w.smi...@gmail.com wrote

Switching AngularUI to default

? Upayavira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: License in Solr

On Mon, Sep 14, 2015, at 11:28 PM, Upayavira wrote: > On Mon, Sep 14, 2015, at 10:41 PM, vetrik kumaran murugesan wrote: >> Hi Team, >> >> >> I see GPL and MIT license used in SOLR. So apache 2.0 holds good for >> all underlying licenses? >> >> e

Re: Couple of AngularJS issues in Solr 5.3

They are small details - I'm happy for you to re-open that ticket, and I'll sort them from there. Thanks for testing - really appreciated! Upayavira On Tue, Sep 15, 2015, at 09:18 PM, Alexandre Rafalovitch wrote: > I've hit a couple of issues in the new UI for Solr 5.3. > > I have po

Re: Couple of AngularJS issues in Solr 5.3

u route them as > appropriate. > > Regards, >Alex. > > Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: > http://www.solr-start.com/ > > > On 15 September 2015 at 16:24, Upayavira <u...@odoko.co.uk> wrote: > > They are small details - I'm h

Re: understanding SOLR 5.3.0

Please ask these questions on the solr-user list. Are you saying that you cannot find licenses for these libraries in the Solr codebase? If you can't, then it may be an omission. What are you trying to identify regarding these dependencies? Upayavira On Wed, Sep 16, 2015, at 08:19 PM, vetrik

Re: Sanity checking in Solr

Could it be added to the debug component? That seems like a natural place for it. It could, as you say, look for standard things that might make a query perform badly, and report them in a new element, or such. Upayavira On Tue, Sep 29, 2015, at 01:24 PM, Mikhail Khludnev wrote: > Hi Toke! W

Re: Solr search

far as I understand) Apache code, therefore Apache licensed. Why is their use a factor in your evaluation? Upayavira

Re: Solr search

There are some dependencies that are dual licensed, e.g GPL and MIT. we are accepting them under the terms of the MIT license NOT the GPL. Thus, you can be sure that the software included in Lucene or Solr will not include any code for which you must follow the obligations of the GPL. upayavira

Re: Lucene/Solr git mirror will soon turn off

Have we heard anything more from Infrastructure? It seems the thing to do right now is to get more of a conversation going with them to understand the issue at hand. Once the release is done, I'd be happy to try and get that conversation going faster than it is. Upayavira On Tue, Dec 8, 2015

Re: Lucene/Solr git mirror will soon turn off

uld be acceptable as a one-off task. So it seems we have two options: 1) Set up a VM and debug reading from SVN 2) Just migrate to Git and be done with it. Thoughts? Volunteers? Upayavira [1] https://svn.apache.org/repos/infra/infrastructure/trunk/projects/git/svn2gitupdate/ On Tue, Dec 8, 2015, at

Re: A 5.4 release?

I've just generated the first RC, but haven't posted it. How long do you expect it to take to get this bug resolved? It does seem worth doing. Upayavira On Thu, Dec 3, 2015, at 09:51 AM, Varun Thacker wrote: > Hi Everyone, > > I think we should try to fix SOLR-8363 before the RC? >

Re: A 5.4 release?

back, though I don't really see a reason unless we see broken builds due to > >> this commit. > >> > >> On Thu, Dec 3, 2015 at 3:07 PM, Adrien Grand <jpou...@gmail.com> wrote: > >>> > >>> SOLR-8330 is not critical so I don't think it should have

Re: A 5.4 release?

Thanks Varun. As a first time Release Manager, I'm currently working through the steps needed to build a release. I'll call a vote as soon as I have uploaded artifacts that are passing smoke tests. Upayavira On Fri, Dec 4, 2015, at 07:16 AM, Varun Thacker wrote: > Hi Upayavira, > &g

Re: [VOTE] Release Lucene/Solr 5.4.0-RC1

else: + raise RuntimeError("Unknown protocol: %s" % url.scheme) h.request('GET', url.path) r = h.getresponse() newLoc = r.getheader('location') Upayavira On Sun, Dec 6, 2015, at 06:26 PM, Noble Paul wrote: > Same here. > > On Sun, Dec 6, 2015 at 2:36 PM, Shalin S

Re: [VOTE] Release Lucene/Solr 5.4.0-RC1

/smokeTestRelease.py https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.4.0-RC1-rev1718046 Please, folks, use the above to run the smoke test for this release. Upayavira On Mon, Dec 7, 2015, at 04:00 AM, Shalin Shekhar Mangar wrote: > Hi Upayavira, > > The svn revision in the URL

Re: Lucene/Solr git mirror will soon turn off

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 survive in perpetuity, regardless of what we do now. Upayavira On Tue, Dec 8, 2015, at 09:24 PM, Doug Turnbull wrote: > It seems you'd want to preserve that hist

Re: Lucene/Solr git mirror will soon turn off

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 survive in perpetuity, regardless of what we do now. Upayavira On Tue, Dec 8, 2015, at 09:24 PM, Doug Turnbull wrote: > It seems you'd want to preserve that hist

Re: Lucene/Solr git mirror will soon turn off

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 survive in perpetuity, regardless of what we do now. Upayavira On Tue, Dec 8, 2015, at 09:24 PM, Doug Turnbull wrote: > It seems you'd want to preserve that hist

Re: Lucene/Solr git mirror will soon turn off

So you're trying to minimise the size of a git clone? I'd agree that Nutch etc aren't relevant. Upayavira On Tue, Dec 8, 2015, at 09:16 PM, Dawid Weiss wrote: > One more thing, perhaps of importance, the raw Lucene repo contains > all the history of projects that then turned top-level

Re: Lucene/Solr git mirror will soon turn off

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 survive in perpetuity, regardless of what we do now. Upayavira On Tue, Dec 8, 2015, at 09:24 PM, Doug Turnbull wrote: > It seems you'd want to preserve that hist

Re: Lucene/Solr git mirror will soon turn off

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 survive in perpetuity, regardless of what we do now. Upayavira On Tue, Dec 8, 2015, at 09:24 PM, Doug Turnbull wrote: > It seems you'd want to preserve that hist

Re: Lucene/Solr git mirror will soon turn off

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 survive in perpetuity, regardless of what we do now. Upayavira On Tue, Dec 8, 2015, at 09:24 PM, Doug Turnbull wrote: > It seems you'd want to preserve that hist

Re: Lucene/Solr git mirror will soon turn off

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 survive in perpetuity, regardless of what we do now. Upayavira On Tue, Dec 8, 2015, at 09:24 PM, Doug Turnbull wrote: > It seems you'd want to preserve that hist

  1   2   3   4   5   6   7   8   >