Re: Lucene/Solr git mirror will soon turn off

Even if we moved to git and did an svn rm on https://svn.apache.org/repos/asf/lucene/dev, the entire history of Lucene would remain in the ASF Subversion repository. Nothing we can do to prevent that!! Upayavira On Fri, Dec 4, 2015, at 09:26 PM, Gus Heck wrote: > If we moved to git wo

Re: Lucene/Solr git mirror will soon turn off

In the original report, the Infrastructure team said that throwing memory at it did not solve the problem. And I believe they threw *a lot* of memory at it. There may well be other options - just needs someone to dive in and look! Upayavira On Fri, Dec 4, 2015, at 11:10 PM, Alexandre

Re: Lucene/Solr git mirror will soon turn off

on the whole tree). Upayavira On Fri, Dec 4, 2015, at 10:16 PM, Mark Miller wrote: > Many old builds will also have problems even with a git checkout. If > you actually wanted to try and build them it would be much more sane > to work from the SVN history I'd hope we can retain.

[VOTE] Release Lucene/Solr 5.4.0-RC1

://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.4.0-RC1-rev178046 I will let this vote run until midnight (GMT) on Wednesday 9 December. Please cast your votes! (and let me know, politely :-) if I missed anything) Upayavira

Re: A 5.4 release?

On Fri, Dec 4, 2015, at 08:59 PM, Michael McCandless wrote: > On Fri, Dec 4, 2015 at 2:29 PM, Upayavira <u...@odoko.co.uk> wrote: > > > > On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote: > >> > >> On Fri, Dec 4, 2015 at 11:34

Re: A 5.4 release?

* Make sure you don't have another Solr instance running on port 8983 whilst running the smoke test (even a Vagrant instance sharing the port without Solr running) as the smoke test will fail. Yes, I'm planning to "soften" the release notes to make them less dense and more accessible.

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

Thx, I hope to create the first RC tomorrow. On Tue, Dec 1, 2015, at 06:36 PM, Noble Paul wrote: > I'm done with SOLR-8355 > > On Tue, Dec 1, 2015 at 4:24 PM, Noble Paul <noble.p...@gmail.com> wrote: > > hi Upayavira, > > sorry for the trouble. There is anothe

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

I've committed the smoke test patch to trunk, 5x and 5_4 branches. Upayavira On Mon, Dec 7, 2015, at 06:27 PM, Michael McCandless wrote: > +1 to release, smoke tester was happy for me (after applying the patch): > > SUCCESS! [0:30:52.332883] > > Mike McCan

Re: A 5.4 release?

On Fri, Dec 4, 2015, at 06:10 PM, Michael McCandless wrote: > On Fri, Dec 4, 2015 at 11:34 AM, Upayavira <u...@odoko.co.uk> wrote: > > > As a first time Release Manager > > Thanks Upayavira! > > But please, please, please take advantage of your ne

Re: 5.4 Release notes

Thanks! On Wed, Dec 9, 2015, at 09:39 PM, Adrien Grand wrote: > I will take care of it. > > Le mer. 9 déc. 2015 22:37, Upayavira <u...@odoko.co.uk> a écrit : >> I'm working on Solr release notes right now (it is hard work >> distilling >> the chang

5.4 Release notes

://wiki.apache.org/lucene-java/ReleaseNote54 Upayavira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 5.4 Release notes

time. Upayavira On Wed, Dec 9, 2015, at 10:44 PM, Adrien Grand wrote: > I updated the page to mention the most important changes, but > obviously this is subjective so if there is a change you care about > that is missing from the list, feel free to add it. > > Le mer. 9 dé

[RESULT] [VOTE] Release Lucene/Solr 5.4.0-RC1

This vote has passed, with 11 +1 votes. I shall continue with the remaining steps to publish the artifacts. Thank you all! Upayavira On Wed, Dec 9, 2015, at 07:44 PM, Yonik Seeley wrote: > +1 > > -Yonik > > On Sat, Dec 5, 2015 at 5:58 AM, Upayavira <u...@odoko.co.uk> w

Re: 5.3.2 bug fix release

