Re: How to specify dismax related parameters like qf

[Ajax Done]

Hi Alex,

I retry again and this time it works, here is the query string:
"{!type=edismax qf=’title_s content_s’}riak solr"

Thanks,
Ajax



> On Oct 17, 2016, at 10:55 AM, Alex Moore  wrote:
> 
> Hey Ajax,
> 
> Have you tried adding those parameters to the LocalParameters {!dismax} block?
> 
> e.g.: {!type=dismax qf='myfield yourfield'}solr rocks
> 
> http://wiki.apache.org/solr/LocalParams#Basic_Syntax 
> 
> 
> Thanks,
> Alex
> 
> On Fri, Oct 14, 2016 at 3:18 PM, AJAX DoneBy Jack  > wrote:
> Hello Basho,
> 
> I am very new on Riak Search, I know can add {!dismax}before query string to 
> use it, but don't know how to specify qf or other dismax related parameters 
> in Riak Java Client. Could you advise?
> 
> Thanks,
> Ajax 
> 
> ___
> riak-users mailing list
> riak-users@lists.basho.com 
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com 
> 
> 
> 

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Inconsistency in Querying Riak TS?

[John Daily]

One of the catches regarding the quantum limit is that unless the
query starts exactly on a boundary, the effective limit is one fewer
because it is determined by the number of partitions the query has to
touch.

I suspect that's the behavior you're seeing.

Sent from my iPhone

> On Oct 17, 2016, at 9:38 PM, Joe Olson  wrote:
>
> According to the documentation at
>
> https://docs.basho.com/riak/ts/1.4.0/using/querying/guidelines/
>
> "A query covering more than a certain number of quanta (5 by default) will 
> generate the error too_many_subqueries and the query system will refuse to 
> run it. Assuming a default quantum of 15 minutes, the maximum query time 
> range is 75 minutes."
>
> However, the example shows a table of quantum 15 seconds. After the example:
>
> "The maximum time range we can query is 60s, anything beyond will fail."
>
> which seems to contradict the first assertion.
>
> Furthermore, I have been getting inconsistant behavior using the quantum.
>
> I have a code snippet placed here, demonstrating this behavior:
>
> https://gist.github.com/anonymous/a4a4ccb8617a00d38fb47a6b11571d81
>
> In this example, I set up two tables, one with a quantum of 6 hours, another 
> with a quantum of 12 days.
>
> I am using the default range (5) on my cluster.
>
> A query spanning 5 quantum partitions is allowed on the 6 hour table, a query 
> spanning 5 quantum partitions
> on the 12 day table fails with the 'too many subqueries' error.
>
> Are the number of allowed subqueries different depending on the quantum size?
>
> If so, is there more detailed documentation on the subject?
>
> Thanks!
>
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Inconsistency in Querying Riak TS?

[Joe Olson]

According to the documentation at 

https://docs.basho.com/riak/ts/1.4.0/using/querying/guidelines/

"A query covering more than a certain number of quanta (5 by default) will 
generate the error too_many_subqueries and the query system will refuse to run 
it. Assuming a default quantum of 15 minutes, the maximum query time range is 
75 minutes."

However, the example shows a table of quantum 15 seconds. After the example:

"The maximum time range we can query is 60s, anything beyond will fail."

which seems to contradict the first assertion.

Furthermore, I have been getting inconsistant behavior using the quantum. 

I have a code snippet placed here, demonstrating this behavior:

https://gist.github.com/anonymous/a4a4ccb8617a00d38fb47a6b11571d81

In this example, I set up two tables, one with a quantum of 6 hours, another 
with a quantum of 12 days.
 
I am using the default range (5) on my cluster.

A query spanning 5 quantum partitions is allowed on the 6 hour table, a query 
spanning 5 quantum partitions
on the 12 day table fails with the 'too many subqueries' error.

Are the number of allowed subqueries different depending on the quantum size? 

If so, is there more detailed documentation on the subject?

Thanks!


___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: How to specify dismax related parameters like qf

[AJAX DoneBy Jack]

Hi Alex,

