This message was deleted.
# community-help
s
This message was deleted.
k
cc @Harpreet Sangar
h
@Alex Kalyvitis Since we support referencing even object fields that follow
object_name.field_name
convention, we cannot parse the collection name containing
.
correctly. Maybe you can use
_
like
production_users
name or create an alias.
a
Ah okay, thank you so much for the quick help team! 🫶
I gave this a try, and with the alias it works fine, but unfortunately I can’t guarantee the referenced field matches exactly one result:
Copy code
{
  "message": "Multiple documents having `email:= `chuck@chucknorris.com`` found in the collection `users`."
}
I’ve reverted the collection schema since, removing any references (drop/recreate). But on the referenced collection (comments), I am getting errors when indexing. Is there a dangling reference there somehow? I am getting such errors:
Copy code
Field `commenter` not found in the ref schema of `comments` having async_reference to `users` collection.
P.S. I’m using example names for simplicity here
I’d appreciate some guidance on the error, without having to drop the users collection if I can avoid it.
h
I am assuming you did an alter operation to update the schema collection? If so, you'll have to drop the collection having the reference field and index again since we don't support alteration of reference fields right now.
j
Is there an ETA for adding a reference field using the alter operation, thereby not having to recreate a collection? @Harpreet Sangar
h
@John Sokol I think it wouldn't be much work to implement this feature but it definitely won't be part of the v29 GA release. We can prioritize this feature based on the demand. Can you open a Github issue for this feature?
a
Hi Harpreet, sorry for the late response. I’ve dropped the collection with the reference. Would indeed be good to have the option to modify reference fields.
h
It is now possible in the latest RC build https://github.com/typesense/typesense/pull/2445
🙌 1