Hi, I want unsubscribe for this group. Could you delete my account? regards.
Sebastiano. 2016-05-03 22:27 GMT+02:00 Ankit Singhal (JIRA) <j...@apache.org>: > > [ > https://issues.apache.org/jira/browse/PHOENIX-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269512#comment-15269512 > ] > > Ankit Singhal commented on PHOENIX-2862: > ---------------------------------------- > > [~samarthjain], let me know if you have further questions. > This pull request has some other couple of fixes too, so can you take > please take a look:- > 1. Like, resolving schema during creation of table if it is set through > jdbc connection string > 2. Check Namespace before creating as direct creating and handling > nameSpaceExistsException was causing issue with CSVBulkLoad. > 3. IndexTool was not support already existing hbase table mapped to > phoenix of format "RAW:Table" (case sensitive > https://github.com/apache/phoenix/pull/166#issuecomment-215305552) > > > > Do client server compatibility checks before upgrading system tables > > -------------------------------------------------------------------- > > > > Key: PHOENIX-2862 > > URL: https://issues.apache.org/jira/browse/PHOENIX-2862 > > Project: Phoenix > > Issue Type: Sub-task > > Reporter: Ankit Singhal > > Assignee: Ankit Singhal > > Fix For: 4.8.0 > > > > Attachments: PHOENIX-2862.patch > > > > > > currently , we allow upgrade of system tables to map to system namespace > by enabling "phoenix.schema.mapSystemTablesToNamespace" config (conjuction > with "phoenix.connection.isNamespaceMappingEnabled") > > but we need to ensure following things whenever client connects with > above config:- > > 1. Server should be upgraded and check consistency of these properties > between client and server. > > 2. If above property does not exists but system:catalog exists, we > should not start creating system.catalog. > > 3. if old client connects, it should not create system.catalog again > ignoring the upgrade and start using it. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >