cc. @franciscojavierarceo
These days, I try to contributing Go feature server in this repository.(e.g recent PR(#5352) that I made)
At present, I use Go feature server(alpha) and apply it on my production environment. My feast environment is below.

• registry: aws s3 storage(in my fix: Reopen for integration test about add s3 storage-based registry store in Go feature server #5352 , I locally succeed in integrating with s3 storage)
• offline store: spark + s3
• online store: aws elasticache valkey(like redis)

But when using Go feature server with redis, I encountered the bug in building redis hash key.

At first, I define my entities, feature views and register them. At this time, one of my entities has int32 type. This int32 type is supported according to feast docs.
After that, I finish materializing features from offline store to online store and run Go feature server. Finally, client application request to go feature server.

But, I check that a specific feature is materialized well but from go feature server, the feature value is null. So instead of go feature server, I tried to fetch the feature with feast python sdk. When using feast python sdk, the feature value is not null. So I confused at this circumstance.

So, I deeply dive about this bug. I found that the features from other entity that has string type is not null from go feature server. So I paid attention to the entity that has int32 type.

I have two feast environments(dev, prod). At present, the prod environment is in the problem. So in dev environment, I intentionally cast the type of entity from int32 to string and re-register, materialize it.
After that, when I fetch the feature from go feature server in dev, I surprised that the feature value is not null!

So, I guess that the cause of this issue is maybe in this source code in go feature server. the probelm is in making hashkey for fetching(HMGet) to redis. Because, in the dev environment, hashkey by made from go feature server source code can be found in the redis. I check it by redis cli or redis insight GUI tool. But in the prod environment, the hashkey from go feature server was not in redis.

• abnormal case(prod)

I build and run go feature server by debug mode and evaluate the redisKeys variable. I copy the data from redisKeys variable, and try to find the key in redis but there is no hashkey in redis.

So, I want to fix this bug.. Can you advise to me? I mention @shuchu based on the commit history about integrating redis as online store in go feature server.

Expected Behavior

In the same feature, the fetched feature from feast-sdk and go feature server is the same.

Current Behavior

In the same feature, the fetched feature from feast-sdk is normal but feature from go feature server is null.

Steps to reproduce

Specifications

• Version: locally development but the problematic source code is the same as in the master branch.
• Platform: MacOS 64bit arm64 OS platform
• Subsystem:

Possible Solution

What is the potential cause of this bug?