amundsen: "Advanced search" returning "Page index out of bounds for available matches" error
I’m using Amundsen with neo4j and ES, with a standard docker-compose installation. The data is ingested in neo4j (visible through browser) & Elasticsearch (visible through API calls), and I can find it and diplay it using the homepage searchbar.
Expected Behavior
Advanced Search must work and return results when there are assets that match the search keywords. This actually used to work with older versions (the one on the master
branch, for example).
Using “*” as a keyword in the Source bar should return every asset.
Current Behavior
I get a Page index out of bounds for available matches
error everytime.
Possible Solution
The error is raised by the frontend service (here).
Steps to Reproduce
- Standard docker installation
- Data ingestion from a PostgreSQL database
- Using the search bar on the homepage works well
- Doing an “Advanced Search” returns the error
Screenshots (if appropriate)
Homepage search :
Advanced search :
Context
Issue appeared with newer versions of Amundsen. It happens evey single time.
Your Environment
- Amunsen version used: newest (
main
branch) - Data warehouse stores:
- Deployment (k8s or native): native (docker-compose on ubuntu)
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (4 by maintainers)
sweet! merged…
Hi @verdan 👋 I tested your last commit from the
vm-versions-upgrade
branch, and the search works great ! Can’t wait to see it merged onmain
. Thanks a lot,I believe this is because of the older version of Amundsen search. have you guys tried this using local docker-compose?, as I can see the version on the search package on docker hub is a couple of months older.
In any way, I will release a new version of the search, that should fix this problem for you all.
I am also getting the same error as https://github.com/amundsen-io/amundsen/pull/1386#issuecomment-890064706 It looks related to this breaking change in elasticsearch 7: https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html
Also having same problem, fresh git clone, runing it with docker-compose -f docker-amundsen.yml up, executing sample_data_loader.py. (After facing same problem on #1442).
Data is on Neo4j and in Elasticsearch as results shows up on direct query:
And on Neo4j:
On frontend it shows up while writing search terms, like:
But nothing on results search page, just “Page index out of bounds for available matches”
Thanks for opening your first issue here!