[JBoss JIRA] (TEIID-4934) Allow importing VDBs with conflicting model
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4934?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4934:
-------------------------------------
The internals are designed such that when the imports occur the models become the part of the originating vdb. Teiid can NOT rename these model names because it will break the transformation queries as they can be fully qualified. We have considered this issue before.
> Allow importing VDBs with conflicting model
> -------------------------------------------
>
> Key: TEIID-4934
> URL: https://issues.jboss.org/browse/TEIID-4934
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 9.2.3
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
>
> It should be possible to import a model via "_import-vdb_" that conflicts with other models also imported via "_import-vdb_" if the conflicting model has the same version.
> This will allow greater model reuse, and not to have duplicated model definitions in multiple vdbs.
> Example:
> VDB 1:
> <code>
> <vdb name="OneVDB" version="1">
> <description>One VDB</description>
> <import-vdb name=ConflictingVDB" version="1"/>
> <import-vdb name="OtherVDB" version="1"/>
> </code>
> VDB 2:
> <code>
> <vdb name="TwoVDB" version="1">
> <description>TwoVDB</description>
> <import-vdb name=ConflictingVDB" version="1"/>
> <import-vdb name="YetOtherVDB" version="1"/>
> </code>
> VDB 3:
> <code>
> <vdb name="ThirdVDB" version="1">
> <description>Third VDB</description>
> <import-vdb name=OneVDB" version="1"/>
> <import-vdb name="TwoVDB" version="1"/>
> </code>
> Currently we cannot use the ThirdVDB as is, since there is a conflicting VDB (ConflictingVDB) defined in VDBS One and Two.
> Since both are using the same version, it should be possible to ignore the conflict (via a property for example).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4931) No Deployed Virtual Databases on console
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4931?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4931:
-------------------------------------
I am thinking this may be due to the amount of DDL data associated with each VDB. I have seen before with other dialog boxes in GWT based dialogs, after a certain amount of data they silently fail. You can verify this by checking to undeploy a VDB at a time and see if the screen automatically starts working?
> No Deployed Virtual Databases on console
> ----------------------------------------
>
> Key: TEIID-4931
> URL: https://issues.jboss.org/browse/TEIID-4931
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.2.3
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Attachments: image-2017-05-24-17-24-08-386.png, list-vdbs-result.json, server.log
>
>
> [^list-vdbs-result.json] After several deploys/undeploys of several VDBs, no VDB is listed any longer on console (Deployed Virtual Databases), although VDBs are effectively deployed.
> On logs:
> 2017-05-24 16:17:49,223 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker2_async-teiid-threads2) TEIID40003 VDB NetSuiteMappingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:49,271 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker0_async-teiid-threads0) TEIID40003 VDB CerillionVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,187 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads3) TEIID40003 VDB SalesForceVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,609 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker4_async-teiid-threads4) TEIID40003 VDB BillingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:52,012 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads5) TEIID40003 VDB CustomerVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,238 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads1) TEIID40003 VDB NetSuiteVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,584 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads6) TEIID40003 VDB ReferenceDataVDB.1 is set to ACTIVE
> 2017-05-24 16:18:27,115 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads7) TEIID40003 VDB FinanceVDB.1 is set to ACTIVE
> On console.
> !image-2017-05-24-17-24-08-386.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4916) Ensure modules have only a single or compatible licenses
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4916?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4916:
---------------------------------------
Converted the metadata module to just EPL.
Created the saxon-xom module to hold the MPL 2.0 (with incompatible license option) code
Further refined and then relicensed the ODataWKTWriter to asl - this removes any usage of lgpl source from the codebase.
> Ensure modules have only a single or compatible licenses
> --------------------------------------------------------
>
> Key: TEIID-4916
> URL: https://issues.jboss.org/browse/TEIID-4916
> Project: Teiid
> Issue Type: Sub-task
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Code that is EPL, MPL, and LGPL should be isolated from code that is ASL.
> For the index metadata logic it probably makes sense to dual or re-license the ASL code under EPL. The remaining MPL (saxon / xom related) logic and LGPL (odata wkt) should be separated as their own modules.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4315:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1335006|https://bugzilla.redhat.com/show_bug.cgi?id=1335006] from NEW to MODIFIED
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 8.12.x-6.4, 9.3.1
>
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4806) Infinispan DSL Resource Adapter: NullPointerException when Admin user/password not provided
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4806?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4806:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1431657|https://bugzilla.redhat.com/show_bug.cgi?id=1431657] from MODIFIED to ON_QA
> Infinispan DSL Resource Adapter: NullPointerException when Admin user/password not provided
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-4806
> URL: https://issues.jboss.org/browse/TEIID-4806
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.9.6_3
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 9.3, 8.12.x-6.4
>
>
> Infinispan DSL Resource adapter properties AdminUserName and AdminPassword are not defined as required. If they are not configured it results in NullpointerException during metadata load of a vdb which uses the connector.
> Creation of such resource-adapter shouldn't have succeeded, if the properties are required.
> {code:xml}
> <resource-adapter id="jdg-protobuf-customer-report">
> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/>
> <transaction-support>LocalTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory" jndi-name="java:/teiid4709-pro-ds" enabled="true" use-java-context="true" pool-name="jdg-protobuf-customer-report">
> <config-property name="MessageDescriptor">
> org.jboss.qe.jdg.remote.protobuf.CustomerReport
> </config-property>
> <config-property name="AuthApplicationRealm">
> ApplicationRealm
> </config-property>
> <config-property name="MessageMarshallers">
> org.jboss.qe.jdg.pojo.CustomerReport:org.jboss.qe.jdg.remote.marshaller.CustomerReportMarshaller
> </config-property>
> <config-property name="AuthUserName">
> teiidUser
> </config-property>
> <config-property name="AuthServerName">
> hostsecured
> </config-property>
> <config-property name="AuthSASLMechanism">
> DIGEST-MD5
> </config-property>
> <config-property name="AuthPassword">
> password
> </config-property>
> <config-property name="Module">
> org.jboss.qe.jdg.pojos
> </config-property>
> <config-property name="RemoteServerList">
> hostname:11323
> </config-property>
> <config-property name="ProtobufDefinitionFile">
> /org/jboss/qe/jdg/remote/protobuf/CustomerReport.proto
> </config-property>
> <config-property name="CacheTypeMap">
> sec-cache:org.jboss.qe.jdg.pojo.CustomerReport;customerId
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> {code}
> 13:34:21,156 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB teiid4709-pro.1 model "Source" metadata failed to load. Reason:java.lang.NullPointerException: org.teiid.translator.TranslatorException: java.lang.NullPointerException
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getCacheContainer(InfinispanConnectionImpl.java:363)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getDescriptor(InfinispanConnectionImpl.java:189)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getDescriptor(InfinispanConnectionImpl.java:180)
> at org.teiid.translator.infinispan.dsl.metadata.ProtobufMetadataProcessor.process(ProtobufMetadataProcessor.java:103)
> at org.teiid.translator.infinispan.dsl.metadata.ProtobufMetadataProcessor.process(ProtobufMetadataProcessor.java:77)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:950) [teiid-api-8.12.10.6_3.jar:8.12.10.6_3]
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.10.6_3.jar:8.12.10.6_3]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.10.6_3.jar:8.12.10.6_3]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.10.6_3.jar:8.12.10.6_3]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.10.6_3.jar:8.12.10.6_3]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.10.6_3.jar:8.12.10.6_3]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_111]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_111]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: javax.resource.ResourceException: java.lang.NullPointerException
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.createRemoteCache(InfinispanConnectionImpl.java:537)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.createRemoteCacheFromServerList(InfinispanConnectionImpl.java:477)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.createCacheContainer(InfinispanConnectionImpl.java:390)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getCacheContainer(InfinispanConnectionImpl.java:361)
> ... 14 more
> Caused by: java.lang.NullPointerException
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.createRemoteCache(InfinispanConnectionImpl.java:500)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-4315.
--------------------------------
Resolution: Done
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 8.12.x-6.4, 9.3.1
>
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4315:
-------------------------------
Fix Version/s: 8.12.x-6.4
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 8.12.x-6.4, 9.3.1
>
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
Work on TEIID-4315 stopped by Van Halbert.
------------------------------------------
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 9.3.1
>
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
Work on TEIID-4315 started by Van Halbert.
------------------------------------------
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 9.3.1
>
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months