`isInitialized` & `dataStore.isInitialized()` about java-server-sdk HOT 3 CLOSED

You didn't say why it looks like a bug to you, so I don't know whether you're missing something, but here's a summary of what the intention is:

• There are two components with different purposes, the "data store" (which is either a simple in-memory store or a database) and the "data source" (which manages the connection to LaunchDarkly for getting flags).
• LDClient.isInitialized() is intended to return true if the SDK has received flag data from LaunchDarkly at least once so far. That is the job of the data source component, so that's why it is delegating to dataSource.isInitialized().
• Even if the SDK has not received flag data from LaunchDarkly, there could still be old flag data present in the data store— specifically, if the data store is a database. If so, we can use that data to evaluate flags, even though we would prefer to have more up-to-date flag data. That's what is going on in the first block you quoted.

from java-server-sdk.

So, the specific scenarios that that first block is there to handle are:

1. The SDK has not (yet) completed a successful initialization because it has not been able to connect to LaunchDarkly. But, when it calls dataStore.isInitialized(), it returns true, indicating that we are using a database and we detected some flag data already in the database (either from a previous run of the application, or put there by another process such as the Relay Proxy). So, we use that data, and we print a warning ("using last known values from data store").
2. Or, the SDK has not yet completed a successful initialization, and there is not already data in the data store. So we have no data, there is no way to evaluate flags, and we print a different warning ("data store unavailable").

from java-server-sdk.

ok makes sense, I was confused by similar naming [dataS]tore with [dataS]ource, and thought that those both are the same thing.

I'm closing the issue now.

from java-server-sdk.