Open slesaad opened 1 year ago
@slesaad Thanks for posting this comparison. I'm actually not seeing the difference in the number matched for each collection. What endpoint returned that matched 0 result? I tried /collections/<collection-id>/items
and the /search
endpoints below and see one match for each collection (hopefully I didn't use the wrong collection ids but can't see it yet 🙃 ).
lis-global-da-tws-trend-airflow
curl -X 'GET' \
'https://dev-stac.delta-backend.com/search?collections=lis-global-da-tws-trend-airflow&limit=10' \
-H 'accept: application/geo+json' | jq '.context'
{
"limit": 10,
"matched": 1,
"returned": 1
}
lis-global-da-tws-trend
curl -X 'GET' \
'https://dev-stac.delta-backend.com/search?collections=lis-global-da-tws-trend&limit=10' \
-H 'accept: application/geo+json' | jq '.context'
{
"limit": 10,
"matched": 1,
"returned": 1
}
Description
As a validation of the ingests done using the [1] new airflow based pipeline, this issue runs the ingestion using both [1] and [2] legacy step functions based pipeline.
The ingest is initiated via the
veda-stac-ingestor
api, endpoint/dataset/publish
with the same inputs for both except the collection id, as can be seen below:For [2], the input was:
Similarly, for [1], the input was:
After the ingestion run was done, the stac records for both were compared and they look like the following:
Collection
[1]
[2]
Items
[1]
[2]
Comparison
On comparison, the STAC records look exactly the same for ingests from both systems [1] and [2].
PI Objective
https://github.com/NASA-IMPACT/veda-architecture/issues/164