cc. @shuchu
I am developing and contributing feast go feature server in this PR(#5336). I succeed in building and running go feature server. But when applying go feature server with redis as online store, the feature value inconsistency occurs.

Expected Behavior

ensure consistency of feature value

Current Behavior

inconsistency of feature value.
I attached two screenshot. Entity, feature view, feature name is all the same but per each request, retrieved feature value is null or not null. What is the cause of this circumstance?

Steps to reproduce

1. apply feast register and materialize to online store
2. feast go feature server retrieved from online store(redis)
3. The result changes every time I run it.

Specifications

At present, I run feast server on EKS cluster and run as deployment including five pods.

• Version: go feature server is alpha, so I develop locally. follow this PR(feat: Add s3 storage-based registry store in Go feature server #5336)
• Platform: arm64, linux debian
• Subsystem:

Possible Solution

I don't know what to do anything yet.