# Namespaces and Pinecone v4

**URL:** <https://community.pinecone.io/t/namespaces-and-pinecone-v4/2638>\
**Category:** Support\
**Tags:** vector-database\
**Created:** [July 11, 2023, 9:00pm UTC](https://community.pinecone.io/t/namespaces-and-pinecone-v4/2638 "2023-07-11T21:00:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gdj0nes](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/gdj0nes/32/223_2.png) [@gdj0nes](https://community.pinecone.io/u/gdj0nes)\
**Post date:** [July 13, 2023, 11:41am UTC](https://community.pinecone.io/t/namespaces-and-pinecone-v4/2638/4 "2023-07-13T11:41:24Z")

</div>

We’ve reverted the change to langchain. Existing indexes are not impacted and namespaces will continue to remain part of our paid product.

> [@Will my us-west4-gcp-free be migrated to the new gcp-starter?](https://community.pinecone.io/t/will-my-us-west4-gcp-free-be-migrated-to-the-new-gcp-starter/2650/2):
>
> Thanks for reaching out! Existing indexes free tier indexes are not impacted and will not be migrated. We have no plan to deprecate namespaces for paid indexes. Users in gcp-starter users who have a multi-tenancy use case should utilize metadata filtering to partition their data.

---

_[View the full topic](https://community.pinecone.io/t/namespaces-and-pinecone-v4/2638)._
