Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: [json-inverted] Query with json filter gets error: "(segment_->type() == SegmentType::Sealed && num_data_chunk_ == 1) #38749

Open
1 task done
ThreadDao opened this issue Dec 25, 2024 · 0 comments
Assignees
Labels
kind/bug Issues or changes related a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@ThreadDao
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: harbor.milvus.io/milvus/milvus:JsDove-optimization_json-72e0417-20241225
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

server

cluster with dev-image: harbor.milvus.io/milvus/milvus:JsDove-optimization_json-72e0417-20241225

client

  1. create collection with 3 fields: id(int64 & pk) + vector + json
{'collection_name': 'laion_json_1', 'auto_id': False, 'num_shards': 1, 'description': '', 'fields': [{'field_id': 100, 'name': 'id', 'description': '', 'type': <DataType.INT64: 5>, 'params': {}, 'is_primary': True}, {'field_id': 101, 'name': 'float_vector', 'description': '', 'type': <DataType.FLOAT_VECTOR: 101>, 'params': {'dim': 768}}, {'field_id': 102, 'name': 'json_1', 'description': '', 'type': <DataType.JSON: 23>, 'params': {}}], 'aliases': [], 'collection_id': 454845922362524415, 'consistency_level': 2, 'properties': {}, 'num_partitions': 1, 'enable_dynamic_field': False}
  1. create HNSW index for vector fields
  2. insert 10million entities -> flush
  3. create index again -> load
  4. query with expr
  • json brute force:
c.query('json_1["Image YResolution"] == "100"', output_fields=["count(*)"])
data: ["{'count(*)': 13307}"] 
  • json inverted index
pymilvus.exceptions.MilvusException: <MilvusException: (code=65535, message=fail to Query on QueryNode 3: worker(8) query failed: Operator::GetOutput failed for [Operator:PhyFilterBitsNode, plan node id: 221] : Assert "(segment_->type() == SegmentType::Sealed && num_data_chunk_ == 1)"  at /go/src/github.com/milvus-io/milvus/internal/core/src/exec/expression/UnaryExpr.cpp:809

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

pods:

json-inverted-op-97-1369-milvus-datanode-56b8d4b7bf-g8r2k         1/1     Running                  0                6h7m    10.104.15.251   4am-node20   <none>           <none>
json-inverted-op-97-1369-milvus-indexnode-7dd96c757-6d8z8         1/1     Running                  0                6h7m    10.104.14.43    4am-node18   <none>           <none>
json-inverted-op-97-1369-milvus-indexnode-7dd96c757-b9g8z         1/1     Running                  0                6h7m    10.104.13.144   4am-node16   <none>           <none>
json-inverted-op-97-1369-milvus-indexnode-7dd96c757-pdsv4         1/1     Running                  0                6h7m    10.104.15.250   4am-node20   <none>           <none>
json-inverted-op-97-1369-milvus-mixcoord-564c6ffd7c-v8plr         1/1     Running                  0                6h7m    10.104.15.252   4am-node20   <none>           <none>
json-inverted-op-97-1369-milvus-proxy-744995f869-fws7x            1/1     Running                  0                6h7m    10.104.30.218   4am-node38   <none>           <none>
json-inverted-op-97-1369-milvus-querynode-0-f696dfb79-pkg4t       1/1     Running                  0                6h7m    10.104.15.253   4am-node20   <none>           <none>

Anything else?

No response

@ThreadDao ThreadDao added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 25, 2024
@ThreadDao ThreadDao added this to the 2.5.1 milestone Dec 25, 2024
@ThreadDao ThreadDao added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Dec 25, 2024
@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 26, 2024
@yanliang567 yanliang567 removed their assignment Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants