[jira] [Commented] (SOLR-12505) Streaming expressions - fetch() does not work as expected

2018-06-21 Thread Dariusz Wojtas (JIRA)


[ 
https://issues.apache.org/jira/browse/SOLR-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518981#comment-16518981
 ] 

Dariusz Wojtas commented on SOLR-12505:
---

[~joel.bernstein] - your guess is correct.

I have tried two changes in the _/select_ handler definition:
 # changed _defType_ to _lucene_
 # commented out the _defType_ parameter

and in both cases it started to work as expected, I get the enriched values.

 

> Streaming expressions - fetch() does not work as expected
> -
>
> Key: SOLR-12505
> URL: https://issues.apache.org/jira/browse/SOLR-12505
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 7.3.1
> Environment: Windows 10, Java 10, Solr Cloud 7.3.1
>Reporter: Dariusz Wojtas
>Assignee: Joel Bernstein
>Priority: Major
> Attachments: names.zip
>
>
> The issue:
>  # when I try to use fetch() within a streaming expression, it does not 
> enrich the inner source data. The result is exactly the same as if there was 
> no surrounding fetch() function.
>  # but it works if I try to do a leftOuterJoin() function instead.
> Use the attached 'names' collection configuration.
>  SOLR works in _cloud_ mode, streaming expressions do work, ie. stream(), 
> join(), etc
> Data to be inserted:
>  ==
> {code:xml}
> 
>  
>   1
>   entity
>   Orignal Darek name
>   uk
>   
>N001
>1
>alternate
>Darek
>   
>   
>N002
>1
>alternate
>Darke
>   
>   
>N003
>1
>alternate
>   Darko
>   
>  
>  
>   2
>   entity
>   Texaco
>   de
>   
>N0011
>2
>alternate
>Texxo
>   
>   
>N0012
>2
>alternate
>Texoco
>   
>  
> 
> {code}
> ==
>  The streaming query to execute.
>  Simplified, as the mainsearch usually does more complext stuff.
>  ==
> {noformat}
>  fetch( 
>  names,
>  search(names,
>  qt="/select",
>  q="*:*",
>  fq="type:alternate",
>  fl="parentId, alias",
>  rows=10,
>  sort="parentId asc"), 
>  on="parentId=id",
>  fl="name,country"
>  )
> {noformat}
> ==
> *Result*:
>  * Collection of attributes: parentId, alias
> *Expected result*:
>  * Collection of attributes: parentId, alias, name, country



--
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] [Updated] (SOLR-12505) Streaming expressions - fetch() does not work as expected

