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
From here, the indices array in pinecone-text is a 32-bit unsigned integer. However, the sparse vectors in the official pinecone connector (see the README here) are expected to be Spark IntegerType. Spark's integers are 32-bit signed. That means that pinecone-text produces indices which overflow Spark's integer type and therefore are incompatible with the pinecone spark connector. I've verified this.
Any ideas on what to do here? A solution might be for spark-pinecone to change that schema from IntegerType to LongType, but since these are both official Pinecone projects figured y'all might have better success getting that change made.
The text was updated successfully, but these errors were encountered:
Looks like the murmurhash function used here has a flag for signed / unsigned. I had thought that a potential solution would be to make that a configurable flag here, but it appears that pinecone itself really is expecting an unsigned integer:
HTTP response body: vectors[0].sparse_values.indices[5]: invalid value -74040069 for type TYPE_UINT32
So looks like the solution has to be a fix on the spark-pinecone side to change from IntegerType to LongType.
From here, the indices array in pinecone-text is a 32-bit unsigned integer. However, the sparse vectors in the official pinecone connector (see the README here) are expected to be Spark
IntegerType
. Spark's integers are 32-bit signed. That means that pinecone-text produces indices which overflow Spark's integer type and therefore are incompatible with the pinecone spark connector. I've verified this.Any ideas on what to do here? A solution might be for spark-pinecone to change that schema from IntegerType to LongType, but since these are both official Pinecone projects figured y'all might have better success getting that change made.
The text was updated successfully, but these errors were encountered: