[jira] [Updated] (SOLR-13981) Remove unused DistributedQueue interface
[
https://issues.apache.org/jira/browse/SOLR-13981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Salamon updated SOLR-13981:
--
Status: Patch Available (was: Open)
> Remove unused DistributedQueue interface
>
>
> Key: SOLR-13981
> URL: https://issues.apache.org/jira/browse/SOLR-13981
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Affects Versions: master (9.0)
>Reporter: Andras Salamon
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The
> {{solr/solrj/src/java/org/apache/solr/common/cloud/DistributedQueue.java}}
> interface is not used anywhere, we can remove this interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (LUCENE-9031) UnsupportedOperationException on highlighting Interval Query
[ https://issues.apache.org/jira/browse/LUCENE-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985269#comment-16985269 ] David Smiley commented on LUCENE-9031: -- I like your code example as it shows the path to how subclassing could do it, IMO. So imagine if a subclass then overrode createQforFoo to produce the interval variation. I'd settle on looping as better than the total duplication we have now but I think we can do better here. > UnsupportedOperationException on highlighting Interval Query > > > Key: LUCENE-9031 > URL: https://issues.apache.org/jira/browse/LUCENE-9031 > Project: Lucene - Core > Issue Type: Bug > Components: modules/queries >Reporter: Mikhail Khludnev >Assignee: Mikhail Khludnev >Priority: Major > Fix For: 8.4 > > Attachments: LUCENE-9031.patch, LUCENE-9031.patch, LUCENE-9031.patch, > LUCENE-9031.patch, LUCENE-9031.patch, LUCENE-9031.patch, LUCENE-9031.patch, > LUCENE-9031.patch, LUCENE-9031.patch > > Time Spent: 3h 50m > Remaining Estimate: 0h > > When UnifiedHighlighter highlights Interval Query it encounters > UnsupportedOperationException. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Closed] (SOLR-13669) [CVE-2019-0193] Remote Code Execution via DataImportHandler
[ https://issues.apache.org/jira/browse/SOLR-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley closed SOLR-13669. --- I left 8.1.2 there because technically it's there. > [CVE-2019-0193] Remote Code Execution via DataImportHandler > --- > > Key: SOLR-13669 > URL: https://issues.apache.org/jira/browse/SOLR-13669 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: contrib - DataImportHandler >Reporter: Michael Stepankin >Assignee: David Smiley >Priority: Major > Fix For: 8.1.2, 8.2.0 > > > The DataImportHandler, an optional but popular module to pull in data from > databases and other sources, has a feature in which the whole DIH > configuration can come from a request's "dataConfig" parameter. The debug > mode of the DIH admin screen uses this to allow convenient debugging / > development of a DIH config. Since a DIH config can contain scripts, this > parameter is a security risk. Starting with version 8.2.0 of Solr, use of > this parameter requires setting the Java System property > "enable.dih.dataConfigParam" to true. > Mitigations: > * Upgrade to 8.2.0 or later, which is secure by default. > * or, edit solrconfig.xml to configure all DataImportHandler usages with an > "invariants" section listing the "dataConfig" parameter set to am empty > string. > * Ensure your network settings are configured so that only trusted traffic > communicates with Solr, especially to the DIH request handler. This is a > best practice to all of Solr. > Credits: > * Michael Stepankin > References: > * https://issues.apache.org/jira/browse/SOLR-13669 > * https://cwiki.apache.org/confluence/display/solr/SolrSecurity -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Resolved] (SOLR-13669) [CVE-2019-0193] Remote Code Execution via DataImportHandler
[ https://issues.apache.org/jira/browse/SOLR-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley resolved SOLR-13669. - Fix Version/s: 8.2.0 Resolution: Fixed > [CVE-2019-0193] Remote Code Execution via DataImportHandler > --- > > Key: SOLR-13669 > URL: https://issues.apache.org/jira/browse/SOLR-13669 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: contrib - DataImportHandler >Reporter: Michael Stepankin >Assignee: David Smiley >Priority: Major > Fix For: 8.2.0, 8.1.2 > > > The DataImportHandler, an optional but popular module to pull in data from > databases and other sources, has a feature in which the whole DIH > configuration can come from a request's "dataConfig" parameter. The debug > mode of the DIH admin screen uses this to allow convenient debugging / > development of a DIH config. Since a DIH config can contain scripts, this > parameter is a security risk. Starting with version 8.2.0 of Solr, use of > this parameter requires setting the Java System property > "enable.dih.dataConfigParam" to true. > Mitigations: > * Upgrade to 8.2.0 or later, which is secure by default. > * or, edit solrconfig.xml to configure all DataImportHandler usages with an > "invariants" section listing the "dataConfig" parameter set to am empty > string. > * Ensure your network settings are configured so that only trusted traffic > communicates with Solr, especially to the DIH request handler. This is a > best practice to all of Solr. > Credits: > * Michael Stepankin > References: > * https://issues.apache.org/jira/browse/SOLR-13669 > * https://cwiki.apache.org/confluence/display/solr/SolrSecurity -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13897) Unsafe publication of Terms object in ZkShardTerms
[ https://issues.apache.org/jira/browse/SOLR-13897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985256#comment-16985256 ] Shalin Shekhar Mangar commented on SOLR-13897: -- Here's a patch that changes the Terms to an AtomicReference. However, I am not convinced that it is still correct. Seems there can be race conditions between registerTerm and removeTerm and also onTermUpdates might receive updates out of order (i.e. monotonic term versions are not guaranteed inside onTermUpdates) > Unsafe publication of Terms object in ZkShardTerms > -- > > Key: SOLR-13897 > URL: https://issues.apache.org/jira/browse/SOLR-13897 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 8.2, 8.3 >Reporter: Shalin Shekhar Mangar >Priority: Major > Fix For: master (9.0), 8.4 > > Attachments: SOLR-13897.patch > > > The Terms object in ZkShardTerms is written using a write lock but reading is > allowed freely. This is not safe and can cause visibility issues and > associated race conditions under contention. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13897) Unsafe publication of Terms object in ZkShardTerms
[ https://issues.apache.org/jira/browse/SOLR-13897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-13897: - Attachment: SOLR-13897.patch > Unsafe publication of Terms object in ZkShardTerms > -- > > Key: SOLR-13897 > URL: https://issues.apache.org/jira/browse/SOLR-13897 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud >Affects Versions: 8.2, 8.3 >Reporter: Shalin Shekhar Mangar >Priority: Major > Fix For: master (9.0), 8.4 > > Attachments: SOLR-13897.patch > > > The Terms object in ZkShardTerms is written using a write lock but reading is > allowed freely. This is not safe and can cause visibility issues and > associated race conditions under contention. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Resolved] (SOLR-13805) Solr - generates an NPE when calling /solr/admin/health on standalone solr
[
https://issues.apache.org/jira/browse/SOLR-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-13805.
--
Fix Version/s: 8.4
master (9.0)
Resolution: Fixed
Thanks Nicholas!
> Solr - generates an NPE when calling /solr/admin/health on standalone solr
> --
>
> Key: SOLR-13805
> URL: https://issues.apache.org/jira/browse/SOLR-13805
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud, SolrJ
>Affects Versions: 8.1, 8.2
>Reporter: Nicholas DiPiazza
>Assignee: Shalin Shekhar Mangar
>Priority: Major
> Fix For: master (9.0), 8.4
>
>
> steps to reproduce:
> unzip solr and run
> {code}
> ./bin/solr start
> {code}
> Then nav to:
> http://localhost:8983/solr/admin/health
> Result will be an NPE:
> {code}
> {
> "responseHeader":{
> "status":500,
> "QTime":20},
> "error":{
> "trace":"java.lang.NullPointerException\n\tat
> org.apache.solr.handler.admin.HealthCheckHandler.handleRequestBody(HealthCheckHandler.java:68)\n\tat
>
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:199)\n\tat
>
> org.apache.solr.servlet.HttpSolrCall.handleAdmin(HttpSolrCall.java:734)\n\tat
> org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:715)\n\tat
> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:496)\n\tat
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:377)\n\tat
>
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:323)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1634)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)\n\tat
>
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:219)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
>
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
> org.eclipse.jetty.server.Server.handle(Server.java:531)\n\tat
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352)\n\tat
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)\n\tat
>
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281)\n\tat
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102)\n\tat
> org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)\n\tat
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762)\n\tat
>
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)\n\tat
> java.lang.Thread.run(Thread.java:748)\n",
> "code":500}}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13805) Solr - generates an NPE when calling /solr/admin/health on standalone solr
[
https://issues.apache.org/jira/browse/SOLR-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985249#comment-16985249
]
ASF subversion and git services commented on SOLR-13805:
Commit ba95111d71cc4d24b5ab4e8c022a3cbde42fd283 in lucene-solr's branch
refs/heads/branch_8x from Shalin Shekhar Mangar
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ba95111 ]
SOLR-13805: NPE when calling /solr/admin/info/health on standalone solr
(cherry picked from commit 5a697344ed1be537ef2acdd18aab653283593370)
> Solr - generates an NPE when calling /solr/admin/health on standalone solr
> --
>
> Key: SOLR-13805
> URL: https://issues.apache.org/jira/browse/SOLR-13805
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud, SolrJ
>Affects Versions: 8.1, 8.2
>Reporter: Nicholas DiPiazza
>Assignee: Shalin Shekhar Mangar
>Priority: Major
>
> steps to reproduce:
> unzip solr and run
> {code}
> ./bin/solr start
> {code}
> Then nav to:
> http://localhost:8983/solr/admin/health
> Result will be an NPE:
> {code}
> {
> "responseHeader":{
> "status":500,
> "QTime":20},
> "error":{
> "trace":"java.lang.NullPointerException\n\tat
> org.apache.solr.handler.admin.HealthCheckHandler.handleRequestBody(HealthCheckHandler.java:68)\n\tat
>
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:199)\n\tat
>
> org.apache.solr.servlet.HttpSolrCall.handleAdmin(HttpSolrCall.java:734)\n\tat
> org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:715)\n\tat
> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:496)\n\tat
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:377)\n\tat
>
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:323)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1634)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)\n\tat
>
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:219)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
>
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
> org.eclipse.jetty.server.Server.handle(Server.java:531)\n\tat
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352)\n\tat
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)\n\tat
>
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281)\n\tat
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102)\n\tat
> org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)\n\tat
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762)\n\tat
>
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)\n\tat
> java.lang.Thread.run(Thread.java:748)\n",
> "code":500}}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13805) Solr - generates an NPE when calling /solr/admin/health on standalone solr
[
https://issues.apache.org/jira/browse/SOLR-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985248#comment-16985248
]
ASF subversion and git services commented on SOLR-13805:
Commit 5a697344ed1be537ef2acdd18aab653283593370 in lucene-solr's branch
refs/heads/master from Shalin Shekhar Mangar
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=5a69734 ]
SOLR-13805: NPE when calling /solr/admin/info/health on standalone solr
> Solr - generates an NPE when calling /solr/admin/health on standalone solr
> --
>
> Key: SOLR-13805
> URL: https://issues.apache.org/jira/browse/SOLR-13805
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud, SolrJ
>Affects Versions: 8.1, 8.2
>Reporter: Nicholas DiPiazza
>Assignee: Shalin Shekhar Mangar
>Priority: Major
>
> steps to reproduce:
> unzip solr and run
> {code}
> ./bin/solr start
> {code}
> Then nav to:
> http://localhost:8983/solr/admin/health
> Result will be an NPE:
> {code}
> {
> "responseHeader":{
> "status":500,
> "QTime":20},
> "error":{
> "trace":"java.lang.NullPointerException\n\tat
> org.apache.solr.handler.admin.HealthCheckHandler.handleRequestBody(HealthCheckHandler.java:68)\n\tat
>
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:199)\n\tat
>
> org.apache.solr.servlet.HttpSolrCall.handleAdmin(HttpSolrCall.java:734)\n\tat
> org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:715)\n\tat
> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:496)\n\tat
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:377)\n\tat
>
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:323)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1634)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)\n\tat
>
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219)\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:219)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
>
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n\tat
> org.eclipse.jetty.server.Server.handle(Server.java:531)\n\tat
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352)\n\tat
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)\n\tat
>
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281)\n\tat
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102)\n\tat
> org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)\n\tat
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762)\n\tat
>
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)\n\tat
> java.lang.Thread.run(Thread.java:748)\n",
> "code":500}}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-solr] KoenDG commented on issue #990: [SOLR-13885] Typo corrections.
KoenDG commented on issue #990: [SOLR-13885] Typo corrections. URL: https://github.com/apache/lucene-solr/pull/990#issuecomment-559903369 I've been updating this a bit because the changes file keeps changing. Makes me wonder: does this go under 8.4 or 9.0 ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (LUCENE-9073) IntervalQuery to respond field on toString and explain
[ https://issues.apache.org/jira/browse/LUCENE-9073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985191#comment-16985191 ] Alan Woodward commented on LUCENE-9073: --- +1 > IntervalQuery to respond field on toString and explain > -- > > Key: LUCENE-9073 > URL: https://issues.apache.org/jira/browse/LUCENE-9073 > Project: Lucene - Core > Issue Type: Improvement > Components: modules/queries >Reporter: Mikhail Khludnev >Priority: Minor > > It seems like IntervalQuery doesnt' expose the field whether on toString() > nor via explain(). I think it's worth to return field for better visibility. > WDYT, [~romseygeek] ? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Created] (SOLR-13983) remove or replace process execution in SystemInfoHandler
Robert Muir created SOLR-13983:
--
Summary: remove or replace process execution in SystemInfoHandler
Key: SOLR-13983
URL: https://issues.apache.org/jira/browse/SOLR-13983
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Robert Muir
SystemInfoHandler is the only place in solr code executing processes.
Since solr is a server/long running process listening to HTTP, ideally process
execution could be disabled (e.g. with security manager). But first this code
needs to be removed or replaced, so that there is no legitimate use of it:
{noformat}
try {
if (!Constants.WINDOWS) {
info.add( "uname", execute( "uname -a" ) );
info.add( "uptime", execute( "uptime" ) );
}
} catch( Exception ex ) {
log.warn("Unable to execute command line tools to get operating system
properties.", ex);
}
return info;
{noformat}
It already looks like its getting data from OS MXbean here, so maybe this logic
is simply outdated or not needed. It seems to be "best-effort" anyway.
Alternatively similar stuff could be fetched by reading from e.g. /proc file
system location if needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Created] (LUCENE-9073) IntervalQuery to respond field on toString and explain
Mikhail Khludnev created LUCENE-9073: Summary: IntervalQuery to respond field on toString and explain Key: LUCENE-9073 URL: https://issues.apache.org/jira/browse/LUCENE-9073 Project: Lucene - Core Issue Type: Improvement Components: modules/queries Reporter: Mikhail Khludnev It seems like IntervalQuery doesnt' expose the field whether on toString() nor via explain(). I think it's worth to return field for better visibility. WDYT, [~romseygeek] ? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13904) Make Analytics component aware of timeAllowed
[ https://issues.apache.org/jira/browse/SOLR-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-13904: Status: Patch Available (was: Open) > Make Analytics component aware of timeAllowed > - > > Key: SOLR-13904 > URL: https://issues.apache.org/jira/browse/SOLR-13904 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Mikhail Khludnev >Assignee: Houston Putman >Priority: Major > Attachments: SOLR-13904.patch, SOLR-13904.patch, SOLR-13904.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13982) set security-related http response headers by default
[
https://issues.apache.org/jira/browse/SOLR-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985184#comment-16985184
]
Robert Muir commented on SOLR-13982:
Attached is an initial patch: I confirmed all parts of the admin UI work fine
with it.
> set security-related http response headers by default
> -
>
> Key: SOLR-13982
> URL: https://issues.apache.org/jira/browse/SOLR-13982
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Robert Muir
>Priority: Major
> Attachments: SOLR-13982.patch
>
>
> Solr server should set some best practice http security response headers, to
> e.g. protect users of the admin ui against XSS/injection/clickjacking/etc
> * Content-Security-Policy
> * X-Content-Type-Options
> * X-XSS-Protection
> * X-Frame-Options
> Disabling inline javascript is important, so that e.g. if there is a bug then
> injected code doesn't get executed. Unfortunately the current admin UI
> dangerously relies on {{eval}}, so for now {{unsafe-eval}} must be allowed so
> that everything still works. This should really be cleaned up, i have the
> feeling as long as it works this way, that you can still execute stuff.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13982) set security-related http response headers by default
[
https://issues.apache.org/jira/browse/SOLR-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-13982:
---
Attachment: SOLR-13982.patch
> set security-related http response headers by default
> -
>
> Key: SOLR-13982
> URL: https://issues.apache.org/jira/browse/SOLR-13982
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Robert Muir
>Priority: Major
> Attachments: SOLR-13982.patch
>
>
> Solr server should set some best practice http security response headers, to
> e.g. protect users of the admin ui against XSS/injection/clickjacking/etc
> * Content-Security-Policy
> * X-Content-Type-Options
> * X-XSS-Protection
> * X-Frame-Options
> Disabling inline javascript is important, so that e.g. if there is a bug then
> injected code doesn't get executed. Unfortunately the current admin UI
> dangerously relies on {{eval}}, so for now {{unsafe-eval}} must be allowed so
> that everything still works. This should really be cleaned up, i have the
> feeling as long as it works this way, that you can still execute stuff.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Created] (SOLR-13982) set security-related http response headers by default
Robert Muir created SOLR-13982:
--
Summary: set security-related http response headers by default
Key: SOLR-13982
URL: https://issues.apache.org/jira/browse/SOLR-13982
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Robert Muir
Solr server should set some best practice http security response headers, to
e.g. protect users of the admin ui against XSS/injection/clickjacking/etc
* Content-Security-Policy
* X-Content-Type-Options
* X-XSS-Protection
* X-Frame-Options
Disabling inline javascript is important, so that e.g. if there is a bug then
injected code doesn't get executed. Unfortunately the current admin UI
dangerously relies on {{eval}}, so for now {{unsafe-eval}} must be allowed so
that everything still works. This should really be cleaned up, i have the
feeling as long as it works this way, that you can still execute stuff.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-solr] asalamon74 opened a new pull request #1046: SOLR-13981: Remove unused DistributedQueue interface
asalamon74 opened a new pull request #1046: SOLR-13981: Remove unused DistributedQueue interface URL: https://github.com/apache/lucene-solr/pull/1046 # Description The solr/solrj/src/java/org/apache/solr/common/cloud/DistributedQueue.java interface is not used anywhere, we can remove this interface. # Solution Remove this interface. # Tests Unit tests # Checklist Please review the following and check all that apply: - [x] I have reviewed the guidelines for [How to Contribute](https://wiki.apache.org/solr/HowToContribute) and my code conforms to the standards described there to the best of my ability. - [x] I have created a Jira issue and added the issue ID to my pull request title. - [x] I am authorized to contribute this code to the ASF and have removed any code I do not have a license to distribute. - [x] I have given Solr maintainers [access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork) to contribute to my PR branch. (optional but recommended) - [x] I have developed this patch against the `master` branch. - [x] I have run `ant precommit` and the appropriate test suite. - [ ] I have added tests for my changes. - [ ] I have added documentation for the [Ref Guide](https://github.com/apache/lucene-solr/tree/master/solr/solr-ref-guide) (for Solr changes only). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Created] (SOLR-13981) Remove unused DistributedQueue interface
Andras Salamon created SOLR-13981:
-
Summary: Remove unused DistributedQueue interface
Key: SOLR-13981
URL: https://issues.apache.org/jira/browse/SOLR-13981
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: master (9.0)
Reporter: Andras Salamon
The {{solr/solrj/src/java/org/apache/solr/common/cloud/DistributedQueue.java}}
interface is not used anywhere, we can remove this interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-solr] romseygeek opened a new pull request #1045: LUCENE-9072: Find matching terms from Matches API
romseygeek opened a new pull request #1045: LUCENE-9072: Find matching terms from Matches API URL: https://github.com/apache/lucene-solr/pull/1045 The Matches API tells us which queries have matched, and what positions they have matched at, but not necessarily which actual terms matched. This commit adds a `getMatchingTerms` method to `Matches`, allowing users to build results pages that indicate which specific query terms are present or absent in each top-k hit. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Created] (LUCENE-9072) Find matching terms from a Matches object
Alan Woodward created LUCENE-9072: - Summary: Find matching terms from a Matches object Key: LUCENE-9072 URL: https://issues.apache.org/jira/browse/LUCENE-9072 Project: Lucene - Core Issue Type: Improvement Reporter: Alan Woodward Assignee: Alan Woodward The Matches API tells us which queries have matched, and what positions they have matched at, but not necessarily which actual terms matched. This issue is for adding a way of finding matching terms, allowing users to build results pages that indicate which specific query terms are present or absent in each top-k hit. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13977) solr create -c not working unter Windows 10
[ https://issues.apache.org/jira/browse/SOLR-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984945#comment-16984945 ] Jan Høydahl commented on SOLR-13977: I know that CHANGES says 8.3.1 for this still. If there are no further re-spins of 8.3.1 I'll move the changes line to 8.4 section. Leaving open for now. > solr create -c not working unter Windows 10 > - > > Key: SOLR-13977 > URL: https://issues.apache.org/jira/browse/SOLR-13977 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: scripts and tools >Affects Versions: 8.3 >Reporter: Ana Oleski >Assignee: Jan Høydahl >Priority: Major > Fix For: 8.4, 8.3.1 > > Attachments: SOLR-13977.patch, image-2019-11-28-11-30-20-758.png > > > Hi, > I've unpacked sol 8.3.1 under Windows 10. I can successfully start the > server with bin/solr start but trying to create a core via command line > solr create -c mycore > fails with > The system cannot find the batch label specified parse_create_args > > This works in 7.7.2. I haven't testes the versions in between -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13977) solr create -c not working unter Windows 10
[ https://issues.apache.org/jira/browse/SOLR-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-13977: --- Fix Version/s: 8.4 > solr create -c not working unter Windows 10 > - > > Key: SOLR-13977 > URL: https://issues.apache.org/jira/browse/SOLR-13977 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: scripts and tools >Affects Versions: 8.3 >Reporter: Ana Oleski >Priority: Major > Fix For: 8.4, 8.3.1 > > Attachments: SOLR-13977.patch, image-2019-11-28-11-30-20-758.png > > > Hi, > I've unpacked sol 8.3.1 under Windows 10. I can successfully start the > server with bin/solr start but trying to create a core via command line > solr create -c mycore > fails with > The system cannot find the batch label specified parse_create_args > > This works in 7.7.2. I haven't testes the versions in between -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Assigned] (SOLR-13977) solr create -c not working unter Windows 10
[ https://issues.apache.org/jira/browse/SOLR-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl reassigned SOLR-13977: -- Assignee: Jan Høydahl > solr create -c not working unter Windows 10 > - > > Key: SOLR-13977 > URL: https://issues.apache.org/jira/browse/SOLR-13977 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: scripts and tools >Affects Versions: 8.3 >Reporter: Ana Oleski >Assignee: Jan Høydahl >Priority: Major > Fix For: 8.4, 8.3.1 > > Attachments: SOLR-13977.patch, image-2019-11-28-11-30-20-758.png > > > Hi, > I've unpacked sol 8.3.1 under Windows 10. I can successfully start the > server with bin/solr start but trying to create a core via command line > solr create -c mycore > fails with > The system cannot find the batch label specified parse_create_args > > This works in 7.7.2. I haven't testes the versions in between -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13977) solr create -c not working unter Windows 10
[ https://issues.apache.org/jira/browse/SOLR-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984941#comment-16984941 ] ASF subversion and git services commented on SOLR-13977: Commit 325e72c45f6420da61907523d4b7361c2ab5c41b in lucene-solr's branch refs/heads/branch_8x from Jan Høydahl [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=325e72c ] SOLR-13977: solr create -c not working under Windows 10 (cherry picked from commit 936f4b6ee9cd8c7f9a17800aadc8c5a91bdf74f6) > solr create -c not working unter Windows 10 > - > > Key: SOLR-13977 > URL: https://issues.apache.org/jira/browse/SOLR-13977 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: scripts and tools >Affects Versions: 8.3 >Reporter: Ana Oleski >Priority: Major > Fix For: 8.3.1 > > Attachments: SOLR-13977.patch, image-2019-11-28-11-30-20-758.png > > > Hi, > I've unpacked sol 8.3.1 under Windows 10. I can successfully start the > server with bin/solr start but trying to create a core via command line > solr create -c mycore > fails with > The system cannot find the batch label specified parse_create_args > > This works in 7.7.2. I haven't testes the versions in between -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13977) solr create -c not working unter Windows 10
[ https://issues.apache.org/jira/browse/SOLR-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984939#comment-16984939 ] Jan Høydahl commented on SOLR-13977: Tested the fix by downloading nightly master build from jenkins, and it works. I'll merge to 8x > solr create -c not working unter Windows 10 > - > > Key: SOLR-13977 > URL: https://issues.apache.org/jira/browse/SOLR-13977 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: scripts and tools >Affects Versions: 8.3 >Reporter: Ana Oleski >Priority: Major > Fix For: 8.3.1 > > Attachments: SOLR-13977.patch, image-2019-11-28-11-30-20-758.png > > > Hi, > I've unpacked sol 8.3.1 under Windows 10. I can successfully start the > server with bin/solr start but trying to create a core via command line > solr create -c mycore > fails with > The system cannot find the batch label specified parse_create_args > > This works in 7.7.2. I haven't testes the versions in between -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (LUCENE-9066) Modal Strategy In Concurrent Query Execution
[ https://issues.apache.org/jira/browse/LUCENE-9066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984827#comment-16984827 ] Atri Sharma commented on LUCENE-9066: - Here is the high level plan of attack that I am considering: 1) Introduce a heuristic in IndexSearcher#slices which accounts for the current work queue length of the passed in Executor. A simple idea could be to only create a new slice iff all of current conditions are met AND the executor's work queue length is less than the number of cores. 2) Introduce an interface which allows giving real time statistics about the current state of the environment which can be used by IndexSearcher to decide whether to execute a slice on a new thread or to execute it on a caller thread. Potentially, the interface can be as simple as the same heuristic as above where IndexSearcher executes a slice on a new thread only when the queue of the executor is smaller than number of cores * 1.5 (similar to what Elasticsearch does, AFAIK). The interface can be used to provide a custom implementation to IndexSearcher thus paving the path for external modules to provide statistics into the system and allowing Lucene to be a friendly neighbor in multi tenant systems. Thoughts? CC [~jpountz] > Modal Strategy In Concurrent Query Execution > > > Key: LUCENE-9066 > URL: https://issues.apache.org/jira/browse/LUCENE-9066 > Project: Lucene - Core > Issue Type: Improvement >Reporter: Atri Sharma >Priority: Major > > When executing a query concurrently today, we do not take any sort of system > statistics into account. For e.g. if the node is under high pressure, it is > not advisable to spawn a large number of threads for a query since they are > most likely to be blocked waiting for CPU to be available. However, the > converse is that for a lightly loaded cluster, the query can consume as many > threads as required. > > This Jira tracks high level efforts in this direction. The first idea is to > account the Executor's wait queue's size as a factor when allocating slices > to a query's segments. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Description:
Hi Team,
We are trying to update only child or parent document in solr 8.3 version as
per the example mentioned in
document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
, but the issue we facing is child or parent document alone not getting
updated.
When we query using parent child query not retuning updated value , but when we
query using q=*:* in debug mode enabled , document count got increased by 1
.i.e. 3 to 4 but its not replace right child doc.
Can you please let us know is there any other configuration need to be added to
support feature (or) child or parent document only update feature not
supported currently ?
*+Configuration:+*
Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
using external zookeeper.
Attached solr-config.xml , managed-schema.xml , parent child query output in
ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
file.
Same example we executed as per document .
*+Index Operation:+*
{
"id": "mydoc",
"path_s": "1.mydoc",
"parent_id_s": "mydoc",
"product_s": "T-Shirt",
"stock": [
{ "path_s": "2.mydoc-mydoc2", "id": "mydoc2", "parent_id_s":
"mydoc2", "color_s": "red", "size_ss": ["L"] }
,
{ "path_s": "2.mydoc-mydoc3", "id": "mydoc3", "parent_id_s":
"mydoc3", "color_s": "blue", "size_ss": ["M" ] }
]
}
*+Update Operation:+*
curl -X POST -H 'Content-Type: application/json'
'[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
--data-binary '
{ "id":"mydoc2", "color_s":
{"set":"test"}
}'
was:
Hi Team,
We are trying to update only child or parent document in solr 8.3 version as
per the example mentioned in
document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
, but the issue we facing is child. Or parent document alone not getting
updated.
When we query using parent child query not retuning updated value , but when we
query using q=*:* in debug mode enabled , document count got increased by 1
.i.e. 3 to 4 but its not replace right child doc.
Can you please let us know is there any other configuration need to be added to
support feature (or) child or parent document only update feature not
supported currently ?
*+Configuration:+*
Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
using external zookeeper.
Attached solr-config.xml , managed-schema.xml , parent child query output in
ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
file.
Same example we executed as per document .
*+Index Operation:+*
{
"id": "mydoc",
"path_s": "1.mydoc",
"parent_id_s": "mydoc",
"product_s": "T-Shirt",
"stock": [
{ "path_s": "2.mydoc-mydoc2", "id": "mydoc2", "parent_id_s":
"mydoc2", "color_s": "red", "size_ss": ["L"] }
,
{ "path_s": "2.mydoc-mydoc3", "id": "mydoc3", "parent_id_s":
"mydoc3", "color_s": "blue", "size_ss": ["M" ] }
]
}
*+Update Operation:+*
curl -X POST -H 'Content-Type: application/json'
'[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
--data-binary '
{ "id":"mydoc2", "color_s":
{"set":"test"}
}'
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, Screenshot 2019-11-25 at
> 4.24.36 PM.png, Screenshot 2019-11-25 at 4.26.12 PM.png, Screenshot
> 2019-11-25 at 4.30.38 PM.png, Screenshot 2019-11-25 at 4.48.54 PM.png,
> SelectAllQuery.txt, managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Description:
Hi Team,
We are trying to update only child or parent document in solr 8.3 version as
per the example mentioned in
document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
, but the issue we facing is child. Or parent document alone not getting
updated.
When we query using parent child query not retuning updated value , but when we
query using q=*:* in debug mode enabled , document count got increased by 1
.i.e. 3 to 4 but its not replace right child doc.
Can you please let us know is there any other configuration need to be added to
support feature (or) child or parent document only update feature not
supported currently ?
*+Configuration:+*
Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
using external zookeeper.
Attached solr-config.xml , managed-schema.xml , parent child query output in
ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
file.
Same example we executed as per document .
*+Index Operation:+*
{
"id": "mydoc",
"path_s": "1.mydoc",
"parent_id_s": "mydoc",
"product_s": "T-Shirt",
"stock": [
{ "path_s": "2.mydoc-mydoc2", "id": "mydoc2", "parent_id_s":
"mydoc2", "color_s": "red", "size_ss": ["L"] }
,
{ "path_s": "2.mydoc-mydoc3", "id": "mydoc3", "parent_id_s":
"mydoc3", "color_s": "blue", "size_ss": ["M" ] }
]
}
*+Update Operation:+*
curl -X POST -H 'Content-Type: application/json'
'[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
--data-binary '
{ "id":"mydoc2", "color_s":
{"set":"test"}
}'
was:
Hi Team,
We are trying to update only child or parent document in solr 8.3 version as
per the example mentioned in
document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
, but the issue we facing is child. Or parent document alone not getting
updated.
When we query using parent child query not retuning updated value , but when we
query using q=*:* in debug mode enabled , document count got increased by 1
.i.e. 3 to 4 but its not replace right child doc.
Can you please let us know is there any other configuration need to be added to
support feature (or) child or parent document only update feature not
supported currently ?
*+Configuration:+*
Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
using external zookeeper.
Attached solr-config.xml , managed-schema.xml , parent child query output in
ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
file.
Same example we executed as per document .
*+Index Operation:+*
{
"id": "mydoc",
"path_s": "1.mydoc",
"parent_id_s": "mydoc",
"product_s": "T-Shirt",
"stock": [
{ "path_s": "2.mydoc-mydoc2", "id": "mydoc2", "parent_id_s":
"mydoc2", "color_s": "red", "size_ss": ["L"] }
,
{ "path_s": "2.mydoc-mydoc3", "id": "mydoc3", "parent_id_s":
"mydoc3", "color_s": "blue", "size_ss": ["M" ] }
]
}
*+Update Operation:+*
*++*
curl -X POST -H 'Content-Type: application/json'
'[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
--data-binary '
{ "id":"mydoc2", "color_s": \\{"set":"test"}
}'
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, Screenshot 2019-11-25 at
> 4.24.36 PM.png, Screenshot 2019-11-25 at 4.26.12 PM.png, Screenshot
> 2019-11-25 at 4.30.38 PM.png, Screenshot 2019-11-25 at 4.48.54 PM.png,
> SelectAllQuery.txt, managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: Screenshot 2019-11-25 at 4.24.36 PM.png
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, Screenshot 2019-11-25 at
> 4.24.36 PM.png, Screenshot 2019-11-25 at 4.26.12 PM.png, Screenshot
> 2019-11-25 at 4.30.38 PM.png, Screenshot 2019-11-25 at 4.48.54 PM.png,
> SelectAllQuery.txt, managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
>
> { "path_s": "2.mydoc-mydoc2", "id": "mydoc2",
> "parent_id_s": "mydoc2", "color_s": "red", "size_ss": ["L"] }
> ,
>
> { "path_s": "2.mydoc-mydoc3", "id": "mydoc3",
> "parent_id_s": "mydoc3", "color_s": "blue", "size_ss": ["M" ]
> }
> ]
> }
>
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> { "id":"mydoc2", "color_s": \\{"set":"test"}
> }'
>
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: Screenshot 2019-11-25 at 4.30.38 PM.png
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, Screenshot 2019-11-25 at
> 4.24.36 PM.png, Screenshot 2019-11-25 at 4.26.12 PM.png, Screenshot
> 2019-11-25 at 4.30.38 PM.png, Screenshot 2019-11-25 at 4.48.54 PM.png,
> SelectAllQuery.txt, managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
>
> { "path_s": "2.mydoc-mydoc2", "id": "mydoc2",
> "parent_id_s": "mydoc2", "color_s": "red", "size_ss": ["L"] }
> ,
>
> { "path_s": "2.mydoc-mydoc3", "id": "mydoc3",
> "parent_id_s": "mydoc3", "color_s": "blue", "size_ss": ["M" ]
> }
> ]
> }
>
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> { "id":"mydoc2", "color_s": \\{"set":"test"}
> }'
>
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Description:
Hi Team,
We are trying to update only child or parent document in solr 8.3 version as
per the example mentioned in
document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
, but the issue we facing is child. Or parent document alone not getting
updated.
When we query using parent child query not retuning updated value , but when we
query using q=*:* in debug mode enabled , document count got increased by 1
.i.e. 3 to 4 but its not replace right child doc.
Can you please let us know is there any other configuration need to be added to
support feature (or) child or parent document only update feature not
supported currently ?
*+Configuration:+*
Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
using external zookeeper.
Attached solr-config.xml , managed-schema.xml , parent child query output in
ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
file.
Same example we executed as per document .
*+Index Operation:+*
{
"id": "mydoc",
"path_s": "1.mydoc",
"parent_id_s": "mydoc",
"product_s": "T-Shirt",
"stock": [
{ "path_s": "2.mydoc-mydoc2", "id": "mydoc2", "parent_id_s":
"mydoc2", "color_s": "red", "size_ss": ["L"] }
,
{ "path_s": "2.mydoc-mydoc3", "id": "mydoc3", "parent_id_s":
"mydoc3", "color_s": "blue", "size_ss": ["M" ] }
]
}
*+Update Operation:+*
*++*
curl -X POST -H 'Content-Type: application/json'
'[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
--data-binary '
{ "id":"mydoc2", "color_s": \\{"set":"test"}
}'
was:
Hi Team,
We are trying to update only child or parent document in solr 8.3 version as
per the example mentioned in
document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
, but the issue we facing is child. Or parent document alone not getting
updated.
When we query using parent child query not retuning updated value , but when we
query using q=*:* in debug mode enabled , document count got increased by 1
.i.e. 3 to 4 but its not replace right child doc.
Can you please let us know is there any other configuration need to be added to
support feature (or) child or parent document only update feature not
supported currently ?
*+Configuration:+*
Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
using external zookeeper.
Attached solr-config.xml , managed-schema.xml , parent child query output in
ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
file.
Same example we executed as per document .
*+Index Operation:+*
{
"id": "mydoc",
"path_s": "1.mydoc",
"parent_id_s": "mydoc",
"product_s": "T-Shirt",
"stock": [
{
"path_s": "2.mydoc-mydoc2",
"id": "mydoc2",
"parent_id_s": "mydoc2",
"color_s": "red",
"size_ss": ["L"]
},
{
"path_s": "2.mydoc-mydoc3",
"id": "mydoc3",
"parent_id_s": "mydoc3",
"color_s": "blue",
"size_ss": ["M" ]
}
]
}
!Screenshot 2019-11-25 at 4.48.54 PM.png!
*+Update Operation:+*
*++*
curl -X POST -H 'Content-Type: application/json'
'[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
--data-binary '
{
"id":"mydoc2",
"color_s": \{"set":"test"}
}'
!image-2019-11-29-14-27-16-606.png!
*+Parent Child Query Result:+*
*!Screenshot 2019-11-25 at 4.30.38 PM.png!*
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, Screenshot 2019-11-25 at
> 4.26.12 PM.png, Screenshot 2019-11-25 at 4.48.54 PM.png, SelectAllQuery.txt,
> managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: Screenshot 2019-11-25 at 4.48.54 PM.png
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, Screenshot 2019-11-25 at
> 4.26.12 PM.png, Screenshot 2019-11-25 at 4.48.54 PM.png, SelectAllQuery.txt,
> managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
>
> { "path_s": "2.mydoc-mydoc2", "id": "mydoc2",
> "parent_id_s": "mydoc2", "color_s": "red", "size_ss": ["L"] }
> ,
>
> { "path_s": "2.mydoc-mydoc3", "id": "mydoc3",
> "parent_id_s": "mydoc3", "color_s": "blue", "size_ss": ["M" ]
> }
> ]
> }
>
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> { "id":"mydoc2", "color_s": \\{"set":"test"}
> }'
>
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: Screenshot 2019-11-25 at 4.26.12 PM.png
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, Screenshot 2019-11-25 at
> 4.26.12 PM.png, Screenshot 2019-11-25 at 4.48.54 PM.png, SelectAllQuery.txt,
> managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
>
> { "path_s": "2.mydoc-mydoc2", "id": "mydoc2",
> "parent_id_s": "mydoc2", "color_s": "red", "size_ss": ["L"] }
> ,
>
> { "path_s": "2.mydoc-mydoc3", "id": "mydoc3",
> "parent_id_s": "mydoc3", "color_s": "blue", "size_ss": ["M" ]
> }
> ]
> }
>
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> { "id":"mydoc2", "color_s": \\{"set":"test"}
> }'
>
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: SelectAllQuery.txt
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, SelectAllQuery.txt,
> managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
> {
> "path_s": "2.mydoc-mydoc2",
> "id": "mydoc2",
> "parent_id_s": "mydoc2",
> "color_s": "red",
> "size_ss": ["L"]
> },
> {
> "path_s": "2.mydoc-mydoc3",
> "id": "mydoc3",
> "parent_id_s": "mydoc3",
> "color_s": "blue",
> "size_ss": ["M" ]
> }
> ]
> }
> !Screenshot 2019-11-25 at 4.48.54 PM.png!
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> {
> "id":"mydoc2",
> "color_s": \{"set":"test"}
> }'
>
> !image-2019-11-29-14-27-16-606.png!
> *+Parent Child Query Result:+*
>
> *!Screenshot 2019-11-25 at 4.30.38 PM.png!*
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: ParentChildQueryOutput.txt
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, SelectAllQuery.txt,
> managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
> {
> "path_s": "2.mydoc-mydoc2",
> "id": "mydoc2",
> "parent_id_s": "mydoc2",
> "color_s": "red",
> "size_ss": ["L"]
> },
> {
> "path_s": "2.mydoc-mydoc3",
> "id": "mydoc3",
> "parent_id_s": "mydoc3",
> "color_s": "blue",
> "size_ss": ["M" ]
> }
> ]
> }
> !Screenshot 2019-11-25 at 4.48.54 PM.png!
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> {
> "id":"mydoc2",
> "color_s": \{"set":"test"}
> }'
>
> !image-2019-11-29-14-27-16-606.png!
> *+Parent Child Query Result:+*
>
> *!Screenshot 2019-11-25 at 4.30.38 PM.png!*
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: solrconfig.xml
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, SelectAllQuery.txt,
> managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
> {
> "path_s": "2.mydoc-mydoc2",
> "id": "mydoc2",
> "parent_id_s": "mydoc2",
> "color_s": "red",
> "size_ss": ["L"]
> },
> {
> "path_s": "2.mydoc-mydoc3",
> "id": "mydoc3",
> "parent_id_s": "mydoc3",
> "color_s": "blue",
> "size_ss": ["M" ]
> }
> ]
> }
> !Screenshot 2019-11-25 at 4.48.54 PM.png!
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> {
> "id":"mydoc2",
> "color_s": \{"set":"test"}
> }'
>
> !image-2019-11-29-14-27-16-606.png!
> *+Parent Child Query Result:+*
>
> *!Screenshot 2019-11-25 at 4.30.38 PM.png!*
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-13980) Solr Parent or Child Document Update Issue
[
https://issues.apache.org/jira/browse/SOLR-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan updated SOLR-13980:
-
Attachment: managed-schema.xml
> Solr Parent or Child Document Update Issue
> --
>
> Key: SOLR-13980
> URL: https://issues.apache.org/jira/browse/SOLR-13980
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: [^solrconfig.xml]
> [^managed-schema.xml]
> [^ParentChildQueryOutput.txt]
> [^SelectAllQuery.txt]
>Reporter: Pavan
>Priority: Major
> Attachments: ParentChildQueryOutput.txt, SelectAllQuery.txt,
> managed-schema.xml, solrconfig.xml
>
>
> Hi Team,
>
> We are trying to update only child or parent document in solr 8.3 version as
> per the example mentioned in
> document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
> , but the issue we facing is child. Or parent document alone not getting
> updated.
>
> When we query using parent child query not retuning updated value , but when
> we query using q=*:* in debug mode enabled , document count got increased by
> 1 .i.e. 3 to 4 but its not replace right child doc.
>
> Can you please let us know is there any other configuration need to be added
> to support feature (or) child or parent document only update feature not
> supported currently ?
>
>
> *+Configuration:+*
> Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
> using external zookeeper.
> Attached solr-config.xml , managed-schema.xml , parent child query output in
> ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
> file.
>
>
> Same example we executed as per document .
>
> *+Index Operation:+*
>
> {
> "id": "mydoc",
> "path_s": "1.mydoc",
> "parent_id_s": "mydoc",
> "product_s": "T-Shirt",
> "stock": [
> {
> "path_s": "2.mydoc-mydoc2",
> "id": "mydoc2",
> "parent_id_s": "mydoc2",
> "color_s": "red",
> "size_ss": ["L"]
> },
> {
> "path_s": "2.mydoc-mydoc3",
> "id": "mydoc3",
> "parent_id_s": "mydoc3",
> "color_s": "blue",
> "size_ss": ["M" ]
> }
> ]
> }
> !Screenshot 2019-11-25 at 4.48.54 PM.png!
>
> *+Update Operation:+*
> *++*
> curl -X POST -H 'Content-Type: application/json'
> '[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
> --data-binary '
> {
> "id":"mydoc2",
> "color_s": \{"set":"test"}
> }'
>
> !image-2019-11-29-14-27-16-606.png!
> *+Parent Child Query Result:+*
>
> *!Screenshot 2019-11-25 at 4.30.38 PM.png!*
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Created] (SOLR-13980) Solr Parent or Child Document Update Issue
Pavan created SOLR-13980:
Summary: Solr Parent or Child Document Update Issue
Key: SOLR-13980
URL: https://issues.apache.org/jira/browse/SOLR-13980
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Environment: [^solrconfig.xml]
[^managed-schema.xml]
[^ParentChildQueryOutput.txt]
[^SelectAllQuery.txt]
Reporter: Pavan
Hi Team,
We are trying to update only child or parent document in solr 8.3 version as
per the example mentioned in
document:[https://lucene.apache.org/solr/guide/8_3/updating-parts-of-documents.html]
, but the issue we facing is child. Or parent document alone not getting
updated.
When we query using parent child query not retuning updated value , but when we
query using q=*:* in debug mode enabled , document count got increased by 1
.i.e. 3 to 4 but its not replace right child doc.
Can you please let us know is there any other configuration need to be added to
support feature (or) child or parent document only update feature not
supported currently ?
*+Configuration:+*
Running locally in SolrCloud mode with 4 Shards and 2 Replication factor ,
using external zookeeper.
Attached solr-config.xml , managed-schema.xml , parent child query output in
ParentChildQueryOutput.txt file and Query all output in SelectAllQuery.txt
file.
Same example we executed as per document .
*+Index Operation:+*
{
"id": "mydoc",
"path_s": "1.mydoc",
"parent_id_s": "mydoc",
"product_s": "T-Shirt",
"stock": [
{
"path_s": "2.mydoc-mydoc2",
"id": "mydoc2",
"parent_id_s": "mydoc2",
"color_s": "red",
"size_ss": ["L"]
},
{
"path_s": "2.mydoc-mydoc3",
"id": "mydoc3",
"parent_id_s": "mydoc3",
"color_s": "blue",
"size_ss": ["M" ]
}
]
}
!Screenshot 2019-11-25 at 4.48.54 PM.png!
*+Update Operation:+*
*++*
curl -X POST -H 'Content-Type: application/json'
'[http://localhost:8983/solr/parentchild/update/json/docs?_route_=mydoc]'
--data-binary '
{
"id":"mydoc2",
"color_s": \{"set":"test"}
}'
!image-2019-11-29-14-27-16-606.png!
*+Parent Child Query Result:+*
*!Screenshot 2019-11-25 at 4.30.38 PM.png!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
