vectorwave 0.1.2__tar.gz → 0.1.3__tar.gz

{vectorwave-0.1.2/src/vectorwave.egg-info → vectorwave-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vectorwave
-Version: 0.1.2
+Version: 0.1.3
 Summary: VectorWave: Seamless Auto-Vectorization Framework
 Author-email: junyeonggim <junyeonggim5@gmail.com>
 License-Expression: MIT
@@ -162,51 +162,112 @@ for i, span in enumerate(trace_spans):
 # - [Span 2] step_2_send_receipt (202.06ms)
 # - [Span 3] process_payment (333.18ms)
 ```
-
 -----
 
 ## ⚙️ Configuration
 
-VectorWave automatically reads Weaviate database connection information from **environment variables** or a `.env` file.
+VectorWave automatically reads Weaviate database connection info and **vectorization strategy** from **environment variables** or a `.env` file.
+
+Create a `.env` file in your project's root directory (e.g., where `test_ex/example.py` is located) and set the required values.
+
+### Vectorizer Strategy (VECTORIZER)
+
+You can select the text vectorization method via the `VECTORIZER` environment variable in your `test_ex/.env` file.
+
+| `VECTORIZER` Setting | Description | Required Additional Settings |
+| :--- | :--- | :--- |
+| **`huggingface`** | (Default Recommended) Uses the `sentence-transformers` library to vectorize on your local CPU. No API key is needed, making it great for immediate testing. | `HF_MODEL_NAME` (e.g., "sentence-transformers/all-MiniLM-L6-v2") |
+| **`openai_client`** | (High-Performance) Uses the OpenAI Python client to vectorize with modern models like `text-embedding-3-small`. | `OPENAI_API_KEY` (A valid OpenAI API key) |
+| **`weaviate_module`** | (Docker Delegate) Delegates the vectorization task to the Weaviate container's built-in module (e.g., `text2vec-openai`). | `WEAVIATE_VECTORIZER_MODULE`, `OPENAI_API_KEY` |
+| **`none`** | Disables vectorization. Data will be stored without vectors. | None |
+
+-----
+
+### .env File Examples
+
+Configure your `.env` file according to the strategy you want to use.
+
+#### Example 1: Using `huggingface` (Local, No API Key)
+
+Uses a `sentence-transformers` model on your local machine. Ideal for testing without API keys.
+
+```ini
+# .env (Using HuggingFace)
+# --- Basic Weaviate Connection ---
+WEAVIATE_HOST=localhost
+WEAVIATE_PORT=8080
+WEAVIATE_GRPC_PORT=50051
+
+# --- [Strategy 1] HuggingFace Config ---
+VECTORIZER="huggingface"
+HF_MODEL_NAME="sentence-transformers/all-MiniLM-L6-v2"
+
+# (OPENAI_API_KEY is not required for this mode)
+OPENAI_API_KEY=sk-...
 
-Create a `.env` file in the root directory of your project (e.g., where `main.py` is located) and set the required values.
+# --- [Advanced] Custom Properties ---
+CUSTOM_PROPERTIES_FILE_PATH=.weaviate_properties
+RUN_ID=test-run-001
+```
 
-### .env File Example
+#### Example 2: Using `openai_client` (Python Client, High-Performance)
+
+Directly calls the OpenAI API via the `openai` Python library.
 
 ```ini
-# .env
-# --- Basic Weaviate Connection Settings ---
+# .env (Using OpenAI Python Client)
+# --- Basic Weaviate Connection ---
 WEAVIATE_HOST=localhost
 WEAVIATE_PORT=8080
 WEAVIATE_GRPC_PORT=50051
 
-# --- Vectorizer , Generative Module Config ---
-# (default: text2vec-openai) Set to 'none' to disable vectorization.
-VECTORIZER_CONFIG=text2vec-openai
-# (default: generative-openai)
-GENERATIVE_CONFIG=generative-openai
-# An OpenAI API key is required if using modules like text2vec-openai.
-# OPENAI_API_KEY=sk-your-key-here
+# --- [Strategy 2] OpenAI Client Config ---
+VECTORIZER="openai_client"
+
+# [Required] You must enter a valid OpenAI API key.
+OPENAI_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
-# --- [Advanced] Custom Property Settings ---
-# 1. The path to the JSON file defining custom properties to add to the schema.
+# (HF_MODEL_NAME is not used in this mode)
+HF_MODEL_NAME=...
+
+# --- [Advanced] Custom Properties ---
 CUSTOM_PROPERTIES_FILE_PATH=.weaviate_properties
+RUN_ID=test-run-001
+```
+
+#### Example 3: Using `weaviate_module` (Docker Delegate)
 
-# 2. Environment variables to be used for 'Global Dynamic Tagging'.
-#    ("run_id" must be defined in the .weaviate_properties file)
+Delegates vectorization to the Weaviate Docker container instead of Python. (See `vw_docker.yml` config).
+
+```ini
+# .env (Delegating to Weaviate Module)
+# --- Basic Weaviate Connection ---
+WEAVIATE_HOST=localhost
+WEAVIATE_PORT=8080
+WEAVIATE_GRPC_PORT=50051
+
+# --- [Strategy 3] Weaviate Module Config ---
+VECTORIZER="weaviate_module"
+WEAVIATE_VECTORIZER_MODULE=text2vec-openai
+WEAVIATE_GENERATIVE_MODULE=generative-openai
+
+# [Required] The Weaviate container will read this API key.
+OPENAI_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+# --- [Advanced] Custom Properties ---
+CUSTOM_PROPERTIES_FILE_PATH=.weaviate_properties
 RUN_ID=test-run-001
-EXPERIMENT_ID=exp-abc
 ```
 
 -----
 
 ### Custom Properties and Dynamic Execution Tagging
 
-VectorWave can store user-defined metadata in both static definitions (`VectorWaveFunctions`) and dynamic logs (`VectorWaveExecutions`). This works in two steps.
+VectorWave can store user-defined metadata in addition to static data (function definitions) and dynamic data (execution logs). This works in two steps.
 
-#### Step 1: Define Custom Schema (The "Allow-List")
+#### Step 1: Define Custom Schema (Tag "Allow-list")
 
-Create a JSON file at the path specified by `CUSTOM_PROPERTIES_FILE_PATH` (default: `.weaviate_properties`).
+Create a JSON file at the path specified by `CUSTOM_PROPERTIES_FILE_PATH` in your `.env` file (default: `.weaviate_properties`).
 
 This file instructs VectorWave to add **new properties (columns)** to the Weaviate collections. This file acts as an **"allow-list"** for all custom tags.
 
@@ -233,17 +294,17 @@ This file instructs VectorWave to add **new properties (columns)** to the Weavia
 }
 ```
 
-* Defining these will add `run_id`, `experiment_id`, `team`, and `priority` properties to *both* collections.
+* This definition will add `run_id`, `experiment_id`, `team`, and `priority` properties to both the `VectorWaveFunctions` and `VectorWaveExecutions` collections.
 
 #### Step 2: Dynamic Execution Tagging (Adding Values)
 
-When a function executes, VectorWave adds tags to the `VectorWaveExecutions` log. It does this in two ways, which are then merged:
+When a function is executed, VectorWave adds tags to the `VectorWaveExecutions` log. These tags are collected and merged from two sources.
 
-**1. Global Tags (from Environment Variables)**
-VectorWave searches for environment variables whose names match the **uppercase** keys from Step 1 (e.g., `RUN_ID`, `EXPERIMENT_ID`) and uses these for run-wide metadata.
+**1. Global Tags (Environment Variables)**
+VectorWave looks for environment variables matching the **UPPERCASE name** of the keys defined in Step 1 (e.g., `RUN_ID`, `EXPERIMENT_ID`). Found values are loaded as `global_custom_values` and added to *all* execution logs. Ideal for run-wide metadata.
 
-**2. Function-Specific Tags (from Decorator)**
-You can pass tags directly to the `@vectorize` decorator as keyword arguments (`**execution_tags`). This is ideal for function-specific metadata.
+**2. Function-Specific Tags (Decorator)**
+You can pass tags as keyword arguments (`**execution_tags`) directly to the `@vectorize` decorator. Ideal for function-specific metadata.
 
 ```python
 # --- .env file ---
@@ -251,7 +312,7 @@ You can pass tags directly to the `@vectorize` decorator as keyword arguments (`
 # TEAM=default-team
 
 @vectorize(
-    search_description="Process a payment",
+    search_description="Process payment",
     sequence_narrative="...",
     team="billing",  # <-- Function-specific tag
     priority=1       # <-- Function-specific tag
@@ -270,14 +331,14 @@ def other_function():
 
 **Tag Merging and Validation Rules**
 
-1.  **Validation (Most Important):** A tag (either global or specific) will **only** be saved to Weaviate if its key (e.g., `run_id`, `team`, `priority`) was first defined in your `.weaviate_properties` file (Step 1). Tags not defined in the schema will be **ignored**, and a warning will be printed on startup.
+1.  **Validation (Important):** Tags (global or function-specific) will **only** be saved to Weaviate if their key (e.g., `run_id`, `team`, `priority`) was first defined in the `.weaviate_properties` file (Step 1). Tags not defined in the schema are **ignored**, and a warning is printed at script startup.
 
-2.  **Priority (Override):** If a tag key is defined in both places (e.g., a global `RUN_ID` in `.env` and a specific `run_id="override-run-xyz"` on the decorator), the **function-specific tag from the decorator will always win**.
+2.  **Priority (Override):** If a tag key is defined in both places (e.g., global `RUN_ID` in `.env` and `run_id="override-xyz"` in the decorator), the **function-specific tag from the decorator always wins**.
 
 **Resulting Logs:**
 
-* `process_payment()` log will have: `{"run_id": "global-run-abc", "team": "billing", "priority": 1}`
-* `other_function()` log will have: `{"run_id": "override-run-xyz", "team": "default-team"}`
+* `process_payment()` execution log: `{"run_id": "global-run-abc", "team": "billing", "priority": 1}`
+* `other_function()` execution log: `{"run_id": "override-run-xyz", "team": "default-team"}`
 
 -----
 

{vectorwave-0.1.2 → vectorwave-0.1.3}/Readme.md

@@ -139,51 +139,112 @@ for i, span in enumerate(trace_spans):
 # - [Span 2] step_2_send_receipt (202.06ms)
 # - [Span 3] process_payment (333.18ms)
 ```
-
 -----
 
 ## ⚙️ Configuration
 
-VectorWave automatically reads Weaviate database connection information from **environment variables** or a `.env` file.
+VectorWave automatically reads Weaviate database connection info and **vectorization strategy** from **environment variables** or a `.env` file.
+
+Create a `.env` file in your project's root directory (e.g., where `test_ex/example.py` is located) and set the required values.
+
+### Vectorizer Strategy (VECTORIZER)
+
+You can select the text vectorization method via the `VECTORIZER` environment variable in your `test_ex/.env` file.
+
+| `VECTORIZER` Setting | Description | Required Additional Settings |
+| :--- | :--- | :--- |
+| **`huggingface`** | (Default Recommended) Uses the `sentence-transformers` library to vectorize on your local CPU. No API key is needed, making it great for immediate testing. | `HF_MODEL_NAME` (e.g., "sentence-transformers/all-MiniLM-L6-v2") |
+| **`openai_client`** | (High-Performance) Uses the OpenAI Python client to vectorize with modern models like `text-embedding-3-small`. | `OPENAI_API_KEY` (A valid OpenAI API key) |
+| **`weaviate_module`** | (Docker Delegate) Delegates the vectorization task to the Weaviate container's built-in module (e.g., `text2vec-openai`). | `WEAVIATE_VECTORIZER_MODULE`, `OPENAI_API_KEY` |
+| **`none`** | Disables vectorization. Data will be stored without vectors. | None |
+
+-----
+
+### .env File Examples
+
+Configure your `.env` file according to the strategy you want to use.
+
+#### Example 1: Using `huggingface` (Local, No API Key)
+
+Uses a `sentence-transformers` model on your local machine. Ideal for testing without API keys.
+
+```ini
+# .env (Using HuggingFace)
+# --- Basic Weaviate Connection ---
+WEAVIATE_HOST=localhost
+WEAVIATE_PORT=8080
+WEAVIATE_GRPC_PORT=50051
+
+# --- [Strategy 1] HuggingFace Config ---
+VECTORIZER="huggingface"
+HF_MODEL_NAME="sentence-transformers/all-MiniLM-L6-v2"
+
+# (OPENAI_API_KEY is not required for this mode)
+OPENAI_API_KEY=sk-...
 
-Create a `.env` file in the root directory of your project (e.g., where `main.py` is located) and set the required values.
+# --- [Advanced] Custom Properties ---
+CUSTOM_PROPERTIES_FILE_PATH=.weaviate_properties
+RUN_ID=test-run-001
+```
 
-### .env File Example
+#### Example 2: Using `openai_client` (Python Client, High-Performance)
+
+Directly calls the OpenAI API via the `openai` Python library.
 
 ```ini
-# .env
-# --- Basic Weaviate Connection Settings ---
+# .env (Using OpenAI Python Client)
+# --- Basic Weaviate Connection ---
 WEAVIATE_HOST=localhost
 WEAVIATE_PORT=8080
 WEAVIATE_GRPC_PORT=50051
 
-# --- Vectorizer , Generative Module Config ---
-# (default: text2vec-openai) Set to 'none' to disable vectorization.
-VECTORIZER_CONFIG=text2vec-openai
-# (default: generative-openai)
-GENERATIVE_CONFIG=generative-openai
-# An OpenAI API key is required if using modules like text2vec-openai.
-# OPENAI_API_KEY=sk-your-key-here
+# --- [Strategy 2] OpenAI Client Config ---
+VECTORIZER="openai_client"
+
+# [Required] You must enter a valid OpenAI API key.
+OPENAI_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
-# --- [Advanced] Custom Property Settings ---
-# 1. The path to the JSON file defining custom properties to add to the schema.
+# (HF_MODEL_NAME is not used in this mode)
+HF_MODEL_NAME=...
+
+# --- [Advanced] Custom Properties ---
 CUSTOM_PROPERTIES_FILE_PATH=.weaviate_properties
+RUN_ID=test-run-001
+```
+
+#### Example 3: Using `weaviate_module` (Docker Delegate)
 
-# 2. Environment variables to be used for 'Global Dynamic Tagging'.
-#    ("run_id" must be defined in the .weaviate_properties file)
+Delegates vectorization to the Weaviate Docker container instead of Python. (See `vw_docker.yml` config).
+
+```ini
+# .env (Delegating to Weaviate Module)
+# --- Basic Weaviate Connection ---
+WEAVIATE_HOST=localhost
+WEAVIATE_PORT=8080
+WEAVIATE_GRPC_PORT=50051
+
+# --- [Strategy 3] Weaviate Module Config ---
+VECTORIZER="weaviate_module"
+WEAVIATE_VECTORIZER_MODULE=text2vec-openai
+WEAVIATE_GENERATIVE_MODULE=generative-openai
+
+# [Required] The Weaviate container will read this API key.
+OPENAI_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+# --- [Advanced] Custom Properties ---
+CUSTOM_PROPERTIES_FILE_PATH=.weaviate_properties
 RUN_ID=test-run-001
-EXPERIMENT_ID=exp-abc
 ```
 
 -----
 
 ### Custom Properties and Dynamic Execution Tagging
 
-VectorWave can store user-defined metadata in both static definitions (`VectorWaveFunctions`) and dynamic logs (`VectorWaveExecutions`). This works in two steps.
+VectorWave can store user-defined metadata in addition to static data (function definitions) and dynamic data (execution logs). This works in two steps.
 
-#### Step 1: Define Custom Schema (The "Allow-List")
+#### Step 1: Define Custom Schema (Tag "Allow-list")
 
-Create a JSON file at the path specified by `CUSTOM_PROPERTIES_FILE_PATH` (default: `.weaviate_properties`).
+Create a JSON file at the path specified by `CUSTOM_PROPERTIES_FILE_PATH` in your `.env` file (default: `.weaviate_properties`).
 
 This file instructs VectorWave to add **new properties (columns)** to the Weaviate collections. This file acts as an **"allow-list"** for all custom tags.
 
@@ -210,17 +271,17 @@ This file instructs VectorWave to add **new properties (columns)** to the Weavia
 }
 ```
 
-* Defining these will add `run_id`, `experiment_id`, `team`, and `priority` properties to *both* collections.
+* This definition will add `run_id`, `experiment_id`, `team`, and `priority` properties to both the `VectorWaveFunctions` and `VectorWaveExecutions` collections.
 
 #### Step 2: Dynamic Execution Tagging (Adding Values)
 
-When a function executes, VectorWave adds tags to the `VectorWaveExecutions` log. It does this in two ways, which are then merged:
+When a function is executed, VectorWave adds tags to the `VectorWaveExecutions` log. These tags are collected and merged from two sources.
 
-**1. Global Tags (from Environment Variables)**
-VectorWave searches for environment variables whose names match the **uppercase** keys from Step 1 (e.g., `RUN_ID`, `EXPERIMENT_ID`) and uses these for run-wide metadata.
+**1. Global Tags (Environment Variables)**
+VectorWave looks for environment variables matching the **UPPERCASE name** of the keys defined in Step 1 (e.g., `RUN_ID`, `EXPERIMENT_ID`). Found values are loaded as `global_custom_values` and added to *all* execution logs. Ideal for run-wide metadata.
 
-**2. Function-Specific Tags (from Decorator)**
-You can pass tags directly to the `@vectorize` decorator as keyword arguments (`**execution_tags`). This is ideal for function-specific metadata.
+**2. Function-Specific Tags (Decorator)**
+You can pass tags as keyword arguments (`**execution_tags`) directly to the `@vectorize` decorator. Ideal for function-specific metadata.
 
 ```python
 # --- .env file ---
@@ -228,7 +289,7 @@ You can pass tags directly to the `@vectorize` decorator as keyword arguments (`
 # TEAM=default-team
 
 @vectorize(
-    search_description="Process a payment",
+    search_description="Process payment",
     sequence_narrative="...",
     team="billing",  # <-- Function-specific tag
     priority=1       # <-- Function-specific tag
@@ -247,14 +308,14 @@ def other_function():
 
 **Tag Merging and Validation Rules**
 
-1.  **Validation (Most Important):** A tag (either global or specific) will **only** be saved to Weaviate if its key (e.g., `run_id`, `team`, `priority`) was first defined in your `.weaviate_properties` file (Step 1). Tags not defined in the schema will be **ignored**, and a warning will be printed on startup.
+1.  **Validation (Important):** Tags (global or function-specific) will **only** be saved to Weaviate if their key (e.g., `run_id`, `team`, `priority`) was first defined in the `.weaviate_properties` file (Step 1). Tags not defined in the schema are **ignored**, and a warning is printed at script startup.
 
-2.  **Priority (Override):** If a tag key is defined in both places (e.g., a global `RUN_ID` in `.env` and a specific `run_id="override-run-xyz"` on the decorator), the **function-specific tag from the decorator will always win**.
+2.  **Priority (Override):** If a tag key is defined in both places (e.g., global `RUN_ID` in `.env` and `run_id="override-xyz"` in the decorator), the **function-specific tag from the decorator always wins**.
 
 **Resulting Logs:**
 
-* `process_payment()` log will have: `{"run_id": "global-run-abc", "team": "billing", "priority": 1}`
-* `other_function()` log will have: `{"run_id": "override-run-xyz", "team": "default-team"}`
+* `process_payment()` execution log: `{"run_id": "global-run-abc", "team": "billing", "priority": 1}`
+* `other_function()` execution log: `{"run_id": "override-run-xyz", "team": "default-team"}`
 
 -----
 

{vectorwave-0.1.2 → vectorwave-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "vectorwave"
-version = "0.1.2"
+version = "0.1.3"
 authors = [
     { name = "junyeonggim", email = "junyeonggim5@gmail.com" },
 ]
@@ -14,10 +14,10 @@ requires-python = ">=3.10"
 license = "MIT"
 classifiers = [
     "Programming Language :: Python :: 3",
-    "Programming Language :: Python :: 3.10",  # ← 추가
-    "Programming Language :: Python :: 3.11",  # ← 추가
-    "Programming Language :: Python :: 3.12",  # ← 추가
-    "Programming Language :: Python :: 3.13",  # ← 추가
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
     "Operating System :: OS Independent",
     "Development Status :: 3 - Alpha",
     "Intended Audience :: Developers",

{vectorwave-0.1.2 → vectorwave-0.1.3}/src/tests/batch/test_batch.py

@@ -93,5 +93,6 @@ def test_add_object_calls_client_batch(mock_deps):
 
     mock_deps["client"].collections.get.return_value.data.insert.assert_called_once_with(
         properties=props,
-        uuid="test-uuid"
+        uuid="test-uuid",
+        vector=None
 )

{vectorwave-0.1.2 → vectorwave-0.1.3}/src/tests/database/test_db.py

@@ -392,16 +392,12 @@ def test_create_schema_vectorizer_openai(test_settings):
     mock_collections.exists.return_value = False
     mock_client.collections = mock_collections
 
-    test_settings.VECTORIZER_CONFIG = "text2vec-openai"
-    test_settings.GENERATIVE_CONFIG = "generative-openai"
+    test_settings.VECTORIZER = "weaviate_module"
+    test_settings.WEAVIATE_VECTORIZER_MODULE = "text2vec-openai"
+
+    # [수정] test_settings.GENERATIVE_CONFIG = "generative-openai" ->
+    test_settings.WEAVIATE_GENERATIVE_MODULE = "generative-openai"
 
-    expected_vector_config = {
-        "vectorizer": "text2vec-openai",
-        "text2vec-openai": {
-            "vectorizeClassName": test_settings.IS_VECTORIZE_COLLECTION_NAME,
-        }
-    }
-    expected_generative_config = {"generator": "generative-openai"}
 
     # 2. Act
     create_vectorwave_schema(mock_client, test_settings)
@@ -411,9 +407,16 @@ def test_create_schema_vectorizer_openai(test_settings):
 
     call_args = mock_collections.create.call_args
 
+    vector_config_arg = call_args.kwargs.get('vector_config')
+    # assert isinstance(vector_config_arg, wvc.Configure.Vectorizer)
+    # assert vector_config_arg.name == "text2vec-openai"
+
+    assert vector_config_arg.vectorizer == "text2vec-openai"
+
+    # 3b. Generative Config 검증
+    generative_config_arg = call_args.kwargs.get('generative_config')
+    assert generative_config_arg.generative == "generative-openai"
 
-    assert call_args.kwargs.get('vector_config') == expected_vector_config
-    assert call_args.kwargs.get('generative_config') == expected_generative_config
 
 
 
@@ -427,9 +430,8 @@ def test_create_schema_vectorizer_none(test_settings):
     mock_collections.exists.return_value = False
     mock_client.collections = mock_collections
 
-    test_settings.VECTORIZER_CONFIG = "none"
-
-    expected_vector_config = {"vectorizer": "none"}
+    test_settings.VECTORIZER = "none"
+    test_settings.WEAVIATE_VECTORIZER_MODULE = ""
 
     # 2. Act
     create_vectorwave_schema(mock_client, test_settings)
@@ -440,7 +442,10 @@ def test_create_schema_vectorizer_none(test_settings):
     call_args = mock_collections.create.call_args
     # mock_none.assert_called_once() -> 삭제
 
-    assert call_args.kwargs.get('vector_config') == expected_vector_config
+    vector_config_arg = call_args.kwargs.get('vector_config')
+
+
+    assert vector_config_arg.vectorizer == "none"
 
 
 def test_create_schema_vectorizer_invalid(test_settings):
@@ -453,12 +458,11 @@ def test_create_schema_vectorizer_invalid(test_settings):
     mock_collections.exists.return_value = False
     mock_client.collections = mock_collections
 
-    test_settings.VECTORIZER_CONFIG = "unsupported-module"
+    test_settings.VECTORIZER = "unsupported-module"
 
     # 2. Act & 3. Assert
     with pytest.raises(SchemaCreationError) as exc_info:
         create_vectorwave_schema(mock_client, test_settings)
 
-    assert "Unsupported VECTORIZER_CONFIG" in str(exc_info.value)
-    assert "'text2vec-openai', 'none'" in str(exc_info.value)
-    assert "text2vec-huggingface" not in str(exc_info.value)
+    assert "Invalid VECTORIZER setting" in str(exc_info.value)
+    assert "unsupported-module" in str(exc_info.value)

{vectorwave-0.1.2 → vectorwave-0.1.3}/src/tests/models/test_db_config.py

@@ -60,13 +60,16 @@ def test_get_settings_loads_custom_props_success(mock_open_file, mock_exists):
 
 
 @patch('os.path.exists', return_value=False)
-def test_get_settings_file_not_found(mock_exists, capsys):
+def test_get_settings_file_not_found(mock_exists, caplog):
     """
     Case 2: .weaviate_properties file does not exist
     - settings.custom_properties should be None
-    - A 'file not found' note should be printed
+    - A 'file not found' message should be logged at DEBUG level
     """
+    import logging
+
     # Arrange
+    caplog.set_level(logging.DEBUG)  # DEBUG 레벨로 설정 (중요!)
     get_weaviate_settings.cache_clear()
 
     # Act
@@ -76,21 +79,23 @@ def test_get_settings_file_not_found(mock_exists, capsys):
     mock_exists.assert_called_with(".weaviate_properties")
     assert settings.custom_properties is None
 
-    # Check if 'file not found' note was printed
-    captured = capsys.readouterr()
-    assert "file not found" in captured.out
+    # Check if 'file not found' message was logged
+    assert "file not found" in caplog.text.lower() or "not found" in caplog.text
 
 
 @patch('os.path.exists', return_value=True)
 @patch('builtins.open', new_callable=mock_open, read_data=MOCK_INVALID_JSON)
 @patch('json.load', side_effect=JSONDecodeError("Mock JSON Decode Error", "", 0))
-def test_get_settings_invalid_json(mock_json_load, mock_open_file, mock_exists, capsys):
+def test_get_settings_invalid_json(mock_json_load, mock_open_file, mock_exists, caplog):
     """
     Case 3: File exists but JSON format is invalid
     - settings.custom_properties should be None
-    - A 'Could not parse JSON' warning should be printed
+    - A 'Could not parse JSON' warning should be logged
     """
+    import logging
+
     # Arrange
+    caplog.set_level(logging.WARNING)
     get_weaviate_settings.cache_clear()
 
     # Act
@@ -99,12 +104,16 @@ def test_get_settings_invalid_json(mock_json_load, mock_open_file, mock_exists,
     # Assert
     mock_exists.assert_called_once()
     mock_open_file.assert_called_once()
-    mock_json_load.assert_called_once() # json.load was called but failed (due to side_effect)
-    assert settings.custom_properties is None # Should be None due to parsing failure
+    mock_json_load.assert_called_once()  # json.load was called but failed (due to side_effect)
+    assert settings.custom_properties is None  # Should be None due to parsing failure
+
+    # Check if 'Could not parse JSON' warning was logged
+    assert "Could not parse JSON" in caplog.text
 
-    # Check if 'Could not parse JSON' warning was printed
-    captured = capsys.readouterr()
-    assert "Could not parse JSON" in captured.out
+    # Also check the log level
+    warning_logs = [r for r in caplog.records if "parse JSON" in r.message]
+    assert len(warning_logs) > 0
+    assert warning_logs[0].levelname == "WARNING"
 
 @patch('os.path.exists', return_value=True)
 @patch('builtins.open', new_callable=mock_open, read_data=MOCK_JSON_DATA)