2018-06-20 Thread Dariusz Wojtas (JIRA)


 [ 
https://issues.apache.org/jira/browse/SOLR-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dariusz Wojtas updated SOLR-12505:
--
Description: 
The issue:
 # when I try to use fetch() within a streaming expression, it does not enrich 
the inner source data. The result is exactly the same as if there was no 
surrounding fetch() function.
 # but it works if I try to do a leftOuterJoin() function instead.

Use the attached 'names' collection configuration.
 SOLR works in _cloud_ mode, streaming expressions do work, ie. stream(), 
join(), etc

Data to be inserted:
 ==
{code:xml}

 
  1
  entity
  Orignal Darek name
  uk
  
   N001
   1
   alternate
   Darek
  
  
   N002
   1
   alternate
   Darke
  
  
   N003
   1
   alternate
  Darko
  
 
 
  2
  entity
  Texaco
  de
  
   N0011
   2
   alternate
   Texxo
  
  
   N0012
   2
   alternate
   Texoco
  
 

{code}
==
 The streaming query to execute.
 Simplified, as the mainsearch usually does more complext stuff.
 ==
{noformat}
 fetch( 
 names,
 search(names,
 qt="/select",
 q="*:*",
 fq="type:alternate",
 fl="parentId, alias",
 rows=10,
 sort="parentId asc"), 
 on="parentId=id",
 fl="name,country"
 )
{noformat}
==

*Result*:
 * Collection of attributes: parentId, alias

*Expected result*:
 * Collection of attributes: parentId, alias, name, country

  was:
The issue:
 # when I try to use fetch() within a streaming expression, it does not enrich 
the inner source data. The result is exactly the same as if there was no 
surrounding fetch() function.
 # but it works if I try to do a leftOuterJoin() function instead.

Use the attached 'names' collection configuration.
 SOLR works in _cloud_ mode, streaming expressions do work, ie. stream(), 
join(), etc

Data to be inserted:
 ==
{code:xml}
 
 
 1
 entity
 Orignal Darek name
 uk
 
 N001
 1
 alternate
 Darek
 
 
 N002
 1
 alternate
 Darke
 
 
 N003
 1
 alternate
 Darko
 
 
 
 2
 entity
 Texaco
 de
 
 N0011
 2
 alternate
 Texxo
 
 
 N0012
 2
 alternate
 Texoco
 
 
 
{code}
==
 The streaming query to execute.
 Simplified, as the mainsearch usually does more complext stuff.
 ==
{noformat}
 fetch( 
 names,
 search(names,
 qt="/select",
 q="*:*",
 fq="type:alternate",
 fl="parentId, alias",
 rows=10,
 sort="parentId asc"), 
 on="parentId=id",
 fl="name,country"
 )
{noformat}
==

*Result*:
 * Collection of attributes: parentId, alias

*Expected result*:
 * Collection of attributes: parentId, alias, name, country


> Streaming expressions - fetch() does not work as expected
> -
>
> Key: SOLR-12505
> URL: https://issues.apache.org/jira/browse/SOLR-12505
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 7.3.1
> Environment: Windows 10, Java 10, Solr Cloud 7.3.1
>Reporter: Dariusz Wojtas
>Priority: Major
> Attachments: names.zip
>
>
> The issue:
>  # when I try to use fetch() within a streaming expression, it does not 
> enrich the inner source data. The result is exactly the same as if there was 
> no surrounding fetch() function.
>  # but it works if I try to do a leftOuterJoin() function instead.
> Use the attached 'names' collection configuration.
>  SOLR works in _cloud_ mode, streaming expressions do work, ie. stream(), 
> join(), etc
> Data to be inserted:
>  ==
> {code:xml}
> 
>  
>   1
>   entity
>   Orignal Darek name
>   uk
>   
>N001
>1
>alternate
>Darek
>   
>   
>N002
>1
>alternate
>Darke
>   
>   
>N003
>1
>alternate
>   Darko
>   
>  
>  
>   2
>   entity
>   Texaco
>   de
>   
>N0011
>2
>alternate
>Texxo
>   
>   
>N0012
>2
>alternate
>Texoco
>   
>  
> 
> {code}
> ==
>  The streaming query to execute.
>  Simplified, as the mainsearch usually does more complext stuff.
>  ==
> {noformat}
>  fetch( 
>  names,
>  search(names,
>  qt="/select",
>  q="*:*",
>  fq="type:alternate",
>  fl="parentId, alias",
>  rows=10,
>  sort="parentId asc"), 
>  on="parentId=id",
>  fl="name,country"
>  )
> {noformat}
> ==
> *Result*:
>  * Collection of attributes: parentId, alias
> *Expected result*:
>  * Collection of attributes: parentId, alias, name, country



--
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] [Updated] (SOLR-12505) Streaming expressions - fetch() does not work as expected

2018-06-20 Thread Dariusz Wojtas (JIRA)


 [ 
https://issues.apache.org/jira/browse/SOLR-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dariusz Wojtas updated SOLR-12505:
--
Attachment: names.zip

> Streaming expressions - fetch() does not work as expected
> -
>
> Key: SOLR-12505
> URL: https://issues.apache.org/jira/browse/SOLR-12505
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 7.3.1
> Environment: Windows 10, Java 10, Solr Cloud 7.3.1
>Reporter: Dariusz Wojtas
>Priority: Major
> Attachments: names.zip
>
>
> The issue:
>  # when I try to use fetch() within a streaming expression, it does not 
> enrich the inner source data. The result is exactly the same as if there was 
> no surrounding fetch() function.
>  # but it works if I try to do a leftOuterJoin() function instead.
> Use the attached 'names' collection configuration.
>  SOLR works in _cloud_ mode, streaming expressions do work, ie. stream(), 
> join(), etc
> Data to be inserted:
>  ==
> {code:xml}
>  
>  
>  1
>  entity
>  Orignal Darek name
>  uk
>  
>  N001
>  1
>  alternate
>  Darek
>  
>  
>  N002
>  1
>  alternate
>  Darke
>  
>  
>  N003
>  1
>  alternate
>  Darko
>  
>  
>  
>  2
>  entity
>  Texaco
>  de
>  
>  N0011
>  2
>  alternate
>  Texxo
>  
>  
>  N0012
>  2
>  alternate
>  Texoco
>  
>  
>  
> {code}
> ==
>  The streaming query to execute.
>  Simplified, as the mainsearch usually does more complext stuff.
>  ==
> {noformat}
>  fetch( 
>  names,
>  search(names,
>  qt="/select",
>  q="*:*",
>  fq="type:alternate",
>  fl="parentId, alias",
>  rows=10,
>  sort="parentId asc"), 
>  on="parentId=id",
>  fl="name,country"
>  )
> {noformat}
> ==
> *Result*:
>  * Collection of attributes: parentId, alias
> *Expected result*:
>  * Collection of attributes: parentId, alias, name, country



--
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] [Created] (SOLR-12505) Streaming expressions - fetch() does not work as expected

