I'm currently using the json serializer with strings as keys (I originally was using int64 keys when I noticed that all responses were 404s and switched to see if strings would work as they do for BDB stores). I've tried serval different configurations and tried the embedded rest service, but it also returns only 404 responses. I do see that the coordinator service appears to be reading the configuration files correctly, as requests to un-configured stores will return a response indicating such.
<stores>
<store>
<name>siml</name>
<persistence>read-only</persistence>
<routing>client</routing>
<replication-factor>1</replication-factor>
<required-reads>1</required-reads>
<required-writes>1</required-writes>
<key-serializer>
<type>json</type>
<schema-info>"string"</schema-info>
</key-serializer>
<value-serializer>
<type>json</type>
<schema-info>["string"]</schema-info>
</value-serializer>
</store>
</stores>
coordinator.properties:
bootstrap_urls=tcp://localhost:6666
fat_clients_config_file_path=readonly/coordinator/fatclients_config.avro
fatclients_config.avro:
{
"siml": {
"socket_timeout_ms": "1500",
"connection_timeout_ms": "500",
"identifier_string": "siml"
}
}