You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was trying to use Scroll feature with typedclient API and I got an error many times which is cannot parse scroll id. Then, I started to look into source code of package and I realized that Scroll(duration time.Duration) method updates r.req.Scroll value
That's why the scroll id that I sent cannot be added to the request and gives an error. When I added r.req.ScrollId = scrollid to ScrollId method it works correctly. I am not sure if it is a bug or not.
Scroll has been deprecated for some time now, I'd recommend you use search_after with a Point in Time.
I'm keeping this issue open, the ScrollId in the specification is optional, which means the method should point to the body. I'm going to investigate this.
Hi, I was trying to use Scroll feature with typedclient API and I got an error many times which is
cannot parse scroll id
. Then, I started to look into source code of package and I realized thatScroll(duration time.Duration)
method updates r.req.Scroll valueHowever,
ScrollId(scrollid string)
method just updates r.scrollid valueThat's why the scroll id that I sent cannot be added to the request and gives an error. When I added
r.req.ScrollId = scrollid
toScrollId
method it works correctly. I am not sure if it is a bug or not.Last version of ScrollId method :
I used it like this :
es.Scroll().Scroll(15 * time.Minute).ScrollId(scrollId).Do(context.Background())
If I'm wrong please let me know, if it is a bug how could we figure this out?
The text was updated successfully, but these errors were encountered: