# Successfully Added Data to Weaviate but Facing Retrieval Issue
**URL:** https://forum.weaviate.io/t/successfully-added-data-to-weaviate-but-facing-retrieval-issue/2937
**Category:** Support
**Tags:** bug, developer-experience, python
**Created:** [July 4, 2024, 12:47pm UTC](https://forum.weaviate.io/t/successfully-added-data-to-weaviate-but-facing-retrieval-issue/2937 "2024-07-04T12:47:57Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Freddy](https://forum.weaviate.io/u/Freddy)
#### Post date: [July 4, 2024, 12:47pm UTC](https://forum.weaviate.io/t/successfully-added-data-to-weaviate-but-facing-retrieval-issue/2937/1 "2024-07-04T12:47:57Z")
Hello Community,
I wanted to share a recent experience with Weaviate, and seek some advice or suggestions on an issue I encountered. I successfully added the following data to Weaviate:
```auto
{
"class": "SearchProduct_3",
"creationTimeUnix": 1720096787175,
"id": "a-a-a-a-a,
"lastUpdateTimeUnix": 1720096787175,
"properties": {
"description": "A percentage-based merchant charge of 2.9% per transaction. Suitable for businesses with varying transaction amounts.",
"keywords": "merchant,percentage,transaction fee,business,2.9%",
"row_data": {
"charge_id": "a-a-a-a-a",
"charge_name": "merchant charges",
"charge_per_unit": 2.9,
"charge_type": "percent",
"is_active": true,
"is_deleted": false
},
"title": "Percentage-Based Merchant Charges"
},
"vectorWeights": null
}
```
The data was successfully added without any issues. However, when I attempted to retrieve the data, I encountered the following error related to the `row_data` key:
```auto
"errors": [
{
"locations": [
{
"column": 122,
"line": 1
}
],
"message": "Field \"row_data\" of type \"SearchProduct_3_row_data_object\" must have a sub selection.",
"path": null
}
]
```
### Request for Suggestions:
- Has anyone encountered a similar issue with nested fields in Weaviate?
- Any advice on how to resolve this error or configure the sub-selection for `row_data`?
Looking forward to any insights or suggestions from the community!
Thanks in advance! ๐
@DudaNogueira
---
### Author:  [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [July 4, 2024, 9:05pm UTC](https://forum.weaviate.io/t/successfully-added-data-to-weaviate-but-facing-retrieval-issue/2937/2 "2024-07-04T21:05:46Z")
Hi @Freddy !
What is the server version?
Can you share the query?
If you are trying to filter by nested object, this is not possible as of now:
> **[Data types | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/config-refs/datatypes#datatype-object)**
>
> \- Configuration: Schema
Let me know if this helps.
Thanks!
---
### Author:  [@Freddy](https://forum.weaviate.io/u/Freddy)
#### Post date: [July 5, 2024, 6:25am UTC](https://forum.weaviate.io/t/successfully-added-data-to-weaviate-but-facing-retrieval-issue/2937/3 "2024-07-05T06:25:37Z")
Version is : 1.23.6
Query is :
```auto
(
self.client.query.get(class_name, properties=['title', 'description', 'row_data', 'keywords'])
.with_hybrid(
query="get me charge data",
alpha=0.6,
fusion_type=HybridFusion.RANKED,
)
).do()
```
---
### Author:  [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [July 5, 2024, 7:47pm UTC](https://forum.weaviate.io/t/successfully-added-data-to-weaviate-but-facing-retrieval-issue/2937/4 "2024-07-05T19:47:51Z")
Oh, I see. You have a problem on hybrid search with nested . ๐
Note that filtering on nested objects are yet supported โน
Check here the note when this feature was released:
> **[Weaviate 1.22 Release | Weaviate - Vector Database](https://weaviate.io/blog/weaviate-1-22-release#future-improvements)**
>
> Weaviate 1.22 released with nest object storage, async indexing, further gRPC support, and more!
There is a feature request around this in [our roadmap](https://weaviate.io/developers/weaviate/roadmap):
>
>
> \#2424 introduced storing of nested objects. The next step is to make filtering (โฆand vectorization for modules) available for them.
Please, leave your ๐ on that issue so we can keep it high on priority!
I was able to partially reproduce this issue.
Check the following code, running on
```python
print(weaviate. __version__ , client.get_meta().get("version"))
>>> client: 4.6.5, server:1.25.6
```
this is basically the same query but using python v4 client. And it raise the same error you have:
```python
client.collections.delete("Nested")
collection = client.collections.get("Nested")
collection.data.insert({"parent": {"child": "hello nested world"}})
results = collection.query.hybrid(query="get me charge data", alpha=0.6, fusion_type=wvc.query.HybridFusion.RANKED)
```
However, this will work
```python
client.collections.delete("Nested")
collection = client.collections.get("Nested")
collection.data.insert({"parent": {"child": "hello nested world"}, "other": "text"})
results = collection.query.hybrid(query="get me charge data", alpha=0.6, fusion_type=wvc.query.HybridFusion.RANKED)
```
Note the โotherโ property.
Now, considering that the nested object is not indexable, can you make sure you have other content on your collection other than the nested obhect?
Let me know if this helps.
Thanks!