Vector Databases: Pinecone, Weaviate & pgvector · レッスン

Pineconeインデックスの作成

最初のPineconeインデックスをセットアップし、次元数、メトリクス、その他の重要なパラメーターを設定する方法を学びます。

「Pineconeインデックスの作成」はCoddyKit上の無料Vector Databases: Pinecone, Weaviate & pgvectorレッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはVector Databases: Pinecone, Weaviate & pgvector学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Vector Databases: Pinecone, Weaviate & pgvectorコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

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!

よくある質問

「Pineconeインデックスの作成」レッスンは無料ですか？

はい。「Pineconeインデックスの作成」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Vector Databases: Pinecone, Weaviate & pgvectorコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Vector Databases: Pinecone, Weaviate & pgvectorコースには全4レッスンが含まれています。

「Pineconeインデックスの作成」で何を学びますか？

最初のPineconeインデックスをセットアップし、次元数、メトリクス、その他の重要なパラメーターを設定する方法を学びます。ブラウザで直接実行するハンズオンコードでVector Databases: Pinecone, Weaviate & pgvectorを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Vector Databases: Pinecone, Weaviate & pgvectorを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのVector Databases: Pinecone, Weaviate & pgvectorは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/4です。

「Pineconeインデックスの作成」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このVector Databases: Pinecone, Weaviate & pgvectorレッスンでコードを書いて実行できますか？

はい。すべてのVector Databases: Pinecone, Weaviate & pgvectorレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Vector Databases: Pinecone, Weaviate & pgvectorに戻る