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
[
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
[
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
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
