Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove TSDB listener accept message #6252

Merged
merged 13 commits into from
Apr 12, 2016
Merged

Remove TSDB listener accept message #6252

merged 13 commits into from
Apr 12, 2016

Conversation

simnv
Copy link
Contributor

@simnv simnv commented Apr 7, 2016

Required for all non-trivial PRs
  • Rebased/mergable
  • Tests pass
  • CHANGELOG.md updated
  • Sign CLA (if not already signed)

OpenTSDB input pollutes log with "TSDB listener accept" messages:

$ tail -f /var/log/influxdb/influxd.log
[run] 2016/04/07 16:56:34 TSDB listener accept  &{0xc2c0018a28 0xc2e0f92660}
[run] 2016/04/07 16:56:34 TSDB listener accept  &{0xc493201318 0xc502761500}

Fix for #6251

simnv and others added 10 commits April 7, 2016 17:15
Fixes #6211.

In Go-land packages with the same name, e.g., internal, do not clash
with each other when they're in different parts of the project. However
with protobufs definitions will clash if they share the same package
name.

This commit renames the influxql protobuf package to `influxql` to
avoid a clash with a message definition in another protobuf package
called internal. Go package aliases allow us to continue to refer to the
internal package as `internal` rather than `influxql`.
Influxdb uses gdm for the dependency management. For gdm to work on Windows, it needs go 1.6. Influx still uses go 1.4.3. So go 1.6 will be sed for the pre-build stages, and go 1.4.3 to run the tests.
This arrangements is working in AppVeyor now.
The following query was fixed previously:

    SELECT 'value' FROM cpu

This ended up hitting the `buildExprIterator()` code path and was
handled properly. But this query:

    SELECT 'value', value FROM cpu

This took a different code path that would trigger a panic because it
triggered a panic instead of an error condition. This code path has now
been modified to trigger an error instead of a panic.

Fixes #6248.
Queries with a time constraint but no group by would not include the
final point from the underlying iterator.

Fixes #6229.
@toddboom
Copy link
Contributor

@simnv Could you give this a quick rebase? Thanks!

@simnv
Copy link
Contributor Author

simnv commented Apr 12, 2016

@toddboom Done.

@toddboom toddboom merged commit 1e6b76e into influxdata:master Apr 12, 2016
@simnv simnv deleted the opentsdb-log-less branch April 13, 2016 05:03
@timhallinflux timhallinflux added this to the 0.13.0 milestone Dec 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants