[jira] [Commented] (CALCITE-1076) Metadata distribution is broken due to last refactor
[
https://issues.apache.org/jira/browse/CALCITE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133559#comment-15133559
]
Ted Xu commented on CALCITE-1076:
-
Thanks [~julianhyde], that's exactly what I'm expecting, but I'm not sure if
adding {{RelMdDistribution}} into default metadata provider could have other
impact.
I'm added {{RelMdDistribution}} into default metadata provider, the updated
pull request is https://github.com/apache/calcite/pull/194. We can also add
{{RelMdDistribution}} into RelMetadataTest only, if you feel the former way is
too intrusive.
> Metadata distribution is broken due to last refactor
>
>
> Key: CALCITE-1076
> URL: https://issues.apache.org/jira/browse/CALCITE-1076
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.7.0
>Reporter: Ted Xu
>Assignee: Julian Hyde
>
> Metadata distribution is broken due to last refactor.
> Calls of RelMdDistribution will get:
> {code}
> java.lang.AssertionError: are your methods named wrong?
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CALCITE-1077) Separate Avatica from "core" Calcite build
Josh Elser created CALCITE-1077: --- Summary: Separate Avatica from "core" Calcite build Key: CALCITE-1077 URL: https://issues.apache.org/jira/browse/CALCITE-1077 Project: Calcite Issue Type: Task Components: avatica Reporter: Josh Elser Assignee: Josh Elser Fix For: 1.7.0 Uber-JIRA-issue for tracking the separation of Avatica from the rest of the Calcite build. Long term, Avatica can be a standalone project, but we're not there yet in terms of governance (enough people intimately involved). One thing we can do now is to separate Avatica from Calcite and begin "getting them used to" not being next to one another. DISCUSS thread: https://mail-archives.apache.org/mod_mbox/calcite-dev/201601.mbox/%3C56ABCCFF.3010205%40gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CALCITE-1079) Update website for Avatica
Josh Elser created CALCITE-1079: --- Summary: Update website for Avatica Key: CALCITE-1079 URL: https://issues.apache.org/jira/browse/CALCITE-1079 Project: Calcite Issue Type: Sub-task Components: avatica Reporter: Josh Elser Assignee: Josh Elser Fix For: 1.7.0 * Centralize all of the avatica content into its own "directory" inside of the calcite website * Create history.md file for tracking avatica releases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CALCITE-1078) Move all Avatica module into a detached directory
Josh Elser created CALCITE-1078: --- Summary: Move all Avatica module into a detached directory Key: CALCITE-1078 URL: https://issues.apache.org/jira/browse/CALCITE-1078 Project: Calcite Issue Type: Sub-task Components: avatica Reporter: Josh Elser Assignee: Josh Elser Fix For: 1.7.0 To decouple Avatica from the rest of Calcite, we need to restructure the location of the Maven modules and the pom structure. Let's move all of the avatica modules into an "avatica/" directory at the root of the Calcite repository. We should also directly use the Apache parent pom instead of the Calcite parent pom. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CALCITE-642) Avatica server metrics
[ https://issues.apache.org/jira/browse/CALCITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved CALCITE-642. Resolution: Fixed Merged in https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=7e5710fc7459728a667659ea2b66895812ef839f > Avatica server metrics > -- > > Key: CALCITE-642 > URL: https://issues.apache.org/jira/browse/CALCITE-642 > Project: Calcite > Issue Type: Improvement > Components: avatica >Reporter: Nick Dimiduk >Assignee: Josh Elser > Labels: avatica > Fix For: next > > > Along the same lines as CALCITE-641, avatica server should track some basic > metrics. We can expose them through a "standard" API (such as Hadoop metrics, > or Dropwizard metrics), and include them on some interval in the service log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