Why don't people just upgrade to 5.4? Why do we need another release in the 5.3.x range? Upayavira On Wed, Dec 16, 2015, at 09:12 PM, Shawn Heisey wrote: > On 12/16/2015 1:08 PM, Anshum Gupta wrote: > > There are a bunch of important bug fixes that call for a 5.3.2 in my > &g

Re: [jira] [Updated] (LUCENE-6933) Create a (cleaned up) SVN history in git

One project can have multiple git repos. Apparently there's one or more with 100+ repos, so all is good there if pylucene wants to shift to git also. Upayavira On Wed, Dec 16, 2015, at 09:48 PM, Dawid Weiss wrote: > >> I personally don't care. Git has been a non-issue in PyLucene.

Re: Lucene/Solr git mirror will soon turn off

hat he can make for us. The more history we have the better, but only so far as it stays workable. Upayavira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 406 - Still Failing

Yes, hit some travel, then rhe weekend. Am working (slowly) through the rest of the steps. Upayavira On Sun, Dec 13, 2015, at 09:51 AM, Shalin Shekhar Mangar wrote: > Upayavira, you have to perform the post-release steps to add 5.4 index > to back-compat tests. Until you do that, the

Re: svn commit: r975484 - in /websites/production/lucene/content: ./ core/2_9_4/ core/3_0_3/ core/3_1_0/ core/3_2_0/ core/3_3_0/ core/3_4_0/ core/3_5_0/ core/3_6_0/ core/3_6_1/ core/3_6_2/ core/4_0_0/

Thanks. I did have a "close" button so you are probably right. On Mon, Dec 14, 2015, at 12:32 PM, Robert Muir wrote: > Upayavira, i closed + released. Maybe the problem was just that you > didnt "close" first? > > On Mon, Dec 14, 2015 at 7:23 AM, Upayavira &

Re: svn commit: r975484 - in /websites/production/lucene/content: ./ core/2_9_4/ core/3_0_3/ core/3_1_0/ core/3_2_0/ core/3_3_0/ core/3_4_0/ core/3_5_0/ core/3_6_0/ core/3_6_1/ core/3_6_2/ core/4_0_0/

Ahh, I need to click a "publish" button. They are already up in repository.apache.org.Yes, will do that shortly. Working through remaining steps now, and plan to make announcement today. Upayavira On Mon, Dec 14, 2015, at 11:12 AM, Uwe Schindler wrote: > Hi, > > I just ch

Re: svn commit: r975484 - in /websites/production/lucene/content: ./ core/2_9_4/ core/3_0_3/ core/3_1_0/ core/3_2_0/ core/3_3_0/ core/3_4_0/ core/3_5_0/ core/3_6_0/ core/3_6_1/ core/3_6_2/ core/4_0_0/

Uwe/others, I presume I need some permissions to be able to click the 'release' button in Nexus. Same for updating versions in JIRA. Can someone help there? Upayavira On Mon, Dec 14, 2015, at 11:39 AM, Upayavira wrote: > Ahh, I need to click a "publish" button. They a

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

Ahh, that's a Lucene one. I left the Solr one alone at 5.3.1, as it stated "this tutorial was prepared with 5.3.1" which seemed consistent within itself. Still need someone to look at the back compat issue in trunk. Upayavira On Tue, Dec 15, 2015, at 08:26 AM, Anshum Gupta wrote: >

[ANNOUNCE] Apache Lucene 5.4.0 released

14 December 2015, Apache Lucene™ 5.4.0 available The Lucene PMC is pleased to announce the release of Apache Lucene 5.4.0 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

Re: svn commit: r975484 - in /websites/production/lucene/content: ./ core/2_9_4/ core/3_0_3/ core/3_1_0/ core/3_2_0/ core/3_3_0/ core/3_4_0/ core/3_5_0/ core/3_6_0/ core/3_6_1/ core/3_6_2/ core/4_0_0/

Thx Uwe! Announcements coming shortly. Upayavira On Mon, Dec 14, 2015, at 01:20 PM, Uwe Schindler wrote: > Hi, > > ...and it is visible on Maven Central! Nexus "terms" are a bit confusing. > You need to create a stage repository (this is what ANT is doing), then > clos

[ANNOUNCE] Apache Solr 5.4.0 released

