0Pricing
Vector Databases: Pinecone, Weaviate & pgvector · Leçon

Créer un index Pinecone

Apprenez à configurer votre premier index Pinecone, en définissant ses dimensions, sa métrique et ses autres paramètres essentiels.

Créer un index Pinecone est une leçon Vector Databases: Pinecone, Weaviate & pgvector gratuite sur CoddyKit. Ceci est la leçon 1 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Vector Databases: Pinecone, Weaviate & pgvector, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Vector Databases: Pinecone, Weaviate & pgvector comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Welcome to Pinecone!

Hello! Today, we're diving into Pinecone, a leading vector database. It's designed to store and search billions of vectors incredibly fast.

Think of it as a specialized search engine for your AI's understanding of data, helping it find similar items based on their 'meaning'.

What is a Vector Index?

Before you can store and search vectors in Pinecone, you need an index.

An index is like a specialized table where your vector data (embeddings) will live. It's configured to handle vectors of a specific size and compare them using a particular mathematical method, ensuring efficient similarity searches.

Key Parameter: Dimensions

Every vector has a specific dimension, which is simply the number of values (or features) it contains. For example, a vector [0.1, 0.5, 0.2] has 3 dimensions.

When creating a Pinecone index, you must specify the dimension. This dimension must match the dimension of the embedding vectors you plan to store in it. Mismatched dimensions will cause errors!

Key Parameter: Distance Metric

To find 'similar' vectors, Pinecone needs to know how to calculate the 'distance' or 'similarity' between them. This is done using a distance metric.

  • Cosine Similarity: Measures the angle between vectors. Good for text embeddings.
  • Euclidean Distance: Measures the straight-line distance. Smaller values mean more similar.
  • Dot Product: Often used in recommendation systems, can be faster.

Choose the metric that best suits how your embeddings were generated.

Setting Up Your Pinecone Client

First, you need to initialize the Pinecone client in your Python code. This connects your application to the Pinecone service using your API key and environment.

Replace the placeholders with your actual Pinecone API key and environment (e.g., 'gcp-starter', 'us-west-2').

from pinecone import Pinecone, PodSpec

# Replace with your actual API key and environment
# Get these from your Pinecone console
api_key = "YOUR_API_KEY"
environment = "YOUR_ENVIRONMENT" 

pc = Pinecone(api_key=api_key, environment=environment)

print("Pinecone client initialized!")

Creating Your First Index

Now, let's create a Pinecone index! You'll use the create_index() method, specifying the index name, vector dimension, and distance metric.

We'll also use PodSpec to select the environment. For beginners, 'gcp-starter' is a free, convenient option.

from pinecone import Pinecone, PodSpec

# Assume pc is already initialized
# Replace with your actual API key and environment
api_key = "YOUR_API_KEY"
environment = "YOUR_ENVIRONMENT" # e.g., "gcp-starter"
pc = Pinecone(api_key=api_key, environment=environment)

index_name = "my-first-index"
dimension = 1536 # Common for OpenAI ada-002 embeddings
metric = "cosine" # Common for text embeddings

# Check if index already exists to avoid errors
if index_name not in pc.list_indexes():
    pc.create_index(
        name=index_name,
        dimension=dimension,
        metric=metric,
        spec=PodSpec(environment=environment) # Use your chosen environment
    )
    print(f"Index '{index_name}' created!")
else:
    print(f"Index '{index_name}' already exists.")

Checking Index Status

Index creation isn't instant. It takes a moment for Pinecone to provision the resources. You should always check if your index is ready before trying to use it to upsert data.

The describe_index() method provides status information, including whether the index is 'ready'.

from pinecone import Pinecone, PodSpec
import time

# Assume pc is initialized and index_name is defined
# Replace with your actual API key and environment
api_key = "YOUR_API_KEY"
environment = "YOUR_ENVIRONMENT"
pc = Pinecone(api_key=api_key, environment=environment)
index_name = "my-first-index" # Or the name of your new index

# Wait for the index to be ready
# (This loop might run indefinitely if index creation fails)
if index_name in pc.list_indexes():
    while not pc.describe_index(index_name).status['ready']:
        print(f"Waiting for index '{index_name}' to be ready...")
        time.sleep(1)
    
    print(f"Index '{index_name}' is ready!")
else:
    print(f"Index '{index_name}' does not exist. Please create it first.")

Advanced Pod Configuration

For production applications or larger datasets, you might need more control over your index's infrastructure. The PodSpec allows you to configure:

  • Pod Type: Choose more powerful computing resources (e.g., p1.x1).
  • Replicas: Increase for higher availability and read throughput.
  • Shards: Partition data across multiple servers for scalability.

The 'gcp-starter' environment handles these settings automatically for you.

from pinecone import Pinecone, PodSpec

# Assume pc is initialized
# pc = Pinecone(api_key="...", environment="...")

# Example of creating an index with advanced PodSpec settings
# This is commented out because it requires a non-starter environment
# and may incur costs.
# pc.create_index(
#     name="prod-index",
#     dimension=768,
#     metric="euclidean",
#     spec=PodSpec(
#         environment="us-west-2", # A non-starter environment
#         pod_type="p1.x1",        # A more powerful pod type
#         replicas=2,              # 2 copies of your index for redundancy
#         shards=1                 # Data partitioning
#     )
# )

print("Advanced PodSpec settings are for fine-tuning performance and scale.")

Best Practices for Index Names

Choose clear and descriptive names for your Pinecone indexes. This helps you manage multiple indexes in your project.

  • Use lowercase letters, numbers, and hyphens.
  • Avoid special characters or spaces.
  • Make them unique within your project.
  • Consider including the purpose or data source (e.g., product-catalog-embeddings, qa-docs-v2).

Index Creation Check

You've learned about the essential components needed to create a Pinecone index. Let's test your knowledge!

Recap: Pinecone Index Creation

Great job! You've learned the fundamentals of creating a Pinecone index.

  • An index is crucial for storing and searching vector embeddings.
  • Essential parameters are index name, vector dimension, and distance metric (e.g., cosine, euclidean).
  • You initialize the Pinecone client with your API key and environment.
  • Always check the index status to ensure it's ready before use.
  • PodSpec allows for advanced configuration, especially for production.

Next, we'll learn how to populate your index with actual data!

Questions Fréquemment Posées

La leçon « Créer un index Pinecone » est-elle gratuite ?

Oui — le texte complet de « Créer un index Pinecone » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Vector Databases: Pinecone, Weaviate & pgvector, passe à CoddyKit PRO. Le cours Vector Databases: Pinecone, Weaviate & pgvector comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Créer un index Pinecone » ?

Apprenez à configurer votre premier index Pinecone, en définissant ses dimensions, sa métrique et ses autres paramètres essentiels. Tu pratiques Vector Databases: Pinecone, Weaviate & pgvector avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Vector Databases: Pinecone, Weaviate & pgvector ?

Aucune expérience préalable n'est requise. Vector Databases: Pinecone, Weaviate & pgvector sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 1 sur 4.

Combien de temps prend la leçon « Créer un index Pinecone » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Vector Databases: Pinecone, Weaviate & pgvector ?

Oui. Chaque leçon Vector Databases: Pinecone, Weaviate & pgvector inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Créer un index Pinecone
  2. Insérer ou mettre à jour des données dans Pinecone
  3. Interroger des données vectorielles dans Pinecone
  4. Comprendre la tarification et les pods de Pinecone
← Retour à Vector Databases: Pinecone, Weaviate & pgvector