2018-06-20 Thread Dariusz Wojtas (JIRA)
Dariusz Wojtas created SOLR-12505:
-

 Summary: Streaming expressions - fetch() does not work as expected
 Key: SOLR-12505
 URL: https://issues.apache.org/jira/browse/SOLR-12505
 Project: Solr
  Issue Type: Bug
  Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 7.3.1
 Environment: Windows 10, Java 10, Solr Cloud 7.3.1
Reporter: Dariusz Wojtas


The issue:
 # when I try to use fetch() within a streaming expression, it does not enrich 
the inner source data. The result is exactly the same as if there was no 
surrounding fetch() function.
 # but it works if I try to do a leftOuterJoin() function instead.

Use the attached 'names' collection configuration.
 SOLR works in _cloud_ mode, streaming expressions do work, ie. stream(), 
join(), etc

Data to be inserted:
 ==
{code:xml}
 
 
 1
 entity
 Orignal Darek name
 uk
 
 N001
 1
 alternate
 Darek
 
 
 N002
 1
 alternate
 Darke
 
 
 N003
 1
 alternate
 Darko
 
 
 
 2
 entity
 Texaco
 de
 
 N0011
 2
 alternate
 Texxo
 
 
 N0012
 2
 alternate
 Texoco
 
 
 
{code}
==
 The streaming query to execute.
 Simplified, as the mainsearch usually does more complext stuff.
 ==
{noformat}
 fetch( 
 names,
 search(names,
 qt="/select",
 q="*:*",
 fq="type:alternate",
 fl="parentId, alias",
 rows=10,
 sort="parentId asc"), 
 on="parentId=id",
 fl="name,country"
 )
{noformat}
==

*Result*:
 * Collection of attributes: parentId, alias

*Expected result*:
 * Collection of attributes: parentId, alias, name, country



--
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] [Closed] (SOLR-11848) User guide update on working with XML updates

2018-02-01 Thread Dariusz Wojtas (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dariusz Wojtas closed SOLR-11848.
-

> User guide update on working with XML updates
> -
>
> Key: SOLR-11848
> URL: https://issues.apache.org/jira/browse/SOLR-11848
> Project: Solr
>  Issue Type: Improvement
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation
>Affects Versions: 7.2
>Reporter: Dariusz Wojtas
>Assignee: Cassandra Targett
>Priority: Minor
> Fix For: 7.3
>
>
> I have added some additional information to the user guide in repository:
>   https://github.com/apache/lucene-solr/pull/303
> this covers info about:
> # grouping XML commands with the  element
> # more effective way of working with curl for large files - the original 
> approach described in the guide with _--data-binary_ results in curl out of 
> memory errors for large files being uploaded



--
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] [Updated] (SOLR-11848) User guide update on working with XML updates

2018-01-12 Thread Dariusz Wojtas (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dariusz Wojtas updated SOLR-11848:
--
Component/s: documentation

> User guide update on working with XML updates
> -
>
> Key: SOLR-11848
> URL: https://issues.apache.org/jira/browse/SOLR-11848
> Project: Solr
>  Issue Type: Improvement
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: documentation
>Affects Versions: 7.2
>Reporter: Dariusz Wojtas
>Priority: Minor
>
> I have added some additional information to the user guide in repository:
>   https://github.com/apache/lucene-solr/pull/303
> this covers info about:
> # grouping XML commands with the  element
> # more effective way of working with curl for large files - the original 
> approach described in the guide with _--data-binary_ results in curl out of 
> memory errors for large files being uploaded



--
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-11848) User guide update on working with XML updates

2018-01-12 Thread Dariusz Wojtas (JIRA)
Dariusz Wojtas created SOLR-11848:
-

 Summary: User guide update on working with XML updates
 Key: SOLR-11848
 URL: https://issues.apache.org/jira/browse/SOLR-11848
 Project: Solr
  Issue Type: Improvement
  Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 7.2
Reporter: Dariusz Wojtas
Priority: Minor


I have added some additional information to the user guide in repository:
  https://github.com/apache/lucene-solr/pull/303

this covers info about:
# grouping XML commands with the  element
# more effective way of working with curl for large files - the original 
approach described in the guide with _--data-binary_ results in curl out of 
memory errors for large files being uploaded



--
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-11809) LTR does not work under SOLR 7.2

