Hi Mark, There's not a great reason for this restriction, so it can likely be relaxed. The tenant ID comes from a connection property, so it'll be a string, but we could convert it based on the data type of the first column. Please file a JIRA is this is important for your use case. Thanks, James
On Wed, Feb 18, 2015 at 11:45 AM, Mark Tse <mark....@d2l.com> wrote: > Hi everyone, > > > > Quote from http://phoenix.apache.org/multi-tenancy.html: > > The column that identifies the tenant may be given any name, but must of > type VARCHAR or CHAR. Regular Phoenix connections work with such tables with > no constraints, including working with data across tenant boundaries. > > > > Is there a reason it can’t be something else, such as an INTEGER or an > UNSIGNED_LONG? > > > > Thanks, > > Mark > >
