[jira] [Resolved] (SOLR-11719) Committing to restored collection does nothing
[ https://issues.apache.org/jira/browse/SOLR-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Lavrov resolved SOLR-11719. -- Resolution: Duplicate > Committing to restored collection does nothing > -- > > Key: SOLR-11719 > URL: https://issues.apache.org/jira/browse/SOLR-11719 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.1 >Reporter: Vitaly Lavrov >Priority: Major > Attachments: script.sh > > > Scenario that was reproduced many times: > 1. Restore collection > 2. Send updates > 3. Send commit > Commit request returns instantly and the index stays intact. After collection > reload or cluster reboot updates are visible and commits will work. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Resolved] (SOLR-11720) Backup restore command completes before index is ready
[ https://issues.apache.org/jira/browse/SOLR-11720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Lavrov resolved SOLR-11720. -- Resolution: Duplicate > Backup restore command completes before index is ready > -- > > Key: SOLR-11720 > URL: https://issues.apache.org/jira/browse/SOLR-11720 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.1 >Reporter: Vitaly Lavrov >Priority: Major > > Scenario: > 1. Run backup restore as async command > 2. Check command status until it has 'completed' status > 3. Query collection immediately for total number of documents > The problem is the query will return incorrect number. The query will return > correct number eventually if one keeps querying. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11719) Committing to restored collection does nothing
[ https://issues.apache.org/jira/browse/SOLR-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282110#comment-16282110 ] Vitaly Lavrov commented on SOLR-11719: -- Any comment on this issue? > Committing to restored collection does nothing > -- > > Key: SOLR-11719 > URL: https://issues.apache.org/jira/browse/SOLR-11719 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.1 >Reporter: Vitaly Lavrov > Attachments: script.sh > > > Scenario that was reproduced many times: > 1. Restore collection > 2. Send updates > 3. Send commit > Commit request returns instantly and the index stays intact. After collection > reload or cluster reboot updates are visible and commits will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11719) Committing to restored collection does nothing
[ https://issues.apache.org/jira/browse/SOLR-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Lavrov updated SOLR-11719: - Attachment: script.sh Here is the script to reproduce the issue. I ran it against SolrCloud which is started with `bin/solr -e cloud -noprompt`. > Committing to restored collection does nothing > -- > > Key: SOLR-11719 > URL: https://issues.apache.org/jira/browse/SOLR-11719 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.1 >Reporter: Vitaly Lavrov > Attachments: script.sh > > > Scenario that was reproduced many times: > 1. Restore collection > 2. Send updates > 3. Send commit > Commit request returns instantly and the index stays intact. After collection > reload or cluster reboot updates are visible and commits will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-11719) Committing to restored collection does nothing
[ https://issues.apache.org/jira/browse/SOLR-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278469#comment-16278469 ] Vitaly Lavrov edited comment on SOLR-11719 at 12/5/17 12:28 PM: Here is the [^script.sh] to reproduce the issue. I ran it against SolrCloud which is started with `bin/solr -e cloud -noprompt`. was (Author: lavrovvv): Here is the script to reproduce the issue. I ran it against SolrCloud which is started with `bin/solr -e cloud -noprompt`. > Committing to restored collection does nothing > -- > > Key: SOLR-11719 > URL: https://issues.apache.org/jira/browse/SOLR-11719 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.1 >Reporter: Vitaly Lavrov > Attachments: script.sh > > > Scenario that was reproduced many times: > 1. Restore collection > 2. Send updates > 3. Send commit > Commit request returns instantly and the index stays intact. After collection > reload or cluster reboot updates are visible and commits will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11720) Backup restore command completes before index is ready
[ https://issues.apache.org/jira/browse/SOLR-11720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277714#comment-16277714 ] Vitaly Lavrov commented on SOLR-11720: -- Backup restore command is sent as http://solr.host.com:8983/solr/admin/collections?action=RESTORE=offers=/backup=offers=101=json The target collection 'offers' gets deleted right before restore command is sent (so does configSet). 1. No commits are sent, only searches 2. Old searcher does not exist because collection is being restored 3. Timeline after restore command has shown 'completed' status: 10 seconds after 448435467 documents 20 seconds after 454947732 documents 30 seconds after 460556612 documents 40 seconds after 466567718 documents 50 seconds after 472862588 documents 60 seconds after 472862588 documents 70 seconds after 479985875 documents (final number, the correct one) Number of documents are measured with http://solr.host.com:8983/api/c/offers/query?q=*:* 4. Searches go directly to solr cloud > Backup restore command completes before index is ready > -- > > Key: SOLR-11720 > URL: https://issues.apache.org/jira/browse/SOLR-11720 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.1 >Reporter: Vitaly Lavrov > > Scenario: > 1. Run backup restore as async command > 2. Check command status until it has 'completed' status > 3. Query collection immediately for total number of documents > The problem is the query will return incorrect number. The query will return > correct number eventually if one keeps querying. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11719) Committing to restored collection does nothing
[ https://issues.apache.org/jira/browse/SOLR-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277656#comment-16277656 ] Vitaly Lavrov commented on SOLR-11719: -- The difference is that story is about updates sent to the restored index. SOLR-11720 is about searches in a restored index sent right after restore completes. > Committing to restored collection does nothing > -- > > Key: SOLR-11719 > URL: https://issues.apache.org/jira/browse/SOLR-11719 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 7.1 >Reporter: Vitaly Lavrov > > Scenario that was reproduced many times: > 1. Restore collection > 2. Send updates > 3. Send commit > Commit request returns instantly and the index stays intact. After collection > reload or cluster reboot updates are visible and commits will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-11720) Backup restore command completes before index is ready
Vitaly Lavrov created SOLR-11720: Summary: Backup restore command completes before index is ready Key: SOLR-11720 URL: https://issues.apache.org/jira/browse/SOLR-11720 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: SolrCloud Affects Versions: 7.1 Reporter: Vitaly Lavrov Scenario: 1. Run backup restore as async command 2. Check command status until it has 'completed' status 3. Query collection immediately for total number of documents The problem is the query will return incorrect number. The query will return correct number eventually if one keeps querying. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-11719) Committing to restored collection does nothing
Vitaly Lavrov created SOLR-11719: Summary: Committing to restored collection does nothing Key: SOLR-11719 URL: https://issues.apache.org/jira/browse/SOLR-11719 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: SolrCloud Affects Versions: 7.1 Reporter: Vitaly Lavrov Scenario that was reproduced many times: 1. Restore collection 2. Send updates 3. Send commit Commit request returns instantly and the index stays intact. After collection reload or cluster reboot updates are visible and commits will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11086) Grouping by TrieDateField and DatePointField fails
[
https://issues.apache.org/jira/browse/SOLR-11086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Lavrov updated SOLR-11086:
-
Affects Version/s: 7.0.1
> Grouping by TrieDateField and DatePointField fails
> --
>
> Key: SOLR-11086
> URL: https://issues.apache.org/jira/browse/SOLR-11086
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search
>Affects Versions: 6.6, 7.0.1
>Reporter: Vitaly Lavrov
>Priority: Minor
>
> Whenever grouping is done by either TrieDateField or DatePointField in
> SolrCloud the request fails with the following error:
> {code:java}
> ERROR - 2017-07-14 13:29:29.587; [c:offers s:shard1 r:core_node1
> x:offers_shard1_replica1] org.apache.solr.common.SolrException;
> org.apache.solr.common.SolrException: Invalid Date String:'Fri Feb 16
> 00:00:00 UTC 2018'
> at
> org.apache.solr.util.DateMathParser.parseMath(DateMathParser.java:234)
> at
> org.apache.solr.schema.DatePointField.toNativeType(DatePointField.java:118)
> at
> org.apache.solr.schema.DatePointField.readableToIndexed(DatePointField.java:187)
> at
> org.apache.solr.search.grouping.distributed.command.GroupConverter.fromMutable(GroupConverter.java:57)
> at
> org.apache.solr.search.grouping.distributed.command.SearchGroupsFieldCommand.result(SearchGroupsFieldCommand.java:124)
> at
> org.apache.solr.search.grouping.distributed.shardresultserializer.SearchGroupsResultTransformer.transform(SearchGroupsResultTransformer.java:58)
> at
> org.apache.solr.search.grouping.distributed.shardresultserializer.SearchGroupsResultTransformer.transform(SearchGroupsResultTransformer.java:37)
> at
> org.apache.solr.search.grouping.CommandHandler.processResult(CommandHandler.java:206)
> at
> org.apache.solr.handler.component.QueryComponent.process(QueryComponent.java:420)
> at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:296)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477)
> at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723)
> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.server.Server.handle(Server.java:534)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
> at
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
[jira] [Created] (SOLR-11086) Grouping by TrieDateField and DatePointField fails
Vitaly Lavrov created SOLR-11086:
Summary: Grouping by TrieDateField and DatePointField fails
Key: SOLR-11086
URL: https://issues.apache.org/jira/browse/SOLR-11086
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: search
Affects Versions: 6.6
Reporter: Vitaly Lavrov
Priority: Minor
Whenever grouping is done by either TrieDateField or DatePointField in
SolrCloud the request fails with the following error:
{code:java}
ERROR - 2017-07-14 13:29:29.587; [c:offers s:shard1 r:core_node1
x:offers_shard1_replica1] org.apache.solr.common.SolrException;
org.apache.solr.common.SolrException: Invalid Date String:'Fri Feb 16 00:00:00
UTC 2018'
at
org.apache.solr.util.DateMathParser.parseMath(DateMathParser.java:234)
at
org.apache.solr.schema.DatePointField.toNativeType(DatePointField.java:118)
at
org.apache.solr.schema.DatePointField.readableToIndexed(DatePointField.java:187)
at
org.apache.solr.search.grouping.distributed.command.GroupConverter.fromMutable(GroupConverter.java:57)
at
org.apache.solr.search.grouping.distributed.command.SearchGroupsFieldCommand.result(SearchGroupsFieldCommand.java:124)
at
org.apache.solr.search.grouping.distributed.shardresultserializer.SearchGroupsResultTransformer.transform(SearchGroupsResultTransformer.java:58)
at
org.apache.solr.search.grouping.distributed.shardresultserializer.SearchGroupsResultTransformer.transform(SearchGroupsResultTransformer.java:37)
at
org.apache.solr.search.grouping.CommandHandler.processResult(CommandHandler.java:206)
at
org.apache.solr.handler.component.QueryComponent.process(QueryComponent.java:420)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:296)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477)
at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723)
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at
org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:534)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
at
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at
org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
at
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
at
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
at java.lang.Thread.run(Thread.java:748)
{code}
The
[jira] [Closed] (SOLR-10246) Support grouped faceting for date field type
[ https://issues.apache.org/jira/browse/SOLR-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Lavrov closed SOLR-10246. Resolution: Not A Problem > Support grouped faceting for date field type > > > Key: SOLR-10246 > URL: https://issues.apache.org/jira/browse/SOLR-10246 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Vitaly Lavrov > > According to documentation "Grouped faceting supports facet.field and > facet.range but currently doesn't support date and pivot faceting". > Are there any plans to support dates? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-10246) Support grouped faceting for date field type
[
https://issues.apache.org/jira/browse/SOLR-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023730#comment-16023730
]
Vitaly Lavrov edited comment on SOLR-10246 at 5/24/17 9:45 PM:
---
Yes, it is possible with Json facet api. Request (json facet part) looks like
this:
{code:language=java}
"facet" : {
"availabledates" : {
"field" : "departuredate",
"type" : "terms",
"limit" : 100,
"facet" : {
"card" : "hll(accommodationid)"
}
}
}
{code}
In the example, term facet is calculated for the date field (departuredate) and
then _hll_ function is used to get the number of unique values for
accommodationid field for each date bucket. And this is indeed equivalent of
grouped facet.
was (Author: lavrovvv):
Yes, it is possible with Json facet api. Request (json facet part) looks like
this:
{code:language=java}
"facet" : {
"availabledates" : {
"field" : "departuredate",
"type" : "terms",
"limit" : 100,
"facet" : {
"card" : "hll(accommodationid)"
}
}
}
{code}
> Support grouped faceting for date field type
>
>
> Key: SOLR-10246
> URL: https://issues.apache.org/jira/browse/SOLR-10246
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Vitaly Lavrov
>
> According to documentation "Grouped faceting supports facet.field and
> facet.range but currently doesn't support date and pivot faceting".
> Are there any plans to support dates?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10246) Support grouped faceting for date field type
[
https://issues.apache.org/jira/browse/SOLR-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023730#comment-16023730
]
Vitaly Lavrov commented on SOLR-10246:
--
Yes, it is possible with Json facet api. Request (json facet part) looks like
this:
{code:language=java}
"facet" : {
"availabledates" : {
"field" : "departuredate",
"type" : "terms",
"limit" : 100,
"facet" : {
"card" : "hll(accommodationid)"
}
}
}
{code}
> Support grouped faceting for date field type
>
>
> Key: SOLR-10246
> URL: https://issues.apache.org/jira/browse/SOLR-10246
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Vitaly Lavrov
>
> According to documentation "Grouped faceting supports facet.field and
> facet.range but currently doesn't support date and pivot faceting".
> Are there any plans to support dates?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Issue Comment Deleted] (SOLR-10246) Support grouped faceting for date field type
[ https://issues.apache.org/jira/browse/SOLR-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Lavrov updated SOLR-10246: - Comment: was deleted (was: [~mkhludnev] Json facets could be used as a solution but this functionality is marked as experimental and unstable.) > Support grouped faceting for date field type > > > Key: SOLR-10246 > URL: https://issues.apache.org/jira/browse/SOLR-10246 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Vitaly Lavrov > > According to documentation "Grouped faceting supports facet.field and > facet.range but currently doesn't support date and pivot faceting". > Are there any plans to support dates? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-10246) Support grouped faceting for date field type
[ https://issues.apache.org/jira/browse/SOLR-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925889#comment-15925889 ] Vitaly Lavrov edited comment on SOLR-10246 at 3/15/17 11:35 AM: [~mkhludnev] Json facets could be used as a solution but this functionality is marked as experimental and unstable. was (Author: lavrovvv): Json facets could be used as a solution but this functionality is marked as experimental and unstable. > Support grouped faceting for date field type > > > Key: SOLR-10246 > URL: https://issues.apache.org/jira/browse/SOLR-10246 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Vitaly Lavrov > > According to documentation "Grouped faceting supports facet.field and > facet.range but currently doesn't support date and pivot faceting". > Are there any plans to support dates? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10246) Support grouped faceting for date field type
[ https://issues.apache.org/jira/browse/SOLR-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925889#comment-15925889 ] Vitaly Lavrov commented on SOLR-10246: -- Json facets could be used as a solution but this functionality is marked as experimental and unstable. > Support grouped faceting for date field type > > > Key: SOLR-10246 > URL: https://issues.apache.org/jira/browse/SOLR-10246 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Vitaly Lavrov > > According to documentation "Grouped faceting supports facet.field and > facet.range but currently doesn't support date and pivot faceting". > Are there any plans to support dates? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-10246) Support grouped faceting for date field type
Vitaly Lavrov created SOLR-10246: Summary: Support grouped faceting for date field type Key: SOLR-10246 URL: https://issues.apache.org/jira/browse/SOLR-10246 Project: Solr Issue Type: Improvement Security Level: Public (Default Security Level. Issues are Public) Reporter: Vitaly Lavrov According to documentation "Grouped faceting supports facet.field and facet.range but currently doesn't support date and pivot faceting". Are there any plans to support dates? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
