[Koha-devel] FYI: yaz-client limitations

Tomas Cohen Arazi tomascohen at gmail.com
Mon Oct 31 18:45:57 CET 2016 

Barton told me it could be useful to share this excange I had with IdexData
people during the implementation of the Zebra facets.
It highlights a limitation on the yaz-client tool, and they suggest we
better use zoomsh.

I'm not sure if I already posted this on koha-devel, but it doesn't hurt to
re-post, and might save some people some hours and headaches.

Regards

---------- Forwarded message ---------
From: Adam Dickmeiss <adam at indexdata.dk>
Date: lun., 9 mar. 2015 a las 6:36
Subject: Re: [Info] Possible limit on the amount of specs on an elementset?
[ZEB-663]
To: Tomas Cohen Arazi <tomascohen at gmail.com>
Cc: jira at indexdata.com <jira at indexdata.com>


On 03/02/2015 12:18 PM, Tomas Cohen Arazi wrote:

Hi, I compiled 2.0.60 with the aim to patch it for a problem we are facing,
and I can say the problem I previously reported is still present:

This a limitation in yaz-client which has a limit of 100 characters for
elem command. We'll remove that limitiation. You can use zoomsh instead to
play with longer facet specs.


/ Adam


Z> elem
zebra::facet::su-to:0:100,su-geo:0:100,su-ut:0:100,au:0:100,se:0:100,itype:0:100,location:0:100,holdingbranch:0:100,homebranch:0:100,tomas:0:100
Z> s 1+1
Sent presentRequest (1+1).
Records: 1
Record type: XML
<record xmlns="http://www.indexdata.com/zebra/">
  <facet type="0" index="su-to">
  </facet>
  <facet type="0" index="su-geo">
  </facet>
  <facet type="0" index="su-ut">
  </facet>
  <facet type="0" index="au">
    <term coccur="2" occur="2">Adåker, Ulf</term>
    <term coccur="2" occur="2">Danielsson, Palle</term>
    <term coccur="2" occur="2">Stenson, Bobo</term>
    <term coccur="1" occur="1">Davis, Miles</term>
    <term coccur="1" occur="1">Löfcrantz, Johan</term>
    <term coccur="1" occur="1">Milder, Joakim</term>
    <term coccur="1" occur="1">Öström, Magnus</term>
  </facet>
  <facet type="0" index="se">
  </facet>
  <facet type="0" index="itype">
  </facet>
  <facet type="0" index="location">
  </facet>
  <facet type="0" index="holdingbranch">
  </facet>
</record>
nextResultSetPosition = 2
Elapsed: 0.001203

So 'holdingbranch' is the last facet it retrieves. If I thange the
elementset like this:

Z> elem
zebra::facet::su-to:0:100,su-geo:0:100,su-ut:0:100,au:0:100,se:0:100,itype:0:100,location:0:100,tomas:0:100,homebranch:0:100,holdingbranch:0:100

I still get a 8 facet limit:
Z> s 1+1
Sent presentRequest (1+1).
Records: 1
Record type: XML
<record xmlns="http://www.indexdata.com/zebra/">
  <facet type="0" index="su-to">
  </facet>
  <facet type="0" index="su-geo">
  </facet>
  <facet type="0" index="su-ut">
  </facet>
  <facet type="0" index="au">
    <term coccur="2" occur="2">Adåker, Ulf</term>
    <term coccur="2" occur="2">Danielsson, Palle</term>
    <term coccur="2" occur="2">Stenson, Bobo</term>
    <term coccur="1" occur="1">Davis, Miles</term>
    <term coccur="1" occur="1">Löfcrantz, Johan</term>
    <term coccur="1" occur="1">Milder, Joakim</term>
    <term coccur="1" occur="1">Öström, Magnus</term>
  </facet>
  <facet type="0" index="se">
  </facet>
  <facet type="0" index="itype">
  </facet>
  <facet type="0" index="location">
  </facet>
  <facet type="0" index="homebranch">
  </facet>
</record>
nextResultSetPosition = 2
Elapsed: 0.003697



On Mon, Feb 9, 2015 at 5:08 PM, Tomas Cohen Arazi <tomascohen at gmail.com>
wrote:

Is there a way (or could it be) to skip the error if there are elems with
results? For facets, it would be great that we could ask for n facets, and
retrieve all at once.

I'll try 2.0.59 in about two hours and reply.

El lun., 9 de febrero de 2015 12:59, Adam Dickmeiss <adam at indexdata.dk>
escribió:

On 02/09/2015 04:51 PM, Tomas Cohen Arazi wrote:

It is 2.0.44 on ubuntu 14.04. Should i try a newer?

I don't see things changes with respect to facets.. But you could try
2.0.59 out.


/ Adam


El lun., 9 de febrero de 2015 12:48, Adam Dickmeiss <adam at indexdata.dk>
escribió:

On 02/05/2015 11:27 AM, Adam Dickmeiss wrote:

Hi Tomas,

we'll look into this and get back to you. Please reply-all and keep
[ZEB-663] contents in the subject line for future conversation.

Hi Tomas,

we can't see a limit of 8. Asking for more than 8 returns more than 8. And
supplying any non-existing facet-field throws an error.

What version of Zebra are you using?


/ Adam

/ Adam

On 02/04/2015 03:59 PM, Tomas Cohen Arazi wrote:

Hi, I've been playing with facets retrieval, which shines in Koha 3.18
(thanks!)

One thing I noticed is that asking zebra to retrive more than 8 facets at
once doesn't work (it only retrieves 8). What i did was:

> elem zebra::facet::a1:0:20,...,a8:0:20,bullshit:0:20

('bullshit' doesn't exist on the facet indexes) and

> f a
> s 1+1

shows the expected results. If I do

> elem zebra::facet::a1:0:20,...,a7:0:20,bullshit:0:20

It fails ([25] Specified element set name not valid...)

Regards

-- 
Tomás Cohen Arazi
Prosecretaría de Informática
Universidad Nacional de Córdoba
✆ +54 351 5353750 ext 13168 <%2B54%20351%205353750%20ext%2013168>
GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F


_______________________________________________
Info mailing listInfo at lists.indexdata.dkhttp://lists.indexdata.dk/cgi-bin/mailman/listinfo/info







-- 
Tomás Cohen Arazi
Prosecretaría de Informática
Universidad Nacional de Córdoba
✆ +54 351 5353750 ext 13168 <0351%20535-3750>
GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F


-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161031/785fdc48/attachment-0001.html>

More information about the Koha-devel mailing list