14 December 2015, Apache Solr™ 5.4 available Solr is the popular, blazing fast, open source NoSQL search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, dynamic clustering, database integration, rich document (e.g.,

trunk backwards-compatibility update problem

Running "python3 -u dev-tools/scripts/addBackcompatIndexes.py 5.4.0" on lucene_5x worked fine, however on trunk it gave the below error. I notice there is a lucene/core/src/java/org/apache/lucene/codecs/lucene54/Lucene54Codec.java in lucene_5x but not in trunk. Any ideas? Upayavir

Re: trunk backwards-compatibility update problem

I've committed the backcompat thing for trunk now, and as far as I'm concerned, the release is complete. Now to look at improving the clarity of the release guide. Many thanks! Upayavira On Tue, Dec 15, 2015, at 10:52 AM, Adrien Grand wrote: > Lucene54Codec was not defined in lucene/backw

Re: Breaking Java back-compat in Solr

Add in major components, such as SearchComponent, IpdateProcessor, etc, they need to be considered stable. On Tue, Jan 5, 2016, at 05:49 AM, Anshum Gupta wrote: > Thanks David, > > I agree with what you've suggested but the bigger question here again > is *which* files a we guarantee back-compat

Javascript testing in the Lucene/Solr build process

/praise/etc on the tickets, whether you are a Solr dev or not, as I want to try and do this in a way that suits us all. Upayavira [1] https://issues.apache.org/jira/browse/SOLR-8473 [2] https://issues.apache.org/jira/browse/SOLR-8474

Re: Null Commit Mails from Buildbot for website

an alternative way of accessing our site. I'll report back when I work something out. Upayavira On Sat, Dec 19, 2015, at 07:46 PM, Jack Krupansky wrote: > I had asked about these messages two and a half years ago and nobody > stepped forward to claim that they had any value and merely suggested >

Null Commit Mails from Buildbot for website

whether anything has changed or not. The buildbot job is three stages: svn up, build site, upload site. We could prevent these messages by making the second and third steps "dependent" upon the first. In which case, they won't occur if no files are changed. Any objections to doing this?

Re: Null Commit Mails from Buildbot for website

I did exactly as discussed with infra (commit to the buildbot config file) but nothing whatever changed. Am waiting on feedback[1] from infra as to how to tell buildbot to take notice of my commit. Upayavira [1] https://issues.apache.org/jira/browse/INFRA-11002[1] On Tue, Dec 29, 2015, at 11:36

Re: Null Commit Mails from Buildbot for website

you might see stuff go wrong. If I fail to get my updated script to work, I'll revert to the current config. Upayavira On Sat, Dec 19, 2015, at 09:55 PM, Upayavira wrote: > Okay. I'll dig further into how to make the commits list actually > useful by suppressing these messages. > >

Re: Should schema API allow deleting uniqueKey?

dd a "are you sure you want to delete your unique key?" warning to the UI, in 5.5. We could actually add a check to see if the field has content, and warn them before deleting a field with content. Those would both make lots of sense. Upayavira

Re: Fixing differences in solr/CHANGES.txt between 5x and trunk

This will undoubtedly help with making release notes, but please do track it in a ticket. Thanks! On Wed, Nov 25, 2015, at 03:25 PM, Shawn Heisey wrote: > I ran into some large differences in solr/CHANGES.txt between 5x and > trunk that made it difficult to patch 5x with a diff from trunk. I >

Re: A 5.4 release?

thx :-) On Thu, Nov 26, 2015, at 04:07 PM, Noble Paul wrote: > OK . So I need to commit my fixes there. I missed the branch creation > mail > > > On Thu, Nov 26, 2015 at 9:34 PM, Noble Paul <noble.p...@gmail.com> wrote: > > @Upayavira is there a branch created for 5.4

Re: A 5.4 release?

Thanks to Steve and Uwe, we now have both ASF and Policeman Jenkins pointing at the 5.4 branch. Upayavira On Thu, Nov 26, 2015, at 04:10 PM, Upayavira wrote: > thx :-) > > On Thu, Nov 26, 2015, at 04:07 PM, Noble Paul wrote: > > OK . So I need to commit my fixes there. I mi

Re: A 5.4 release?