2018-01-02 Thread Dariusz Wojtas (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dariusz Wojtas updated SOLR-11809:
--
Description: 
The LTR functionality that works under SOLR 7.0 and 7.1 stopped working in 7.2.
>From the solr-user mailing list it appears it might be related to SOLR-11501 .
I am attaching the minimal working collection definition (attached 
[^ltr-sample.zip]) that shows the problem.

Please deploy the collection (unpack under "server/solr"), run solr and invoke 
the URL below.
  http://localhost:8983/solr/ltr-sample/select?q=*:*

Behaviour:
* under 7.0 and 7.1 - empty resultset is returned (there is no data in the 
collection)
* under 7.2 - error: "rq parameter must be a RankQuery". The stacktrace
{code}
2018-01-02 20:51:06.807 INFO  (qtp205125520-20) [   x:ltr-sample] 
o.a.s.c.S.Request [ltr-sample]  webapp=/solr path=/select 
params={q=*:*&_=1514909140928} status=400 QTime=23
2018-01-02 21:04:27.293 ERROR (qtp205125520-17) [   x:ltr-sample] 
o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: rq parameter 
must be a RankQuery
at 
org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:183)
at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:269)
at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:177)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503)
at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710)
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
[..]
{code}

i have checked - the same issue exists when I try to invoke the _rerank_ query 
parser.

  was:
The LTR functionality that works under SOLR 7.0 and 7.1 stopped working in 7.2.
>From the solr-user mailing list it appears it might be related to SOLR-11501 .
I am attaching the minimal working collection definition (attached 
[^ltr-sample.zip]) that shows the problem.

Please deploy the collection (unpack under "server/solr"), run solr and invoke 
the URL below.
  http://localhost:8983/solr/ltr-sample/select?q=*:*

Behaviour:
* under 7.0 and 7.1 - empty resultset is returned (there is no data in the 
collection)
* under 7.2 - error: "rq parameter must be a RankQuery". The stacktrace
{code}
2018-01-02 20:51:06.807 INFO  (qtp205125520-20) [   x:ltr-sample] 
o.a.s.c.S.Request [ltr-sample]  webapp=/solr path=/select 
params={q=*:*&_=1514909140928} status=400 QTime=23
2018-01-02 21:04:27.293 ERROR (qtp205125520-17) [   x:ltr-sample] 
o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: rq parameter 
must be a RankQuery
at 
org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:183)
at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:269)
at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:177)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503)
at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710)
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
[..]
{code}


> LTR does not work under SOLR 7.2
> 
>
> Key: SOLR-11809
> URL: https://issues.apache.org/jira/browse/SOLR-11809
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 7.2
> Environment: Windows 10, java version "1.8.0_151"
>Reporter: Dariusz Wojtas
> Attachments: ltr-sample.zip
>
>
> The LTR functionality that works under SOLR 7.0 and 7.1 stopped working in 
> 7.2.
> From the solr-user mailing list it appears it might be related to SOLR-11501 .
> I am attaching the minimal working collection definition (attached 
> [^ltr-sample.zip]) that shows the problem.
> Please deploy the collection (unpack under "server/solr"), run solr and 
> invoke the URL below.
>   http://localhost:8983/solr/ltr-sample/select?q=*:*
> Behaviour:
> * under 7.0 and 7.1 - empty resultset is returned 

[jira] [Created] (SOLR-11809) LTR does not work under SOLR 7.2

2018-01-02 Thread Dariusz Wojtas (JIRA)
Dariusz Wojtas created SOLR-11809:
-

 Summary: LTR does not work under SOLR 7.2
 Key: SOLR-11809
 URL: https://issues.apache.org/jira/browse/SOLR-11809
 Project: Solr
  Issue Type: Bug
  Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 7.2
 Environment: Windows 10, java version "1.8.0_151"
Reporter: Dariusz Wojtas
 Attachments: ltr-sample.zip

The LTR functionality that works under SOLR 7.0 and 7.1 stopped working in 7.2.
>From the solr-user mailing list it appears it might be related to SOLR-11501 .
I am attaching the minimal working collection definition (attached 
[^ltr-sample.zip]) that shows the problem.

Please deploy the collection (unpack under "server/solr"), run solr and invoke 
the URL below.
  http://localhost:8983/solr/ltr-sample/select?q=*:*

Behaviour:
* under 7.0 and 7.1 - empty resultset is returned (there is no data in the 
collection)
* under 7.2 - error: "rq parameter must be a RankQuery". The stacktrace
{code}
2018-01-02 20:51:06.807 INFO  (qtp205125520-20) [   x:ltr-sample] 
o.a.s.c.S.Request [ltr-sample]  webapp=/solr path=/select 
params={q=*:*&_=1514909140928} status=400 QTime=23
2018-01-02 21:04:27.293 ERROR (qtp205125520-17) [   x:ltr-sample] 
o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: rq parameter 
must be a RankQuery
at 
org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:183)
at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:269)
at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:177)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503)
at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710)
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
[..]
{code}



--
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