Box Status

Bug report in Search method

フォローする
新規投稿
Support

Hello,

We have detected a problem using your API. Concretely we are trying to search all files inside a folder using the paginated “Search” method (https://api.box.com/2.0/search).

The problem is that when we reach the number of 10000 files, the API fails and returns a “Bad Request” error. Your documentation doesn’t indicate anything about a limit regarding number of files, only that the pagination parameters a maximum of 200 results at a time.

Attached you can find some screenshots to illustrate the problem:

1. From 9800 to 10000.

2. From 10000 to 10200.

3. From 9801 to 10001. Here we have a more descriptive error:

Furthermore, we’ve detected other bug with this Search method regarding the query parameter. It looks like when using spaces between characters it allows a max number of characters in the filter. That’s why we added in the filter the “%” characters as you can see in the previous screenshots. We realized that doing the query like that it works. Please, see the example below to better understanding:

1. Filtering files containing a, b, c, d or e:

2. Adding character f to the query:

In the next screenshot you can see that the error is happening in your web application too.

Hope you can solve this as soon as possible. These errors are blocking our document management application.

Thanks in advance.

0

コメント

6件のコメント

日付 投票
  • Peter Christensen

    HI 

    Yes, there is a 10K offset limit on the search endpoint. This is currently missing from our online documentation but this should be corrected shortly.

    Best regards,
    Peter Christensen, Platform Solutions Engineer, Box

    0
    コメントアクション パーマリンク
  • Support

    Hi Peter,

    any plans to increase that limit? I don't fully understand the reason of this limitation. The search is already recognizing that the folder contains more than 10000 files and the response is being paginated, it shouldn't be a problem the total number of elements, isn't it?

    Regarding the "query" parameter issue, do you have any comment?

    Best.

    0
    コメントアクション パーマリンク
  • Peter Christensen

    I am not aware of any plans to increase the limit at this point. I believe the limit is to protect the overall performance of the search functionality which is primarily there to serve search use cases where users are searching for specific content rather than more reporting style use cases. 

    With regards to the other problem I will check and log a bug if reproducible

    Best regards

    Peter Christensen, Platform Solutions Engineer, Box

    0
    コメントアクション パーマリンク
  • Support

    But you have introduced this limitation recently, because we have discovered folders with more than 20000 files three months ago using the same method and worked correctly. We've started experiencing this issue the last week.

    Regarding the other issue is easily reproducible, you can see it with my postman screenshots or using your web application.

    Best regards.

    0
    コメントアクション パーマリンク
  • Peter Christensen

    Yes, it is a new limitation. I haven't got the exact date it was implemented but it is within the last month or so.

    Regarding the other issue, I can reproduce this but having some issues justifying a search use case where you search for 6 distinct letters rather than words where it works fine with 6+ words. 

    Rgds

    Peter

    0
    コメントアクション パーマリンク
  • Support

    Ok Peter, understood.

    Thanks for the support.

    Regards.

    0
    コメントアクション パーマリンク

投稿コメントは受け付けていません。