# Point In Time Search using wild card index

**URL:** <https://discuss.elastic.co/t/point-in-time-search-using-wild-card-index/290329>\
**Category:** Elasticsearch\
**Tags:** language-clients, point-in-time\
**Created:** [November 27, 2021, 9:36am UTC](https://discuss.elastic.co/t/point-in-time-search-using-wild-card-index/290329 "2021-11-27T09:36:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rohith511](https://avatars.discourse-cdn.com/v4/letter/r/3ab097/32.png) [@rohith511](https://discuss.elastic.co/u/rohith511)\
**Post date:** [November 27, 2021, 9:36am UTC](https://discuss.elastic.co/t/point-in-time-search-using-wild-card-index/290329/1 "2021-11-27T09:36:02Z")

</div>

Sometime back when we created elastic we created multiple indexes with same initial pattern and these are dynamic suffix.  
(eg : microservice\_logs\_XYZ , microservice\_logs\_abc , microservice\_logs\_pqr etc..)  
Not sure the reason why our past team created in that fashion , probably to avoid indexing delays as log volumes are huge.

Now when we started implementing log processing using Python Client ( same is case with REST API) , we opted with 'Point In Time' pagination mode instead of 'Scroll After' as it was recommended by elastic.

Then we started going with creation of PIT ID using wildcard index (microservice\_logs\*), so it can search data requested from all indexes at once.

When we invoke python client/Rest call with search query using PIT ID , first 9999 records where good (as max search size was set to 10000) , when its going for second page (iteration) of PIT search - we are getting 404 status with below exception :

````
            ```

````

"type": "index\_not\_found\_exception",  
"reason": "no such index [microservice\_logs\_ABC-008127]",  
"index\_uuid": "_na_",  
"resource.type": "index\_expression"

```auto

My understanding from reading exception is , might be that specific index not available for search . So trying to unpack this exception more from PIT standpoint : 

a. If that specific index is not available for search , why records from that index are returned for PIT on first place ??
b. Is there a way to procced further with pagination search by ignoring this specific index ??
currently its a hard stop there. 

Kindly help in understanding more about this exception.
```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 25, 2021, 9:36am UTC](https://discuss.elastic.co/t/point-in-time-search-using-wild-card-index/290329/2 "2021-12-25T09:36:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.