{"action":"opened","issue":{"url":"https://api.github.com/repos/debop/hibernate-redis/issues/119","repository_url":"https://api.github.com/repos/debop/hibernate-redis","labels_url":"https://api.github.com/repos/debop/hibernate-redis/issues/119/labels{/name}","comments_url":"https://api.github.com/repos/debop/hibernate-redis/issues/119/comments","events_url":"https://api.github.com/repos/debop/hibernate-redis/issues/119/events","html_url":"https://github.com/debop/hibernate-redis/issues/119","id":318071530,"number":119,"title":"Multitenancy with Spring-Data-JPA","user":{"login":"MurthyKVN","id":31207172,"avatar_url":"https://avatars0.githubusercontent.com/u/31207172?v=4","gravatar_id":"","url":"https://api.github.com/users/MurthyKVN","html_url":"https://github.com/MurthyKVN","followers_url":"https://api.github.com/users/MurthyKVN/followers","following_url":"https://api.github.com/users/MurthyKVN/following{/other_user}","gists_url":"https://api.github.com/users/MurthyKVN/gists{/gist_id}","starred_url":"https://api.github.com/users/MurthyKVN/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MurthyKVN/subscriptions","organizations_url":"https://api.github.com/users/MurthyKVN/orgs","repos_url":"https://api.github.com/users/MurthyKVN/repos","events_url":"https://api.github.com/users/MurthyKVN/events{/privacy}","received_events_url":"https://api.github.com/users/MurthyKVN/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-26T15:05:30Z","updated_at":"2018-04-26T15:05:30Z","closed_at":null,"author_association":"NONE","body":"Hi\r\n\r\nwe are using hibernate-redis-2.4.0 with Hibernate 5.0.12 and Spring-Data-JPA 1.11. We have enabled multitenancy with schema approach. We could see entries in redis server with keys containing tenantId and primary-key of the entity.\r\n\r\nNow, while accessing the application same entity is being loaded for both tenants. We have observed from logs that the tenantId is being resolved properly in both the cases.\r\n\r\nAnybody faced this kind of issue.\r\n\r\nPlease help\r\n\r\n"}}
{"actor":{"display_login":"MurthyKVN"}}