[IGNITE-6288] NPE on SQL query with parameters on custom schema name

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3
• Component/s: sql
• Assignee: Taras Ledkov
• Reporter: Taras Ledkov
• Created: 07/Sep/17 08:47
• Updated: 11/Sep/17 07:16
• Resolved: 11/Sep/17 07:15

Description

Root cause: cache name is used instead of schema name at the CacheQueryPartitionInfo

Reproducer: please add the short test to the tests class SqlSchemaSelfTest

    public void testCustomSchemaName() throws Exception {
        QueryEntity qe = new QueryEntity()
            .setValueType(Person.class.getName())
            .setKeyType(Long.class.getName())
            .setValueFieldName("_value")
            .setKeyFieldName("id")
            .addQueryField("id", Long.class.getName(), null)
            .addQueryField("_value", Person.class.getName(), null)
            .addQueryField("name", String.class.getName(), null)
            .addQueryField("orgId", Long.class.getName(), null);

        qe.setTableName("Person");

        IgniteCache<Long, Person> cache = node.createCache(new CacheConfiguration<Long, Person>()
            .setName(CACHE_PERSON)
            .setQueryEntities(Collections.singletonList(qe))
            .setSqlSchema("TEST"));

        cache.put(1L, new Person("Vasya", 2));

        assertEquals(1, node.context().query().querySqlFieldsNoCache(
            new SqlFieldsQuery("SELECT id, name, orgId FROM TEST.Person where (id = ?)").setArgs(1L), false
        ).getAll().size());
    }

Issue Links

• links to: GitHub Pull Request #2617