I'm for one am okay with these going into 5.4. Upayavira On Wed, Nov 25, 2015, at 05:28 PM, Timothy Potter wrote: > I would like to put SOLR-7169 (also fixes 8267) and SOLR-8101 into > 5.4. I'll commit to trunk and 5x today ... let me know if there are > any objections to also includi

Re: A 5.4 release?

ention. Anyone have comments/observations here? I will create the branch shortly. Upayavira

5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

- and take any action to clear up these tickets asap. I expect to create the first RC this time next week. Thanks! Upayavira On Wed, Nov 25, 2015, at 02:05 PM, Upayavira wrote: > I shall shortly create the 5.4 release branch. From this moment, the > feature freeze starts. > > Looking thr

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

The patch seems innocuous enough. From the ticket though it isn't so clear to me what problem it solves. I'm open to the opinion of others. Upayavira On Mon, Nov 30, 2015, at 12:09 PM, Christine Poerschke (BLOOMBERG/ LONDON) wrote: > Any thoughts on getting the > https://issues.apache.or

Re: CDCR is is being developed for SolrCloud not for Master/Slave?

> > Can someone from dev community confirm that CDCR being developed is > for SolrCloud and not for Master/Slave architecture ? > > Thanks, Susheel You are correct - CDCR will be for allowing multiple SolrCloud farms to work together. Upayavira

Re: A 5.4 release?

concerns/objections. Upayavira On Tue, Nov 17, 2015, at 07:29 PM, Erick Erickson wrote: > The typical process is just what you're doing: Announce a date not too > far in the future and anyone who requires something for the 5.4 can > plead for more time. > > Works for me. > >

lucene-java wiki access

Can someone please grant me access to the lucene-java wiki? My username should be 'Upayavira'. Thanks! - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Lucene/Solr 6.0.0 release

I'd like to see some visible improvements to the Solr UI before then. Notably a "nodes" pane and a couple of others, so a timescale of "a few months" would be great. Upayavira On Fri, Jan 8, 2016, at 02:34 PM, Noble Paul wrote: > deprecating old API is not yet plan

Re: [DISCUSS] Lucene/Solr release management

dow? It seems to me that a lot of the confusion in the documentation is about deciding which branch of the docs you should be following at any one time, so the above could reduce that particular bit of complexity. Upayavira On Wed, 1 Jun 2016, at 07:11 PM, Steve Rowe wrote: > > > On May 31, 2016

Re: Moving Lucene / Solr from SVN to Git

Erick, I found this tutorial really helped me to get my head around git: http://pcottle.github.io/learnGitBranching/ You get to play making commits directly via that web UI, which shows you how commits happen, merges, etc. Upayavira On Sun, Jan 10, 2016, at 06:15 PM, Erick Erickson wrote

Re: How to implement BM25 in Lucene

Vitaly, Please ask this on either the java-user or the solr-user list, depending on your context. You will also need to provide more detail to your question, as you haven't said enough for anyone to say much, other than that BM25 is the default in Solr/Lucene 6.0+. Upayavira On Thu, 16 Jun 2016

Re: Zookeeper and Solr Clients

to a collection, I presume. Upayavira On Thu, Feb 25, 2016, at 04:45 PM, Scott Blum wrote: > You probably also want a child watch on live_nodes to monitor > connected nodes. > > On Thu, Feb 25, 2016 at 11:12 AM, Upayavira <u...@odoko.co.uk> wrote: >> I've recently had a patch merg

Re: Zookeeper and Solr Clients

Perfect. So, if when I want to find a node to talk to, I do: * locate state.json or clusterstate.json * identify a suitable node * confirm the node is life, and if not repeat from previous step Then I should be good. Upayavira On Fri, Feb 26, 2016, at 08:32 PM, Mark Miller wrote: > Ri

Re: Solr Schema API: Deprecation warning for GET operations?

I think you are supposed to be using the bulk api. I think that is what the new UI is using. On Thu, Feb 25, 2016, at 01:18 AM, Alexandre Rafalovitch wrote: > Hello, > > I am using Solr 5.5 and getting deprecation warning when hitting with > GET /collection/schema/fieldtypes/name > > I am

Re: Pushing code to master

