Re: [DISCUSS] Maintaining the Site in Git Instead of SVN

[William Shen]

I think we do need to come up with a strategy on how to maintain website
documentation given that we have several versions that may potentially
conflict in documentation at times. Thomas, is this your main concern?


Josh - Would love to help drive it, though I’m not sure if i have all the
right access to do so.
Seems like we would need to:
- commit the svn site directory into git master (I can create a patch but
would need help committing this)
- file an infra ticket to migrate the website, and enable git-pubsub
(though I’m totally speak out of my knowledge here...)

On Sun, Jun 2, 2019 at 11:42 AM Josh Elser  wrote:

> Yeah, not sure I get your concern, Thomas. We only have one website.
>
> From the ASF Infra side, svn-pubsub (what deploys our code on SVN
> check-in) works the same as git-pubsub. It should just be a request to
> Infra to migrate the website from SVN to Git and then enable
> git-pubsub.
>
> No concerns in doing this from me. Even better if you'd like to drive
> it, William ;)
>
> On Fri, May 31, 2019 at 2:24 PM William Shen 
> wrote:
> >
> > Thomas,
> >
> > Which release line do we currently base our documentation on? Do you
> think
> > it makes sense to bring the site source into master, and always update
> the
> > site from master?
> >
> > - Will
> >
> > On Thu, May 30, 2019 at 8:46 PM Thomas D'Silva
> >  wrote:
> >
> > > Currently this would not be easy to do since we have multiple
> branches. If
> > > we decide to
> > > implement Lars' proposal to have a single branch and a module per
> supported
> > > HBase version
> > > then we could have a module for the website as well.
> > >
> > > On Thu, May 30, 2019 at 7:03 PM swaroopa kadam <
> swaroopa.kada...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Huge +1!
> > > >
> > > > On Thu, May 30, 2019 at 4:38 PM William Shen <
> wills...@marinsoftware.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > Currently, the Phoenix site is maintained in and built from SVN
> > > > > . Not sure what
> level
> > > of
> > > > > work it would require, but does it make sense to move the source
> from
> > > svn
> > > > > to git, so contribution to the website can follow the same JIRA/git
> > > > > workflow as the rest of the project? It could also make sure
> changes to
> > > > > Phoenix code are checked in with corresponding documentation
> changes
> > > when
> > > > > needed.
> > > > >
> > > > > - Will
> > > > >
> > > > --
> > > >
> > > >
> > > > Swaroopa Kadam
> > > > [image: https://]about.me/swaroopa_kadam
> > > > <
> > > >
> > >
> https://about.me/swaroopa_kadam?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api
> > > > >
> > > >
> > >
>

[jira] [Assigned] (PHOENIX-2340) Index creation on multi tenant table causes exception if tenant ID column referenced

[Swaroopa Kadam (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swaroopa Kadam reassigned PHOENIX-2340:
---

Assignee: (was: Swaroopa Kadam)

> Index creation on multi tenant table causes exception if tenant ID column 
> referenced
> 
>
> Key: PHOENIX-2340
> URL: https://issues.apache.org/jira/browse/PHOENIX-2340
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Priority: Major
>
> If an index is attempted to be created on a multi-tenant table, an error 
> occurs if the tenant ID column is referenced in the indexed columns. This is 
> because it's already automatically included. However, it should not be an 
> error if the user references it (as long as it's the first indexed column).
> To repro:
> {code}
> CREATE TABLE IF NOT EXISTS T (
> ORGANIZATION_ID CHAR(15) NOT NULL,
> NETWORK_ID CHAR(15) NOT NULL,
> SUBJECT_ID CHAR(15) NOT NULL,
> RUN_ID CHAR(15) NOT NULL,
> SCORE DOUBLE,
> TOPIC_ID CHAR(15) NOT NULL
> CONSTRAINT PK PRIMARY KEY (
> ORGANIZATION_ID,
> NETWORK_ID,
> SUBJECT_ID,
> RUN_ID,
> TOPIC_ID
> )
> ) MULTI_TENANT=TRUE;
> CREATE INDEX IDX ON T (
> ORGANIZATION_ID,
> NETWORK_ID,
> TOPIC_ID,
> RUN_ID,
> SCORE
> ) INCLUDE (
> SUBJECT_ID
> );
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (PHOENIX-675) Support specifying index details at the time of CREATE TABLE query

[Swaroopa Kadam (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swaroopa Kadam reassigned PHOENIX-675:
--

Assignee: (was: Swaroopa Kadam)

> Support specifying index details at the time of CREATE TABLE query
> --
>
> Key: PHOENIX-675
> URL: https://issues.apache.org/jira/browse/PHOENIX-675
> Project: Phoenix
>  Issue Type: Task
>Reporter: chrajeshbabu
>
> We can support specifying index details during table creation as well(which 
> is supported in some databases). This also helps in Hindex integration where 
> we can avoid unnecessary disable and enable of table every time while 
> creating index.
> Ex:
> CREATE TABLE test (
> id INT NOT NULL,
> last_name  CHAR(30) NOT NULL,
> first_name CHAR(30) NOT NULL,
> PRIMARY KEY (id),
> INDEX name (last_name,first_name)
> );



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] Maintaining the Site in Git Instead of SVN

[Josh Elser]

Yeah, not sure I get your concern, Thomas. We only have one website.

>From the ASF Infra side, svn-pubsub (what deploys our code on SVN
check-in) works the same as git-pubsub. It should just be a request to
Infra to migrate the website from SVN to Git and then enable
git-pubsub.

No concerns in doing this from me. Even better if you'd like to drive
it, William ;)

On Fri, May 31, 2019 at 2:24 PM William Shen  wrote:
>
> Thomas,
>
> Which release line do we currently base our documentation on? Do you think
> it makes sense to bring the site source into master, and always update the
> site from master?
>
> - Will
>
> On Thu, May 30, 2019 at 8:46 PM Thomas D'Silva
>  wrote:
>
> > Currently this would not be easy to do since we have multiple branches. If
> > we decide to
> > implement Lars' proposal to have a single branch and a module per supported
> > HBase version
> > then we could have a module for the website as well.
> >
> > On Thu, May 30, 2019 at 7:03 PM swaroopa kadam  > >
> > wrote:
> >
> > > Huge +1!
> > >
> > > On Thu, May 30, 2019 at 4:38 PM William Shen  > >
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > Currently, the Phoenix site is maintained in and built from SVN
> > > > . Not sure what level
> > of
> > > > work it would require, but does it make sense to move the source from
> > svn
> > > > to git, so contribution to the website can follow the same JIRA/git
> > > > workflow as the rest of the project? It could also make sure changes to
> > > > Phoenix code are checked in with corresponding documentation changes
> > when
> > > > needed.
> > > >
> > > > - Will
> > > >
> > > --
> > >
> > >
> > > Swaroopa Kadam
> > > [image: https://]about.me/swaroopa_kadam
> > > <
> > >
> > https://about.me/swaroopa_kadam?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api
> > > >
> > >
> >