I did tried that in Java client using PB, but getting exception, I can
paste the error here tonight.

Thanks,
Ajax

On Monday, 17 October 2016, Alex Moore  wrote:

> Hey Ajax,
>
> Have you tried adding those parameters to the LocalParameters {!dismax}
>  block?
>
> e.g.: {!type=dismax qf='myfield yourfield'}solr rocks
>
> http://wiki.apache.org/solr/LocalParams#Basic_Syntax
>
> Thanks,
> Alex
>
> On Fri, Oct 14, 2016 at 3:18 PM, AJAX DoneBy Jack  > wrote:
>
>> Hello Basho,
>>
>> I am very new on Riak Search, I know can add {!dismax}before query string
>> to use it, but don't know how to specify qf or other dismax related
>> parameters in Riak Java Client. Could you advise?
>>
>> Thanks,
>> Ajax
>>
>> ___
>> riak-users mailing list
>> riak-users@lists.basho.com
>> 
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: How to specify dismax related parameters like qf

[Alex Moore]

Hey Ajax,

Have you tried adding those parameters to the LocalParameters {!dismax}
 block?

e.g.: {!type=dismax qf='myfield yourfield'}solr rocks

http://wiki.apache.org/solr/LocalParams#Basic_Syntax

Thanks,
Alex

On Fri, Oct 14, 2016 at 3:18 PM, AJAX DoneBy Jack 
wrote:

> Hello Basho,
>
> I am very new on Riak Search, I know can add {!dismax}before query string
> to use it, but don't know how to specify qf or other dismax related
> parameters in Riak Java Client. Could you advise?
>
> Thanks,
> Ajax
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: How to specify dismax related parameters like qf

[Fred Dushin]

The internal solr API will not use the distributed queries generated from 
coverage plans.  You will only get results from the local node.  Theoretically, 
you could aggregate and de-duplicate across multiple nodes, but that would 
result in more data movement than necessary, as it does not leverage the "r=1" 
behavior you get from cover sets and which you get automatically from the Riak 
HTTP API.

-Fred

> On Oct 17, 2016, at 10:17 AM, AJAX DoneBy Jack  wrote:
> 
> Hi Magnus,
> 
> So you suggest to use http API right? That day I were thinking query the 
> internal Solr http by sending request. Could you advise what's the difference 
> between Riak http API and internal Solr http API? What's the pros and cons to 
> use them?
> 
> Thanks,
> Ajax
> 
> On Monday, 17 October 2016, Magnus Kessler  > wrote:
> On 14 October 2016 at 20:18, AJAX DoneBy Jack  > wrote:
> Hello Basho,
> 
> I am very new on Riak Search, I know can add {!dismax}before query string to 
> use it, but don't know how to specify qf or other dismax related parameters 
> in Riak Java Client. Could you advise?
> 
> Thanks,
> Ajax
> 
> Hi Ajax,
> 
> The Riak Java Client, as most other Riak clients, uses the Protocol Buffer 
> API to communicate with Riak. Yokozuna's implementation of the Protocol 
> Buffer API allows only for a small set of query parameters [0], which have 
> been chosen to support the standard query parser. As such, there is currently 
> no easy way to use the extended set of query parameters through the java api.
> 
> However, you may have better luck if you talk directly to HTTP API, exposed 
> at http://:8098/search/query/. This will accept all queries 
> supported by Solr 4.7. Please be aware, though, that some query results that 
> require accumulating data from all Solr nodes (such as stats queries), may 
> not work as expected. Yokozuna constructs a new coverage query very 
> frequently, and the actual results returned depend on which nodes are chosen 
> in this query.
> 
> Kind Regards,
> 
> Magnus
> 
> [0]: 
> https://github.com/basho/yokozuna/blob/develop/src/yz_pb_search.erl#L144-L150 
> 
> 
>  
> 
> ___
> riak-users mailing list
> riak-users@lists.basho.com 
> 
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com 
> 
> 
> 
> 
> 
> -- 
> Magnus Kessler
> Client Services Engineer
> Basho Technologies Limited
> 
> Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: How to specify dismax related parameters like qf