in the JIRA comments, and on this mailing list. Hopefully your patch is interesting to a committer, who will pick it up and, perhaps after discussion, merge it into the main Apache Git repo for Lucene/Solr. Upayavira

Re: Zookeeper and Solr Clients

This is for making a ZK aware Pysolr client (i.e. Python equiv of SolrJ CloudSolrClient). It clearly needs to watch ZK to be able to update the list of hosts that make up a collection. We can't use the API, because we don't yet know where the Solr nodes are! Upayavira On Fri, Feb 26, 2016, at 09

Zookeeper and Solr Clients

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

Re: Clean up our dist folder?

Isnt dist just an svn repo, in which case you can just delete them. No need to ask. Especially if they are already in archive.apache.org, which they should be. Upayavira On Thu, Jan 21, 2016, at 08:58 AM, Jan Høydahl wrote: > Hi > > Over at https://www.apache.org/dist/lucene/ we curre

Re: [Possibly spoofed] Re: Lucene/Solr 6.0.0 Release Branch

I need to check whether the Solr UI messages need quietening down (removing the big red "experimental" banners). This is trivial work that should be done before the 6.0 release. Apologies for going silent here - I've been absorbing the impact of major life changes. Upayavira On T

Re: Lucene/Solr 6.0.0 Release Branch

