You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/weaviate/manage-objects/import.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ This means that the feature is still under development and may change in future
91
91
Here's how to import objects into a collection named `MyCollection` using [server-side batch imports](../concepts/data-import.mdx#server-side-batching). The client will send data in batch sizes using feedback from the server.
Copy file name to clipboardExpand all lines: docs/weaviate/search/filters.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -424,15 +424,15 @@ The output is like this:
424
424
The `ContainsNone` operator works on text properties and take an array of values as input. It will match objects where the property **contains none** of the values in the array.
Copy file name to clipboardExpand all lines: docs/weaviate/tutorials/collection-aliases.mdx
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,15 +75,15 @@ Let's walk through a complete migration scenario where we need to add a new fiel
75
75
First, connect to your Weaviate instance using your preferred client library.
76
76
77
77
<TabsgroupId="languages">
78
-
<TabItemvalue="py"label="Python Client v4">
78
+
<TabItemvalue="py"label="Python">
79
79
<FilteredTextBlock
80
80
text={PyCode}
81
81
startMarker="# START ConnectToWeaviate"
82
82
endMarker="# END ConnectToWeaviate"
83
83
language="py"
84
84
/>
85
85
</TabItem>
86
-
<TabItemvalue="js"label="JS/TS Client v3">
86
+
<TabItemvalue="js"label="JS/TS">
87
87
<FilteredTextBlock
88
88
text={TSCode}
89
89
startMarker="// START ConnectToWeaviate"
@@ -114,15 +114,15 @@ First, connect to your Weaviate instance using your preferred client library.
114
114
Let's create our initial products collection and populate it with data.
115
115
116
116
<TabsgroupId="languages">
117
-
<TabItemvalue="py"label="Python Client v4">
117
+
<TabItemvalue="py"label="Python">
118
118
<FilteredTextBlock
119
119
text={PyCode}
120
120
startMarker="# START Step1CreateOriginal"
121
121
endMarker="# END Step1CreateOriginal"
122
122
language="py"
123
123
/>
124
124
</TabItem>
125
-
<TabItemvalue="js"label="JS/TS Client v3">
125
+
<TabItemvalue="js"label="JS/TS">
126
126
<FilteredTextBlock
127
127
text={TSCode}
128
128
startMarker="// START Step1CreateOriginal"
@@ -153,15 +153,15 @@ Let's create our initial products collection and populate it with data.
153
153
Now create an alias that your application will use. This decouples your application code from the specific collection version.
154
154
155
155
<TabsgroupId="languages">
156
-
<TabItemvalue="py"label="Python Client v4">
156
+
<TabItemvalue="py"label="Python">
157
157
<FilteredTextBlock
158
158
text={PyCode}
159
159
startMarker="# START Step2CreateAlias"
160
160
endMarker="# END Step2CreateAlias"
161
161
language="py"
162
162
/>
163
163
</TabItem>
164
-
<TabItemvalue="js"label="JS/TS Client v3">
164
+
<TabItemvalue="js"label="JS/TS">
165
165
<FilteredTextBlock
166
166
text={TSCode}
167
167
startMarker="// START Step2CreateAlias"
@@ -192,15 +192,15 @@ Now create an alias that your application will use. This decouples your applicat
192
192
Your application code should reference the alias, not the underlying collection. This ensures it continues working regardless of which collection version is active.
193
193
194
194
<TabsgroupId="languages">
195
-
<TabItemvalue="py"label="Python Client v4">
195
+
<TabItemvalue="py"label="Python">
196
196
<FilteredTextBlock
197
197
text={PyCode}
198
198
startMarker="# START MigrationUseAlias"
199
199
endMarker="# END MigrationUseAlias"
200
200
language="py"
201
201
/>
202
202
</TabItem>
203
-
<TabItemvalue="js"label="JS/TS Client v3">
203
+
<TabItemvalue="js"label="JS/TS">
204
204
<FilteredTextBlock
205
205
text={TSCode}
206
206
startMarker="// START MigrationUseAlias"
@@ -233,15 +233,15 @@ The key point is that your application code doesn't need to know whether it's ac
233
233
Now let's create a new version of the collection with an additional field (e.g., adding a `category` property).
234
234
235
235
<TabsgroupId="languages">
236
-
<TabItemvalue="py"label="Python Client v4">
236
+
<TabItemvalue="py"label="Python">
237
237
<FilteredTextBlock
238
238
text={PyCode}
239
239
startMarker="# START Step3NewCollection"
240
240
endMarker="# END Step3NewCollection"
241
241
language="py"
242
242
/>
243
243
</TabItem>
244
-
<TabItemvalue="js"label="JS/TS Client v3">
244
+
<TabItemvalue="js"label="JS/TS">
245
245
<FilteredTextBlock
246
246
text={TSCode}
247
247
startMarker="// START Step3NewCollection"
@@ -272,15 +272,15 @@ Now let's create a new version of the collection with an additional field (e.g.,
272
272
Copy data from the old collection to the new one, adding default values for new fields or transforming data as needed.
273
273
274
274
<TabsgroupId="languages">
275
-
<TabItemvalue="py"label="Python Client v4">
275
+
<TabItemvalue="py"label="Python">
276
276
<FilteredTextBlock
277
277
text={PyCode}
278
278
startMarker="# START Step4MigrateData"
279
279
endMarker="# END Step4MigrateData"
280
280
language="py"
281
281
/>
282
282
</TabItem>
283
-
<TabItemvalue="js"label="JS/TS Client v3">
283
+
<TabItemvalue="js"label="JS/TS">
284
284
<FilteredTextBlock
285
285
text={TSCode}
286
286
startMarker="// START Step4MigrateData"
@@ -311,15 +311,15 @@ Copy data from the old collection to the new one, adding default values for new
311
311
This is the magic moment - update the alias to point to the new collection. This switch is instantaneous, and all queries using the `ProductsAlias` alias now access the new collection.
312
312
313
313
<TabsgroupId="languages">
314
-
<TabItemvalue="py"label="Python Client v4">
314
+
<TabItemvalue="py"label="Python">
315
315
<FilteredTextBlock
316
316
text={PyCode}
317
317
startMarker="# START Step5UpdateAlias"
318
318
endMarker="# END Step5UpdateAlias"
319
319
language="py"
320
320
/>
321
321
</TabItem>
322
-
<TabItemvalue="js"label="JS/TS Client v3">
322
+
<TabItemvalue="js"label="JS/TS">
323
323
<FilteredTextBlock
324
324
text={TSCode}
325
325
startMarker="// START Step5UpdateAlias"
@@ -350,15 +350,15 @@ This is the magic moment - update the alias to point to the new collection. This
350
350
After verifying that everything works correctly with the new collection, you can safely delete the old one.
0 commit comments