[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507358#comment-15507358 ] Mikhail Khludnev commented on SOLR-6082: sure! SOLR-9539 > Umbrella JIRA for Admin UI and SolrCloud. > - > > Key: SOLR-6082 > URL: https://issues.apache.org/jira/browse/SOLR-6082 > Project: Solr > Issue Type: Improvement > Components: web gui >Affects Versions: 4.9, 6.0 >Reporter: Erick Erickson >Assignee: Erick Erickson > > It would be very helpful if the admin UI were more "cloud friendly". This is > an umbrella JIRA so we can collect sub-tasks as necessary. I think there > might be scattered JIRAs about this, let's link them in as we find them. > [~steffkes] - I've taken the liberty of assigning it to you since you > expressed some interest. Feel free to assign it back if you want... > Let's imagine that a user has a cluster with _no_ collections assigned and > start from there. > Here's a simple way to set this up. Basically you follow the reference guide > tutorial but _don't_ define a collection. > 1> completely delete the "collection1" directory from example > 2> cp -r example example2 > 3> in example, execute "java -DzkRun -jar start.jar" > 4> in example2, execute "java -Djetty.port=7574 -DzkHost=localhost:9983 -jar > start.jar" > Now the "cloud link" appears. If you expand the tree view, you see the two > live nodes. But, there's nothing in the graph view, no cores are selectable, > etc. > First problem (need to solve before any sub-jiras, so including it here): You > have to push a configuration directory to ZK. > [~thetapi] The _last_ time Stefan and I started allowing files to be written > to Solr from the UI it was...unfortunate. I'm assuming that there's something > similar here. That is, we shouldn't allow pushing the Solr config _to_ > ZooKeeper through the Admin UI, where they'd be distributed to all the solr > nodes. Is that true? If this is a security issue, we can keep pushing the > config dirs to ZK a manual step for now... > Once we determine how to get configurations up, we can work on the various > sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503407#comment-15503407 ] Upayavira commented on SOLR-6082: - [~mkhludnev] please create a separate ticket. The two UIs should be using the same back-end so should exhibit the same behaviour. > Umbrella JIRA for Admin UI and SolrCloud. > - > > Key: SOLR-6082 > URL: https://issues.apache.org/jira/browse/SOLR-6082 > Project: Solr > Issue Type: Improvement > Components: web gui >Affects Versions: 4.9, 6.0 >Reporter: Erick Erickson >Assignee: Erick Erickson > > It would be very helpful if the admin UI were more "cloud friendly". This is > an umbrella JIRA so we can collect sub-tasks as necessary. I think there > might be scattered JIRAs about this, let's link them in as we find them. > [~steffkes] - I've taken the liberty of assigning it to you since you > expressed some interest. Feel free to assign it back if you want... > Let's imagine that a user has a cluster with _no_ collections assigned and > start from there. > Here's a simple way to set this up. Basically you follow the reference guide > tutorial but _don't_ define a collection. > 1> completely delete the "collection1" directory from example > 2> cp -r example example2 > 3> in example, execute "java -DzkRun -jar start.jar" > 4> in example2, execute "java -Djetty.port=7574 -DzkHost=localhost:9983 -jar > start.jar" > Now the "cloud link" appears. If you expand the tree view, you see the two > live nodes. But, there's nothing in the graph view, no cores are selectable, > etc. > First problem (need to solve before any sub-jiras, so including it here): You > have to push a configuration directory to ZK. > [~thetapi] The _last_ time Stefan and I started allowing files to be written > to Solr from the UI it was...unfortunate. I'm assuming that there's something > similar here. That is, we shouldn't allow pushing the Solr config _to_ > ZooKeeper through the Admin UI, where they'd be distributed to all the solr > nodes. Is that true? If this is a security issue, we can keep pushing the > config dirs to ZK a manual step for now... > Once we determine how to get configurations up, we can work on the various > sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[
https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503324#comment-15503324
]
Mikhail Khludnev commented on SOLR-6082:
Just a note: if zookeeper is unavailable new ui freezes for a long time and
then respond with \{\{placehoders}}. Old UI is musch responsive in such
disaster.
> Umbrella JIRA for Admin UI and SolrCloud.
> -
>
> Key: SOLR-6082
> URL: https://issues.apache.org/jira/browse/SOLR-6082
> Project: Solr
> Issue Type: Improvement
> Components: web gui
>Affects Versions: 4.9, 6.0
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>
> It would be very helpful if the admin UI were more "cloud friendly". This is
> an umbrella JIRA so we can collect sub-tasks as necessary. I think there
> might be scattered JIRAs about this, let's link them in as we find them.
> [~steffkes] - I've taken the liberty of assigning it to you since you
> expressed some interest. Feel free to assign it back if you want...
> Let's imagine that a user has a cluster with _no_ collections assigned and
> start from there.
> Here's a simple way to set this up. Basically you follow the reference guide
> tutorial but _don't_ define a collection.
> 1> completely delete the "collection1" directory from example
> 2> cp -r example example2
> 3> in example, execute "java -DzkRun -jar start.jar"
> 4> in example2, execute "java -Djetty.port=7574 -DzkHost=localhost:9983 -jar
> start.jar"
> Now the "cloud link" appears. If you expand the tree view, you see the two
> live nodes. But, there's nothing in the graph view, no cores are selectable,
> etc.
> First problem (need to solve before any sub-jiras, so including it here): You
> have to push a configuration directory to ZK.
> [~thetapi] The _last_ time Stefan and I started allowing files to be written
> to Solr from the UI it was...unfortunate. I'm assuming that there's something
> similar here. That is, we shouldn't allow pushing the Solr config _to_
> ZooKeeper through the Admin UI, where they'd be distributed to all the solr
> nodes. Is that true? If this is a security issue, we can keep pushing the
> config dirs to ZK a manual step for now...
> Once we determine how to get configurations up, we can work on the various
> sub-jiras.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488451#comment-15488451 ] Erick Erickson commented on SOLR-6082: -- Upayavira was driving this bus, so if he closed it that's "the final word" ;) > Umbrella JIRA for Admin UI and SolrCloud. > - > > Key: SOLR-6082 > URL: https://issues.apache.org/jira/browse/SOLR-6082 > Project: Solr > Issue Type: Improvement > Components: web gui >Affects Versions: 4.9, 6.0 >Reporter: Erick Erickson >Assignee: Erick Erickson > > It would be very helpful if the admin UI were more "cloud friendly". This is > an umbrella JIRA so we can collect sub-tasks as necessary. I think there > might be scattered JIRAs about this, let's link them in as we find them. > [~steffkes] - I've taken the liberty of assigning it to you since you > expressed some interest. Feel free to assign it back if you want... > Let's imagine that a user has a cluster with _no_ collections assigned and > start from there. > Here's a simple way to set this up. Basically you follow the reference guide > tutorial but _don't_ define a collection. > 1> completely delete the "collection1" directory from example > 2> cp -r example example2 > 3> in example, execute "java -DzkRun -jar start.jar" > 4> in example2, execute "java -Djetty.port=7574 -DzkHost=localhost:9983 -jar > start.jar" > Now the "cloud link" appears. If you expand the tree view, you see the two > live nodes. But, there's nothing in the graph view, no cores are selectable, > etc. > First problem (need to solve before any sub-jiras, so including it here): You > have to push a configuration directory to ZK. > [~thetapi] The _last_ time Stefan and I started allowing files to be written > to Solr from the UI it was...unfortunate. I'm assuming that there's something > similar here. That is, we shouldn't allow pushing the Solr config _to_ > ZooKeeper through the Admin UI, where they'd be distributed to all the solr > nodes. Is that true? If this is a security issue, we can keep pushing the > config dirs to ZK a manual step for now... > Once we determine how to get configurations up, we can work on the various > sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488043#comment-15488043 ] Cassandra Targett commented on SOLR-6082: - [~erickerickson], You said in December you were waiting to finish SOLR-6082 before resolving this one, but this one is SOLR-6082, so I wonder if you really meant SOLR-6083 (which is relatively recently closed)? The only other issue open that's linked to this one is SOLR-5128, but that's a rather large issue on its own. One could keep an "umbrella" issue open forever, but it feels to me like this one has served its purpose for now. WDYT? > Umbrella JIRA for Admin UI and SolrCloud. > - > > Key: SOLR-6082 > URL: https://issues.apache.org/jira/browse/SOLR-6082 > Project: Solr > Issue Type: Improvement > Components: web gui >Affects Versions: 4.9, 6.0 >Reporter: Erick Erickson >Assignee: Erick Erickson > > It would be very helpful if the admin UI were more "cloud friendly". This is > an umbrella JIRA so we can collect sub-tasks as necessary. I think there > might be scattered JIRAs about this, let's link them in as we find them. > [~steffkes] - I've taken the liberty of assigning it to you since you > expressed some interest. Feel free to assign it back if you want... > Let's imagine that a user has a cluster with _no_ collections assigned and > start from there. > Here's a simple way to set this up. Basically you follow the reference guide > tutorial but _don't_ define a collection. > 1> completely delete the "collection1" directory from example > 2> cp -r example example2 > 3> in example, execute "java -DzkRun -jar start.jar" > 4> in example2, execute "java -Djetty.port=7574 -DzkHost=localhost:9983 -jar > start.jar" > Now the "cloud link" appears. If you expand the tree view, you see the two > live nodes. But, there's nothing in the graph view, no cores are selectable, > etc. > First problem (need to solve before any sub-jiras, so including it here): You > have to push a configuration directory to ZK. > [~thetapi] The _last_ time Stefan and I started allowing files to be written > to Solr from the UI it was...unfortunate. I'm assuming that there's something > similar here. That is, we shouldn't allow pushing the Solr config _to_ > ZooKeeper through the Admin UI, where they'd be distributed to all the solr > nodes. Is that true? If this is a security issue, we can keep pushing the > config dirs to ZK a manual step for now... > Once we determine how to get configurations up, we can work on the various > sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15055064#comment-15055064 ] Erick Erickson commented on SOLR-6082: -- SOLR-6082 is the only remaining JIRA lined to this one, and I'm working on closing that. Once that's resolved, I'll close this one. Meanwhile, I think this is pretty obsolete with the Angular JS work that [~upayavira] & co. have done. I think any additional work on the admin UI will make its way into new tickets. [~shalinmangar] Don't really mean to steal this, if you want it back just grab it.. > Umbrella JIRA for Admin UI and SolrCloud. > - > > Key: SOLR-6082 > URL: https://issues.apache.org/jira/browse/SOLR-6082 > Project: Solr > Issue Type: Improvement > Components: web gui >Affects Versions: 4.9, Trunk >Reporter: Erick Erickson >Assignee: Erick Erickson > > It would be very helpful if the admin UI were more "cloud friendly". This is > an umbrella JIRA so we can collect sub-tasks as necessary. I think there > might be scattered JIRAs about this, let's link them in as we find them. > [~steffkes] - I've taken the liberty of assigning it to you since you > expressed some interest. Feel free to assign it back if you want... > Let's imagine that a user has a cluster with _no_ collections assigned and > start from there. > Here's a simple way to set this up. Basically you follow the reference guide > tutorial but _don't_ define a collection. > 1> completely delete the "collection1" directory from example > 2> cp -r example example2 > 3> in example, execute "java -DzkRun -jar start.jar" > 4> in example2, execute "java -Djetty.port=7574 -DzkHost=localhost:9983 -jar > start.jar" > Now the "cloud link" appears. If you expand the tree view, you see the two > live nodes. But, there's nothing in the graph view, no cores are selectable, > etc. > First problem (need to solve before any sub-jiras, so including it here): You > have to push a configuration directory to ZK. > [~thetapi] The _last_ time Stefan and I started allowing files to be written > to Solr from the UI it was...unfortunate. I'm assuming that there's something > similar here. That is, we shouldn't allow pushing the Solr config _to_ > ZooKeeper through the Admin UI, where they'd be distributed to all the solr > nodes. Is that true? If this is a security issue, we can keep pushing the > config dirs to ZK a manual step for now... > Once we determine how to get configurations up, we can work on the various > sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15055141#comment-15055141 ] Shalin Shekhar Mangar commented on SOLR-6082: - It's all yours, Erick. > Umbrella JIRA for Admin UI and SolrCloud. > - > > Key: SOLR-6082 > URL: https://issues.apache.org/jira/browse/SOLR-6082 > Project: Solr > Issue Type: Improvement > Components: web gui >Affects Versions: 4.9, Trunk >Reporter: Erick Erickson >Assignee: Erick Erickson > > It would be very helpful if the admin UI were more "cloud friendly". This is > an umbrella JIRA so we can collect sub-tasks as necessary. I think there > might be scattered JIRAs about this, let's link them in as we find them. > [~steffkes] - I've taken the liberty of assigning it to you since you > expressed some interest. Feel free to assign it back if you want... > Let's imagine that a user has a cluster with _no_ collections assigned and > start from there. > Here's a simple way to set this up. Basically you follow the reference guide > tutorial but _don't_ define a collection. > 1> completely delete the "collection1" directory from example > 2> cp -r example example2 > 3> in example, execute "java -DzkRun -jar start.jar" > 4> in example2, execute "java -Djetty.port=7574 -DzkHost=localhost:9983 -jar > start.jar" > Now the "cloud link" appears. If you expand the tree view, you see the two > live nodes. But, there's nothing in the graph view, no cores are selectable, > etc. > First problem (need to solve before any sub-jiras, so including it here): You > have to push a configuration directory to ZK. > [~thetapi] The _last_ time Stefan and I started allowing files to be written > to Solr from the UI it was...unfortunate. I'm assuming that there's something > similar here. That is, we shouldn't allow pushing the Solr config _to_ > ZooKeeper through the Admin UI, where they'd be distributed to all the solr > nodes. Is that true? If this is a security issue, we can keep pushing the > config dirs to ZK a manual step for now... > Once we determine how to get configurations up, we can work on the various > sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556820#comment-14556820 ] Upayavira commented on SOLR-6082: - I've started thinking about a collections API panel. Here's what I have in mind: A list of collections down the left hand side. A list of nodes down the right hand side. Each of these lists is independently scrollable. At the top of the collections box is a big (+) symbol, clicking on which allows us to create a new collection. Click on a collection, it will expand to show its shards. Click on a node, it will expand to show the shards/collections it hosts. You can drag a shard from a collection over onto a node. You can drag a shard from one node to another (visually, it will leave the shard behind which will make it clear that you are cloning). There's more to it than this, but this is the basic idea. This should all be pretty straightforward. Ironically, the one thing I've got to work out now is how to work with the CSS, as, to-date I've always had the old UI to base my work upon :-) I am deliberately not addressing configurations as a part of the above. I am working on the assumption that relevant configs are already in place. Umbrella JIRA for Admin UI and SolrCloud. - Key: SOLR-6082 URL: https://issues.apache.org/jira/browse/SOLR-6082 Project: Solr Issue Type: Improvement Components: web gui Affects Versions: 4.9, Trunk Reporter: Erick Erickson Assignee: Shalin Shekhar Mangar It would be very helpful if the admin UI were more cloud friendly. This is an umbrella JIRA so we can collect sub-tasks as necessary. I think there might be scattered JIRAs about this, let's link them in as we find them. [~steffkes] - I've taken the liberty of assigning it to you since you expressed some interest. Feel free to assign it back if you want... Let's imagine that a user has a cluster with _no_ collections assigned and start from there. Here's a simple way to set this up. Basically you follow the reference guide tutorial but _don't_ define a collection. 1 completely delete the collection1 directory from example 2 cp -r example example2 3 in example, execute java -DzkRun -jar start.jar 4 in example2, execute java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar Now the cloud link appears. If you expand the tree view, you see the two live nodes. But, there's nothing in the graph view, no cores are selectable, etc. First problem (need to solve before any sub-jiras, so including it here): You have to push a configuration directory to ZK. [~thetapi] The _last_ time Stefan and I started allowing files to be written to Solr from the UI it was...unfortunate. I'm assuming that there's something similar here. That is, we shouldn't allow pushing the Solr config _to_ ZooKeeper through the Admin UI, where they'd be distributed to all the solr nodes. Is that true? If this is a security issue, we can keep pushing the config dirs to ZK a manual step for now... Once we determine how to get configurations up, we can work on the various sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14259693#comment-14259693 ] Erick Erickson commented on SOLR-6082: -- [~shalinmangar] Don't know whether this is getting much of your attention, but see SOLR-5507. Upayavira is working on moving the admin UI to AngularJS, coordinating the two efforts seems like A Good Thing An open question is how to prioritize this and the work on SOLR-5507. How/when should priority be given to reproducing the current admin UI which looks at things largely on the basis of individual nodes with SolrCloud bolted on as opposed to adding SolrCloud-centric features to the admin UI? Recording here for posterity, as always the people doing the work are the ones who get to choose. Umbrella JIRA for Admin UI and SolrCloud. - Key: SOLR-6082 URL: https://issues.apache.org/jira/browse/SOLR-6082 Project: Solr Issue Type: Improvement Components: web gui Affects Versions: 4.9, Trunk Reporter: Erick Erickson Assignee: Shalin Shekhar Mangar It would be very helpful if the admin UI were more cloud friendly. This is an umbrella JIRA so we can collect sub-tasks as necessary. I think there might be scattered JIRAs about this, let's link them in as we find them. [~steffkes] - I've taken the liberty of assigning it to you since you expressed some interest. Feel free to assign it back if you want... Let's imagine that a user has a cluster with _no_ collections assigned and start from there. Here's a simple way to set this up. Basically you follow the reference guide tutorial but _don't_ define a collection. 1 completely delete the collection1 directory from example 2 cp -r example example2 3 in example, execute java -DzkRun -jar start.jar 4 in example2, execute java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar Now the cloud link appears. If you expand the tree view, you see the two live nodes. But, there's nothing in the graph view, no cores are selectable, etc. First problem (need to solve before any sub-jiras, so including it here): You have to push a configuration directory to ZK. [~thetapi] The _last_ time Stefan and I started allowing files to be written to Solr from the UI it was...unfortunate. I'm assuming that there's something similar here. That is, we shouldn't allow pushing the Solr config _to_ ZooKeeper through the Admin UI, where they'd be distributed to all the solr nodes. Is that true? If this is a security issue, we can keep pushing the config dirs to ZK a manual step for now... Once we determine how to get configurations up, we can work on the various sub-jiras. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6082) Umbrella JIRA for Admin UI and SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084985#comment-14084985 ] Shalin Shekhar Mangar commented on SOLR-6082: - I am working on this. Umbrella JIRA for Admin UI and SolrCloud. - Key: SOLR-6082 URL: https://issues.apache.org/jira/browse/SOLR-6082 Project: Solr Issue Type: Improvement Components: web gui Affects Versions: 4.9, 5.0 Reporter: Erick Erickson Assignee: Shalin Shekhar Mangar It would be very helpful if the admin UI were more cloud friendly. This is an umbrella JIRA so we can collect sub-tasks as necessary. I think there might be scattered JIRAs about this, let's link them in as we find them. [~steffkes] - I've taken the liberty of assigning it to you since you expressed some interest. Feel free to assign it back if you want... Let's imagine that a user has a cluster with _no_ collections assigned and start from there. Here's a simple way to set this up. Basically you follow the reference guide tutorial but _don't_ define a collection. 1 completely delete the collection1 directory from example 2 cp -r example example2 3 in example, execute java -DzkRun -jar start.jar 4 in example2, execute java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar Now the cloud link appears. If you expand the tree view, you see the two live nodes. But, there's nothing in the graph view, no cores are selectable, etc. First problem (need to solve before any sub-jiras, so including it here): You have to push a configuration directory to ZK. [~thetapi] The _last_ time Stefan and I started allowing files to be written to Solr from the UI it was...unfortunate. I'm assuming that there's something similar here. That is, we shouldn't allow pushing the Solr config _to_ ZooKeeper through the Admin UI, where they'd be distributed to all the solr nodes. Is that true? If this is a security issue, we can keep pushing the config dirs to ZK a manual step for now... Once we determine how to get configurations up, we can work on the various sub-jiras. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
