Re: Please help test the new Angular JS Admin UI
Also, while you are at it, it'd be good to get SOLR-4777 in so the Admin UI is correct when users look at the SolrCloud graph post an operation that can leave the slice INACTIVE e.g. Shard split. On Wed, Jun 17, 2015 at 2:50 PM, Anshum Gupta ans...@anshumgupta.net wrote: This looks good overall and thanks for migrating it to something that more developers can contribute to. I started solr (trunk) in cloud mode using the bin scripts and opened the new admin UI. The section for 'cores' says 'No cores available. Go and create one'. Starting Solr 5.0, we officially stated in the change log and at other places that the only supported way to create a collection is through the Collections API. We should move along those lines and not stray with the new interface. I am not sure if the intention with this move is to first migrate everything as is and then redo the design but I'd strongly suggest that we do things the right way. On Sun, Jun 14, 2015 at 5:53 PM, Erick Erickson erickerick...@gmail.com wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- Anshum Gupta -- Anshum Gupta
Re: Please help test the new Angular JS Admin UI
This looks good overall and thanks for migrating it to something that more developers can contribute to. I started solr (trunk) in cloud mode using the bin scripts and opened the new admin UI. The section for 'cores' says 'No cores available. Go and create one'. Starting Solr 5.0, we officially stated in the change log and at other places that the only supported way to create a collection is through the Collections API. We should move along those lines and not stray with the new interface. I am not sure if the intention with this move is to first migrate everything as is and then redo the design but I'd strongly suggest that we do things the right way. On Sun, Jun 14, 2015 at 5:53 PM, Erick Erickson erickerick...@gmail.com wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- Anshum Gupta
Re: Please help test the new Angular JS Admin UI
Thanks Ramkumar, will dig into these next week.
Upayavira
On Wed, Jun 17, 2015, at 02:08 PM, Ramkumar R. Aiyengar wrote:
I started with an empty Solr instance and Firefox 38 on Linux. This is
the
trunk source..
There's a 'No cores available. Go and create one' button available in the
old and the new UI. In the old UI, clicking it goes to the core admin,
and
pops open the dialog for Add Core. The new UI only goes to the core
admin.
Also, when you then click on the Add Core, the dialog bleeds into the
sidebar.
I then started with a getting started config and a cloud of 2x2. Then
brought up admin UI on one of them, opened up one of the cores, and
clicked
on the Files tab -- that showed an exception..
{data:{responseHeader:{status:500,QTime:1},error:{msg:Path
must not end with /
character,trace:java.lang.IllegalArgumentException:
Path must not end with / character\n\tat
org.apache.zookeeper.common.PathUtils.validatePath(PathUtils.java:58)\n\tat
org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1024)\n\tat
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:319)\n\tat
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:316)\n\tat
org.apache.solr.common.cloud.ZkCmdExecutor.retryOperation(ZkCmdExecutor.java:61)\n\tat
org.apache.solr.common.cloud.SolrZkClient.exists(SolrZkClient.java:316)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.getAdminFileFromZooKeeper(ShowFileRequestHandler.java:324)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.showFromZooKeeper(ShowFileRequestHandler.java:148)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.handleRequestBody(ShowFileRequestHandler.java:135)\n\tat
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)\n\tat
org.apache.solr.core.SolrCore.execute(SolrCore.java:2057)\n\tat
org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:648)\n\tat
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:452)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)\n\tat
Moving to Plugins/Stats, and then Core, and selecting the first searcher
entry (e.g. for me, it is Searcher@3a7bd1[gettingstarted_shard1_replica1]
main), I see stats like:
- searcherName:Searcher@#8203;3a7bd1[gettingstarted_shard1_replica1]
main
- reader:
ExitableDirectoryReader(#8203;UninvertingDirectoryReader(#8203;))
Notice the unescaped characters there..
Re: Please help test the new Angular JS Admin UI
I started with an empty Solr instance and Firefox 38 on Linux. This is the
trunk source..
There's a 'No cores available. Go and create one' button available in the
old and the new UI. In the old UI, clicking it goes to the core admin, and
pops open the dialog for Add Core. The new UI only goes to the core admin.
Also, when you then click on the Add Core, the dialog bleeds into the
sidebar.
I then started with a getting started config and a cloud of 2x2. Then
brought up admin UI on one of them, opened up one of the cores, and clicked
on the Files tab -- that showed an exception..
{data:{responseHeader:{status:500,QTime:1},error:{msg:Path
must not end with / character,trace:java.lang.IllegalArgumentException:
Path must not end with / character\n\tat
org.apache.zookeeper.common.PathUtils.validatePath(PathUtils.java:58)\n\tat
org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1024)\n\tat
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:319)\n\tat
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:316)\n\tat
org.apache.solr.common.cloud.ZkCmdExecutor.retryOperation(ZkCmdExecutor.java:61)\n\tat
org.apache.solr.common.cloud.SolrZkClient.exists(SolrZkClient.java:316)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.getAdminFileFromZooKeeper(ShowFileRequestHandler.java:324)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.showFromZooKeeper(ShowFileRequestHandler.java:148)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.handleRequestBody(ShowFileRequestHandler.java:135)\n\tat
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)\n\tat
org.apache.solr.core.SolrCore.execute(SolrCore.java:2057)\n\tat
org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:648)\n\tat
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:452)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)\n\tat
Moving to Plugins/Stats, and then Core, and selecting the first searcher
entry (e.g. for me, it is Searcher@3a7bd1[gettingstarted_shard1_replica1]
main), I see stats like:
- searcherName:Searcher@#8203;3a7bd1[gettingstarted_shard1_replica1]
main
- reader:
ExitableDirectoryReader(#8203;UninvertingDirectoryReader(#8203;))
Notice the unescaped characters there..
RE: Please help test the new Angular JS Admin UI
i will check with Henry about this prolem again.
Best,
Soonho
From: Ramkumar R. Aiyengar [andyetitmo...@gmail.com]
Sent: Wednesday, June 17, 2015 5:08 PM
To: solr-user@lucene.apache.org
Subject: Re: Please help test the new Angular JS Admin UI
I started with an empty Solr instance and Firefox 38 on Linux. This is the
trunk source..
There's a 'No cores available. Go and create one' button available in the
old and the new UI. In the old UI, clicking it goes to the core admin, and
pops open the dialog for Add Core. The new UI only goes to the core admin.
Also, when you then click on the Add Core, the dialog bleeds into the
sidebar.
I then started with a getting started config and a cloud of 2x2. Then
brought up admin UI on one of them, opened up one of the cores, and clicked
on the Files tab -- that showed an exception..
{data:{responseHeader:{status:500,QTime:1},error:{msg:Path
must not end with / character,trace:java.lang.IllegalArgumentException:
Path must not end with / character\n\tat
org.apache.zookeeper.common.PathUtils.validatePath(PathUtils.java:58)\n\tat
org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1024)\n\tat
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:319)\n\tat
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:316)\n\tat
org.apache.solr.common.cloud.ZkCmdExecutor.retryOperation(ZkCmdExecutor.java:61)\n\tat
org.apache.solr.common.cloud.SolrZkClient.exists(SolrZkClient.java:316)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.getAdminFileFromZooKeeper(ShowFileRequestHandler.java:324)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.showFromZooKeeper(ShowFileRequestHandler.java:148)\n\tat
org.apache.solr.handler.admin.ShowFileRequestHandler.handleRequestBody(ShowFileRequestHandler.java:135)\n\tat
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)\n\tat
org.apache.solr.core.SolrCore.execute(SolrCore.java:2057)\n\tat
org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:648)\n\tat
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:452)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)\n\tat
Moving to Plugins/Stats, and then Core, and selecting the first searcher
entry (e.g. for me, it is Searcher@3a7bd1[gettingstarted_shard1_replica1]
main), I see stats like:
- searcherName:Searcher@#8203;3a7bd1[gettingstarted_shard1_replica1]
main
- reader:
ExitableDirectoryReader(#8203;UninvertingDirectoryReader(#8203;))
Notice the unescaped characters there..
Re: Please help test the new Angular JS Admin UI
The intention very much is to do a collections API pane. In fact, I've got a first pass made already that can create/delete collections, and show the details of a collection and its replicas. But I want to focus on getting the feature-for-feature replacement working first. If we don't do that, then we can't make it default, then we create a divided experience for want a working UI and want the cool new features. A decent collections API tab really won't take that long I don't think once we've given the new version a good shake-down. Upayavira On Wed, Jun 17, 2015, at 02:50 PM, Anshum Gupta wrote: This looks good overall and thanks for migrating it to something that more developers can contribute to. I started solr (trunk) in cloud mode using the bin scripts and opened the new admin UI. The section for 'cores' says 'No cores available. Go and create one'. Starting Solr 5.0, we officially stated in the change log and at other places that the only supported way to create a collection is through the Collections API. We should move along those lines and not stray with the new interface. I am not sure if the intention with this move is to first migrate everything as is and then redo the design but I'd strongly suggest that we do things the right way. On Sun, Jun 14, 2015 at 5:53 PM, Erick Erickson erickerick...@gmail.com wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- Anshum Gupta
Re: Please help test the new Angular JS Admin UI
This kind of feedback is _very_ valuable, many thanks to all. I may be the one committing this, but Upayavira is doing all the work so hats off to him. And it's time for anyone who likes UI work to step up and contribute ;). I'll be happy to commit changes. Just link any JIRAs (especially ones with patches attached) to SOLR-7666 and I'll see them. Or mention me in the new JIRA and I'll link them. Needless to say, UI work isn't something I'm very good at On Wed, Jun 17, 2015 at 5:55 PM, Upayavira u...@odoko.co.uk wrote: We can get things like this in. If you want, feel free to have a go. As much as I want to work on funky new stuff, I really need to focus on finishing stuff first. Upayavira On Wed, Jun 17, 2015, at 02:53 PM, Anshum Gupta wrote: Also, while you are at it, it'd be good to get SOLR-4777 in so the Admin UI is correct when users look at the SolrCloud graph post an operation that can leave the slice INACTIVE e.g. Shard split. On Wed, Jun 17, 2015 at 2:50 PM, Anshum Gupta ans...@anshumgupta.net wrote: This looks good overall and thanks for migrating it to something that more developers can contribute to. I started solr (trunk) in cloud mode using the bin scripts and opened the new admin UI. The section for 'cores' says 'No cores available. Go and create one'. Starting Solr 5.0, we officially stated in the change log and at other places that the only supported way to create a collection is through the Collections API. We should move along those lines and not stray with the new interface. I am not sure if the intention with this move is to first migrate everything as is and then redo the design but I'd strongly suggest that we do things the right way. On Sun, Jun 14, 2015 at 5:53 PM, Erick Erickson erickerick...@gmail.com wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- Anshum Gupta -- Anshum Gupta
Re: Please help test the new Angular JS Admin UI
We can get things like this in. If you want, feel free to have a go. As much as I want to work on funky new stuff, I really need to focus on finishing stuff first. Upayavira On Wed, Jun 17, 2015, at 02:53 PM, Anshum Gupta wrote: Also, while you are at it, it'd be good to get SOLR-4777 in so the Admin UI is correct when users look at the SolrCloud graph post an operation that can leave the slice INACTIVE e.g. Shard split. On Wed, Jun 17, 2015 at 2:50 PM, Anshum Gupta ans...@anshumgupta.net wrote: This looks good overall and thanks for migrating it to something that more developers can contribute to. I started solr (trunk) in cloud mode using the bin scripts and opened the new admin UI. The section for 'cores' says 'No cores available. Go and create one'. Starting Solr 5.0, we officially stated in the change log and at other places that the only supported way to create a collection is through the Collections API. We should move along those lines and not stray with the new interface. I am not sure if the intention with this move is to first migrate everything as is and then redo the design but I'd strongly suggest that we do things the right way. On Sun, Jun 14, 2015 at 5:53 PM, Erick Erickson erickerick...@gmail.com wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- Anshum Gupta -- Anshum Gupta
Re: Please help test the new Angular JS Admin UI
Slight correction, the url, if running locally, would be: Http://localhost:8983/solr/index.html The reason we need your help: there is so much to the admin UI that I cannot possibly have created the test setups to have tested it all. If there are aspects of the UI you rely upon, please try them out on 5.2.1 - any bugs we don't find could persist long enough to be annoying and inconvenient. Likewise, the sooner we can finish testing, the sooner we can do some fun things: * revamp the UI to be cloud friendly, e.g. Create and manage collections * update schema browser to allow you to update your schema * improve query tab to be able to prettily display your search results, e.g. - graphical explains viewer - parsed query debugger * and much more If enough people engage with testing, I will publish a zip file you can unpack on top of your 5.2.1 zip to clear up any bugs that have been found so far. Keep the bug reports coming!! Upayavira On Mon, Jun 15, 2015, at 01:53 AM, Erick Erickson wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick
Re: Please help test the new Angular JS Admin UI
The current UI was written before tools like AngularJS were widespread, and before decent separation of concerns was easy to achieve in Javascript. In a sense, your paraphrase of the justification was as you described - to make it easier for programmer types - partly by using a tool that is closer to their working model, but also this rewrite has more than halved the number of lines of code in the UI, which will make it vastly more maintainable and extensible. As a case in point, I've got a working patch that I'll release at some point soon that gives us a collections version of the core admin pane. I'd love to add HDFS support to the UI if there were APIs worth exposing (I haven't dug into HDFS support yet). Make sense? Upayavira On Mon, Jun 15, 2015, at 07:49 AM, Mark Miller wrote: I didn't really follow this issue - what was the motivation for the rewrite? Is it entirely under: new code should be quite a bit easier to work on for programmer types or are there other reasons as well? - Mark On Mon, Jun 15, 2015 at 10:40 AM Erick Erickson erickerick...@gmail.com wrote: Gaaah, that'll teach me to type URLs late on Sunday! Thanks Upayavira! You'll notice that 5.2.1 just had the release announcement posted, so let the fun begin! Erick On Mon, Jun 15, 2015 at 4:12 AM, Upayavira u...@odoko.co.uk wrote: Slight correction, the url, if running locally, would be: Http://localhost:8983/solr/index.html The reason we need your help: there is so much to the admin UI that I cannot possibly have created the test setups to have tested it all. If there are aspects of the UI you rely upon, please try them out on 5.2.1 - any bugs we don't find could persist long enough to be annoying and inconvenient. Likewise, the sooner we can finish testing, the sooner we can do some fun things: * revamp the UI to be cloud friendly, e.g. Create and manage collections * update schema browser to allow you to update your schema * improve query tab to be able to prettily display your search results, e.g. - graphical explains viewer - parsed query debugger * and much more If enough people engage with testing, I will publish a zip file you can unpack on top of your 5.2.1 zip to clear up any bugs that have been found so far. Keep the bug reports coming!! Upayavira On Mon, Jun 15, 2015, at 01:53 AM, Erick Erickson wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- - Mark about.me/markrmiller
Re: Please help test the new Angular JS Admin UI
Gaaah, that'll teach me to type URLs late on Sunday! Thanks Upayavira! You'll notice that 5.2.1 just had the release announcement posted, so let the fun begin! Erick On Mon, Jun 15, 2015 at 4:12 AM, Upayavira u...@odoko.co.uk wrote: Slight correction, the url, if running locally, would be: Http://localhost:8983/solr/index.html The reason we need your help: there is so much to the admin UI that I cannot possibly have created the test setups to have tested it all. If there are aspects of the UI you rely upon, please try them out on 5.2.1 - any bugs we don't find could persist long enough to be annoying and inconvenient. Likewise, the sooner we can finish testing, the sooner we can do some fun things: * revamp the UI to be cloud friendly, e.g. Create and manage collections * update schema browser to allow you to update your schema * improve query tab to be able to prettily display your search results, e.g. - graphical explains viewer - parsed query debugger * and much more If enough people engage with testing, I will publish a zip file you can unpack on top of your 5.2.1 zip to clear up any bugs that have been found so far. Keep the bug reports coming!! Upayavira On Mon, Jun 15, 2015, at 01:53 AM, Erick Erickson wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick
Re: Please help test the new Angular JS Admin UI
I didn't really follow this issue - what was the motivation for the rewrite? Is it entirely under: new code should be quite a bit easier to work on for programmer types or are there other reasons as well? - Mark On Mon, Jun 15, 2015 at 10:40 AM Erick Erickson erickerick...@gmail.com wrote: Gaaah, that'll teach me to type URLs late on Sunday! Thanks Upayavira! You'll notice that 5.2.1 just had the release announcement posted, so let the fun begin! Erick On Mon, Jun 15, 2015 at 4:12 AM, Upayavira u...@odoko.co.uk wrote: Slight correction, the url, if running locally, would be: Http://localhost:8983/solr/index.html The reason we need your help: there is so much to the admin UI that I cannot possibly have created the test setups to have tested it all. If there are aspects of the UI you rely upon, please try them out on 5.2.1 - any bugs we don't find could persist long enough to be annoying and inconvenient. Likewise, the sooner we can finish testing, the sooner we can do some fun things: * revamp the UI to be cloud friendly, e.g. Create and manage collections * update schema browser to allow you to update your schema * improve query tab to be able to prettily display your search results, e.g. - graphical explains viewer - parsed query debugger * and much more If enough people engage with testing, I will publish a zip file you can unpack on top of your 5.2.1 zip to clear up any bugs that have been found so far. Keep the bug reports coming!! Upayavira On Mon, Jun 15, 2015, at 01:53 AM, Erick Erickson wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- - Mark about.me/markrmiller
Re: Please help test the new Angular JS Admin UI
Sure, just curious. Wasn't sure if there was other motivations around what could be done, or the overall look and feel that could be achieved or anything beyond it's just easier for devs to work on and maintain (which is always good when it comes to JavaScript - I still wish it was all GWT :) ). - Mark On Mon, Jun 15, 2015 at 11:35 AM Upayavira u...@odoko.co.uk wrote: The current UI was written before tools like AngularJS were widespread, and before decent separation of concerns was easy to achieve in Javascript. In a sense, your paraphrase of the justification was as you described - to make it easier for programmer types - partly by using a tool that is closer to their working model, but also this rewrite has more than halved the number of lines of code in the UI, which will make it vastly more maintainable and extensible. As a case in point, I've got a working patch that I'll release at some point soon that gives us a collections version of the core admin pane. I'd love to add HDFS support to the UI if there were APIs worth exposing (I haven't dug into HDFS support yet). Make sense? Upayavira On Mon, Jun 15, 2015, at 07:49 AM, Mark Miller wrote: I didn't really follow this issue - what was the motivation for the rewrite? Is it entirely under: new code should be quite a bit easier to work on for programmer types or are there other reasons as well? - Mark On Mon, Jun 15, 2015 at 10:40 AM Erick Erickson erickerick...@gmail.com wrote: Gaaah, that'll teach me to type URLs late on Sunday! Thanks Upayavira! You'll notice that 5.2.1 just had the release announcement posted, so let the fun begin! Erick On Mon, Jun 15, 2015 at 4:12 AM, Upayavira u...@odoko.co.uk wrote: Slight correction, the url, if running locally, would be: Http://localhost:8983/solr/index.html The reason we need your help: there is so much to the admin UI that I cannot possibly have created the test setups to have tested it all. If there are aspects of the UI you rely upon, please try them out on 5.2.1 - any bugs we don't find could persist long enough to be annoying and inconvenient. Likewise, the sooner we can finish testing, the sooner we can do some fun things: * revamp the UI to be cloud friendly, e.g. Create and manage collections * update schema browser to allow you to update your schema * improve query tab to be able to prettily display your search results, e.g. - graphical explains viewer - parsed query debugger * and much more If enough people engage with testing, I will publish a zip file you can unpack on top of your 5.2.1 zip to clear up any bugs that have been found so far. Keep the bug reports coming!! Upayavira On Mon, Jun 15, 2015, at 01:53 AM, Erick Erickson wrote: And anyone who, you know, really likes working with UI code please help making it better! As of Solr 5.2, there is a new version of the Admin UI available, and several improvements are already in 5.2.1 (release imminent). The old admin UI is still the default, the new one is available at solr_ip:port/admin/index.html Currently, you will see very little difference at first glance; the goal for this release was to have as much of the current functionality as possible ported to establish the framework. Upayavira has done almost all of the work getting this in place, thanks for taking that initiative Upayavira! Anyway, the plan is several fold: Get as much testing on this as possible over the 5.2 time frame. Make the new Angular JS-based code the default in 5.3 Make improvements/bug fixes to the admin UI on the new code line, particularly SolrCloud functionality. Deprecate the current code and remove it eventually. The new code should be quite a bit easier to work on for programmer types, and there are Big Plans Afoot for making the admin UI more SolrCloud-friendly. Now that the framework is in place, it should be easier for anyone who wants to volunteer to contribute, please do! So please give it a whirl. I'm sure there will be things that crop up, and any help addressing them will be appreciated. There's already an umbrella JIRA for this work, see: https://issues.apache.org/jira/browse/SOLR-7666. Please link any new issues to this JIRA so we can keep track of it all as well as coordinate efforts. If all goes well, this JIRA can be used to see what's already been reported too. Note that things may be moving pretty quickly, so trunk and 5x will always be the most current. That said looking at 5.2.1 will be much appreciated. Erick -- - Mark about.me/markrmiller -- - Mark about.me/markrmiller
Re: Please help test the new Angular JS Admin UI
On 6/14/2015 6:53 PM, Erick Erickson wrote: And anyone who, you know, really likes working with UI code please help making it better! Did some quick testing with Solr 5.2.1, after starting it and adding a core based on the techproducts example. For the most part, it looks very good, and most of what I looked looked like it was complete. Because the core was empty, some of the pages didn't have anything to display. Now for the few problems I did notice, and one idea: On the dashboard, the memory/swap graphs had no numbers and were just solid bars. Under JVM, the Args entry was blank, but I'm pretty sure that when using bin\solr, there are a a whole bunch of arguments. I'm running this test on Windows 7 64-bit with 64-bit Oracle JDK8u45. The favicon was the standard jetty icon instead of the Solr icon. Then I went to the current admin UI, which switched it to the Solr icon. When I went back to the angular UI, the favicon was still showing the Solr icon. The Core Overview page says Last Modified: NaN years ago for a brand new empty core. The current UI has a blank field here. As I click around the UI, there is a spinning cursor above the S in Solr in the upper left corner of the UI. It is only half the cursor, though ... and it never stops spinning and never disappears. This is on Firefox 38.0.5. On Chrome 43.0.2357.124, it behaves similarly, except that the half-visible spinning cursor does disappear after the page is finished loading. Here's how it looks: https://www.dropbox.com/s/u5otx80hgk3rdu9/half-spinning-cursor-angular-ui.png?dl=0 I noticed that the URL includes /index.html# which is used in a way similar to /# in the current UI. It occurred to me that the inclusion of index.html makes it more obvious that you can't use that URL for a Solr client. Perhaps we could keep some text in the URL at that location even after it becomes default? Using admin (or some variation) instead of index.html seems like a good option. Thanks, Shawn