Given its triviality, I have made this change. Solr peeps, please view the messages at the top of the two UIs and object if needs be. Upayavira On Thu, 10 Mar 2016, at 11:24 PM, Upayavira wrote: > I need to check whether the Solr UI messages need quietening down > (removing the b

Re: Lucene/Solr 5.5.1

I would like to include at least one, possibly two, trivial but significant fixes to the Solr Admin UI - SOLR-9032 is one of them, where the create alias feature fails without telling you. I'll try to get this committed by the end of the weekend. Upayavira On Fri, 29 Apr 2016, at 03:44 AM

Re: How can we use an "OR" search between two fields

Yes. That will just work. Didn't you try it? Upayavira On Wed, 27 Apr 2016, at 01:24 PM, Mushthaq Rumy wrote: > Hi, > I just want to know whether is it possible to use "OR" search between > two fields in Solr. > > Eg: field1:abc OR field2:abc > > Hopin

Re: Lucene/Solr 6.0.1

There are a collection of minor UI patches languishing in JIRA that it would be good to get out there too. I will endeavour to get them into Git before Friday. Upayavira On Fri, 13 May 2016, at 06:07 PM, Steve Rowe wrote: > Good idea, Adrien, but: I want to include SOLR-8992 in a 6.0.x rele

Re: Welcome Scott Blum as a Lucene/Solr committer!

Welcome Scott! On Tue, 19 Apr 2016, at 11:16 AM, David Smiley wrote: > Welcome Scott! > > On Tue, Apr 19, 2016 at 9:21 AM Shalin Shekhar Mangar > wrote: >> I'm pleased to announce that Scott Blum has accepted the Lucene PMC's >> invitation to become a committer. >> >>

Re: Is "solr.AnalyzerName" expansion supposed to work for Analyzers?

s, although I could only do the SolrResourceLoader and SolrAnalyzer > stuff. Not knowing how to get a list of acceptable components was the thing that stopped me adding that part of the schema API to the admin UI. And API to tell you which components exist would be extremely helpful. Upayav

Re: Shorter URLs to Solr ref-guide?

If you do want to register a new domain, I suggest getting the Infrastructure team to do it (an INFRA ticket?) and point it at a requisite location. It will likely be easier to do it that way, so that the ASF owns the domain name from the get go. Upayavira On Mon, 10 Jul 2017, at 09:56 AM, Jan

Re: SolrCloud "master mode" planned?

On Wed, 26 Apr 2017, at 10:06 PM, David Smiley wrote: > >> On Apr 26, 2017, at 4:35 PM, Upayavira <u...@odoko.co.uk> wrote: >> >> I have done a *lot* of automating this. Redoing it recently it was >> quite embarrassing to realise how much complexity there i

Re: SolrCloud "master mode" planned?

zookeeper, but without Solr. To really make it neat, we offer some way (a la Exhibitor) for multiple concurrently started ZK nodes to autodiscover each other, then getting our three ZK nodes up won't be quite so treacherous. Just a thought. Upayavira On Wed, 26 Apr 2017, at 03:58 PM, Mike Drob wrot

Re: query other solr collection from within a solr plugin

Go look in the source for the Join query parser. It does this. Upayavira On Thu, 26 Jul 2018, at 1:04 PM, Nicolas Franck wrote: > I'm writing a solr plugin in java that has to query another solr > collection to gather > information. What is the best way to do this? > > For now

Re: Next steps for Solr Admin UI - request for in-depth discussion

start building using something like Bootstrap or MaterialUI, and style it later - i.e. just following conventions rather than doing 'design'. Upayavira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Next steps for Solr Admin UI - request for in-depth discussion

sn't properly responsive, and it doesn't use idioms that people have come to expect from a UI (e.g. no hamburgers). In theory, I would support a rewrite of the visuals - it would make Solr seem more modern. However, I do not underestimate the amount of work involved. Upayavira --

Re: Next steps for Solr Admin UI - request for in-depth discussion

the UI would require a different set of skills, and would probably involve us bringing in a UI designer from somewhere to give us mocked-up components to start from. So really, the question as to how best to do it will likely depend on who is doing the work. Upayavira On Sun, 15 Apr 2018, at 6:13

Re: Wiki non-migration

manage access more clearly. Even though moin is capable of building sites, no-one at the ASF has used it that way at the moment. But as you say, if you only want something simple, then you don't need any complex web building system for it. Regards, Upayavira

Re: Wiki non-migration

On Fri, 2010-07-30 at 14:51 -0700, Marvin Humphrey wrote: On Fri, Jul 30, 2010 at 09:10:25PM +0100, Upayavira wrote: Have you created an AdminGroup page and locked that down with an ACL? I just tried to create an AdminGroup page with the following directive: #acl

Re: Lucy trademark issues

. Go for it. Upayavira

Re: Incubator PMC/Board report for August 2010 (gene...@incubator.apache.org)

directory to 'publish' when you've changed the source file in SVN. If you're not in the incubator group, as on infrastructure@ to be added. Upayavira On Thu, 05 Aug 2010 21:01 -0700, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Marvin, There is an action item under Mentors

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13010836#comment-13010836 ] Upayavira commented on SOLR-2399: - Now that there are 3.1 releases around, I'll try

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13010886#comment-13010886 ] Upayavira commented on SOLR-2399: - There's no need to test it with old releases

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011205#comment-13011205 ] Upayavira commented on SOLR-2399: - To give folks an incentive to upgrade? :-) I've found

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011208#comment-13011208 ] Upayavira commented on SOLR-2399: - Hah, I see you've fixed this already. But I deal with KB

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012502#comment-13012502 ] Upayavira commented on SOLR-2399: - It seems to me that the first task here is to reach

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012806#comment-13012806 ] Upayavira commented on SOLR-2399: - I've updated my github repo with an implementation

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013971#comment-13013971 ] Upayavira commented on SOLR-2399: - https://github.com/upayavira/solr-admin/commit

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022143#comment-13022143 ] Upayavira commented on SOLR-2399: - Patching/etc really aren't much of an issue

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026256#comment-13026256 ] Upayavira commented on SOLR-2399: - I've just seen the admin console fail on IE9

[jira] [Commented] (SOLR-2459) LogLevelSelection Servlet outputs plain HTML

[ https://issues.apache.org/jira/browse/SOLR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042046#comment-13042046 ] Upayavira commented on SOLR-2459: - So, slf4j is a facade, and it looks like Solr uses JDK

[jira] [Commented] (SOLR-2459) LogLevelSelection Servlet outputs plain HTML

[ https://issues.apache.org/jira/browse/SOLR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042078#comment-13042078 ] Upayavira commented on SOLR-2459: - Well, Solr doesn't distinguish between GET and POST

[jira] [Commented] (SOLR-2459) LogLevelSelection Servlet outputs plain HTML

[ https://issues.apache.org/jira/browse/SOLR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042129#comment-13042129 ] Upayavira commented on SOLR-2459: - As far as a Handler is concerned, it is just a list

[jira] [Commented] (SOLR-2459) LogLevelSelection Servlet outputs plain HTML

[ https://issues.apache.org/jira/browse/SOLR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042160#comment-13042160 ] Upayavira commented on SOLR-2459: - Ryan, I'd implement both approaches - the latter might

[jira] [Commented] (SOLR-2459) LogLevelSelection Servlet outputs plain HTML

[ https://issues.apache.org/jira/browse/SOLR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042189#comment-13042189 ] Upayavira commented on SOLR-2459: - Ryan - that could work, and it makes it clear

[jira] [Updated] (SOLR-2459) LogLevelSelection Servlet outputs plain HTML

[ https://issues.apache.org/jira/browse/SOLR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upayavira updated SOLR-2459: Attachment: sample-output.json sample-output.xml LogLevelHandler.patch

[jira] [Commented] (SOLR-2459) LogLevelSelection Servlet outputs plain HTML

[ https://issues.apache.org/jira/browse/SOLR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043061#comment-13043061 ] Upayavira commented on SOLR-2459: - Stefan - with set=, you can do multiples, so set

[jira] [Commented] (SOLR-792) Pivot (ie: Decision Tree) Faceting Component

[ https://issues.apache.org/jira/browse/SOLR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043095#comment-13043095 ] Upayavira commented on SOLR-792: Is this supposed to support distributed search? I just

[jira] [Created] (SOLR-2630) XsltUpdateRequestHandler

: Upayavira Priority: Minor Fix For: 4.0 Attachments: xslt-update-handler.patch An update request handler that can accept a tr param, allowing the indexing of any XML content that is passed to solr, so long as there is an XSLT stylesheet in solr/conf/xslt that can

[jira] [Updated] (SOLR-2630) XsltUpdateRequestHandler

[ https://issues.apache.org/jira/browse/SOLR-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upayavira updated SOLR-2630: Attachment: xslt-update-handler.patch Patch for XsltUpdateRequestHandler, along with a test case

[jira] [Commented] (SOLR-2630) XsltUpdateRequestHandler

[ https://issues.apache.org/jira/browse/SOLR-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058552#comment-13058552 ] Upayavira commented on SOLR-2630: - Great! I was sure I'd missed stuff. Happy to improve

[jira] [Commented] (SOLR-2630) XsltUpdateRequestHandler

[ https://issues.apache.org/jira/browse/SOLR-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058705#comment-13058705 ] Upayavira commented on SOLR-2630: - I considered the same thing, making

[jira] [Commented] (SOLR-2641) Auto Facet Selection component

[ https://issues.apache.org/jira/browse/SOLR-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061810#comment-13061810 ] Upayavira commented on SOLR-2641: - Same issue with pivot facets (SOLR-792). I'm going

[jira] [Created] (SOLR-4157) Migrate Browse functionality to the Admin UI

Upayavira created SOLR-4157: --- Summary: Migrate Browse functionality to the Admin UI Key: SOLR-4157 URL: https://issues.apache.org/jira/browse/SOLR-4157 Project: Solr Issue Type: Improvement

[jira] [Updated] (SOLR-4157) Migrate Browse functionality to the Admin UI

[ https://issues.apache.org/jira/browse/SOLR-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upayavira updated SOLR-4157: Attachment: SOLR-4157.patch Migrate Browse functionality to the Admin UI

[jira] [Created] (SOLR-4772) DateRoundingUpdateProcessorFactory

Upayavira created SOLR-4772: --- Summary: DateRoundingUpdateProcessorFactory Key: SOLR-4772 URL: https://issues.apache.org/jira/browse/SOLR-4772 Project: Solr Issue Type: Improvement

[jira] [Updated] (SOLR-4772) DateRoundingUpdateProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upayavira updated SOLR-4772: Attachment: DateRoundingUpdateProcessorFactory.zip DateRoundingUpdateProcessorFactory

[jira] [Commented] (SOLR-4772) DateRoundingUpdateProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643915#comment-13643915 ] Upayavira commented on SOLR-4772: - Thx Hoss, I'll upload another patch

[jira] [Updated] (SOLR-4772) DateRoundingUpdateProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upayavira updated SOLR-4772: Attachment: DateRoundingUpdateProcessorFactory.zip Updated patch that answers these points - particularly

<    1   2   3   4   5   6   7   8   >