[ https://issues.apache.org/jira/browse/IGNITE-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106165#comment-17106165 ]
Igor Sapego commented on IGNITE-12975: -------------------------------------- Looks good, but need a test that will show that problem solved and prevent regression. > pyignte sql query should not try to create a cache > -------------------------------------------------- > > Key: IGNITE-12975 > URL: https://issues.apache.org/jira/browse/IGNITE-12975 > Project: Ignite > Issue Type: Bug > Components: python > Affects Versions: 2.7.6 > Reporter: Isaac Zhu > Assignee: Igor Sapego > Priority: Major > Attachments: IGNITE-12975_Fix_cache_obtaining_method.patch > > > I find in this line: > [https://github.com/apache/ignite/blob/master/modules/platforms/python/pyignite/client.py#L395] > When doing an SQL query through the pyignite thin client, it is trying to get > the cache by calling "get_or_create_cache". This caused my ignite instance > returns an "Authorization error" because I was using an account that only can > read cache and does not have permission to create a cache - we implemented a > Security Processor in our ignite cluster to handle the authorization. > I think here call the "self.get_cache" is enough to perform a SQL query -- This message was sent by Atlassian Jira (v8.3.4#803005)