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
I'm running into a problem when using case class to describe documents.
If for one document a text field value is an empty string (""), the document can be stored by Solr but the specific field will not be. Then at query time, the SolrClient seems unable to rebuild the document when I try to getResultsAs[MyCaseClass](...)
It seems to work with Option[String] (with Some("") becoming None though)
The text was updated successfully, but these errors were encountered:
@a-tsioh As long as I tested, Solr (or SolrJ) doesn't allow an empty string for a required string field while we can specify an empty string for optional string fields though these fields are not stored in the document.
Meanwhile, if a field doesn't exist in a document on Solr, solr-scala-client handles it as null. Then it's converted to null for String field or None for Option[String] field. This is an intentional behavior in solr-scala-client end.
I guess the field you tried to store an empty string is optional. Then you should use Option[String] and use None instead of an empty string even when you store documents.
Thank you for this useful work !
I'm running into a problem when using case class to describe documents.
If for one document a text field value is an empty string (""), the document can be stored by Solr but the specific field will not be. Then at query time, the SolrClient seems unable to rebuild the document when I try to
getResultsAs[MyCaseClass](...)
It seems to work with Option[String] (with Some("") becoming None though)
The text was updated successfully, but these errors were encountered: