Thanks Sergey for your answer, i'll try it.
Regards,
Mathieu
--
View this message in context:
http://apache-phoenix-user-list.1124778.n5.nabble.com/How-to-migrate-sql-cascade-and-foreign-keys-tp3226p3255.html
Sent from the Apache Phoenix User List mailing list archive at Nabble.com.
Hi all,
I am cross posting this from the Calcite mailing list, since the phoenix
query server uses Avatica from the Calcite project.
Go 1.8 was released recently and the database/sql package saw a lot of
new features. I just tagged the v1.3.0 release for the Go Avatica
driver[0] which ships
Hi,
You may specify HBase config by setting HBASE_CONF_DIR env variable. Or
just put the directory that has it in the classpath. If no hbase-site.xml
found, the default values will be used.
As for the memory, it really depends on the usage scenario. If you have
large tables with thousands of
Unsubscribe yourself just like you subscribed yourself.
user-unsubscr...@phoenix.apache.org
Saravanan A wrote:
unsubscribe.
re #1, you need to ensure that the correct hbase-site.xml is on the
classpath on your application. Phoenix does *not* do this for you.
Pradheep Shanmugam wrote:
Hi,
1. When using phoenix thick client(4.4.0) at the application, where
does the client hbase-site.xml reside..I don’t see one?
Well, Apache Phoenix doesn't support foreign key, so you need to manage
this functionality on your application layer. Sometimes, depending on the
scenario you may emulate this functionality using VIEWs for user table with
additional columns instead of creating a set of separated tables. More
--
Best Regards,
Vijay kukkala
318-243-9725