[AJAX DoneBy Jack]

Hi Magnus,

So you suggest to use http API right? That day I were thinking query the
internal Solr http by sending request. Could you advise what's the
difference between Riak http API and internal Solr http API? What's the
pros and cons to use them?

Thanks,
Ajax

On Monday, 17 October 2016, Magnus Kessler  wrote:

> On 14 October 2016 at 20:18, AJAX DoneBy Jack  > wrote:
>
>> Hello Basho,
>>
>> I am very new on Riak Search, I know can add {!dismax}before query string
>> to use it, but don't know how to specify qf or other dismax related
>> parameters in Riak Java Client. Could you advise?
>>
>> Thanks,
>> Ajax
>>
>
> Hi Ajax,
>
> The Riak Java Client, as most other Riak clients, uses the Protocol Buffer
> API to communicate with Riak. Yokozuna's implementation of the Protocol
> Buffer API allows only for a small set of query parameters [0], which have
> been chosen to support the standard query parser. As such, there is
> currently no easy way to use the extended set of query parameters through
> the java api.
>
> However, you may have better luck if you talk directly to HTTP API,
> exposed at http://:8098/search/query/. This will accept
> all queries supported by Solr 4.7. Please be aware, though, that some query
> results that require accumulating data from all Solr nodes (such as stats
> queries), may not work as expected. Yokozuna constructs a new coverage
> query very frequently, and the actual results returned depend on which
> nodes are chosen in this query.
>
> Kind Regards,
>
> Magnus
>
> [0]: https://github.com/basho/yokozuna/blob/develop/src/yz_
> pb_search.erl#L144-L150
>
>
>
>>
>> ___
>> riak-users mailing list
>> riak-users@lists.basho.com
>> 
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>
>
> --
> Magnus Kessler
> Client Services Engineer
> Basho Technologies Limited
>
> Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: How to specify dismax related parameters like qf

[Magnus Kessler]

On 14 October 2016 at 20:18, AJAX DoneBy Jack  wrote:

> Hello Basho,
>
> I am very new on Riak Search, I know can add {!dismax}before query string
> to use it, but don't know how to specify qf or other dismax related
> parameters in Riak Java Client. Could you advise?
>
> Thanks,
> Ajax
>

Hi Ajax,

The Riak Java Client, as most other Riak clients, uses the Protocol Buffer
API to communicate with Riak. Yokozuna's implementation of the Protocol
Buffer API allows only for a small set of query parameters [0], which have
been chosen to support the standard query parser. As such, there is
currently no easy way to use the extended set of query parameters through
the java api.

However, you may have better luck if you talk directly to HTTP API, exposed
at http://:8098/search/query/. This will accept all
queries supported by Solr 4.7. Please be aware, though, that some query
results that require accumulating data from all Solr nodes (such as stats
queries), may not work as expected. Yokozuna constructs a new coverage
query very frequently, and the actual results returned depend on which
nodes are chosen in this query.

Kind Regards,

Magnus

[0]:
https://github.com/basho/yokozuna/blob/develop/src/yz_pb_search.erl#L144-L150



>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>


-- 
Magnus Kessler
Client Services Engineer
Basho Technologies Limited

Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: riak claimant

[Magnus Kessler]

On 12 October 2016 at 19:07, Travis Kirstine <
tkirst...@firstbasesolutions.com> wrote:

> Does the riak claimant node have higher load than the other nodes?
>

Hi Travis,

The role of the claimant node is simply to coordinate certain cluster
related operations that involve changes to the ring, such as nodes joining
or leaving the cluster. Otherwise this node has no special role during
operations that manipulate data stored in the cluster.

Kind Regards,

Magnus



>
>
> Travis Kirstine
>
> *Project Supervisor *
>
> 140 Renfrew Drive, Suite 100
>
> Markham, Ontario L3R 6B3 Canada
>
> 
> T: 905.477.3600 Ext 267 | C: 647
>


-- 
Magnus Kessler
Client Services Engineer
Basho Technologies Limited

Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com