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

Init all record fields #111

Merged
merged 1 commit into from
Feb 11, 2019
Merged

Conversation

bpintea
Copy link
Collaborator

@bpintea bpintea commented Feb 8, 2019

Some of the string record fields have been left 0-ed, which is
problematic when their value is asked for. This PR inits them all to
the empty string, so that the transfer can take place.

(Their value would normally be provided by the data source, but this is
now not available with the current ES/SQL API.)

The PR also fixes two API tracing statements.

Some of the string record fields have been left 0-ed, which is
problematic when their value is asked for. This commit inits them all to
the empty string, so that the transfer can take place.

(Their value would normally be provided by the data source, but this is
now not available with the current ES/SQL API.)
Copy link
Collaborator

@edsavage edsavage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bpintea bpintea merged commit f50959b into elastic:master Feb 11, 2019
@bpintea bpintea deleted the fix/init_all_rec_fields branch February 11, 2019 10:52
bpintea added a commit that referenced this pull request Feb 11, 2019
Some of the string record fields have been left 0-ed, which is
problematic when their value is asked for. This commit inits them all to
the empty string, so that the transfer can take place.

(Their value would normally be provided by the data source, but this is
now not available with the current ES/SQL API.)

(cherry picked from commit f50959b)
bpintea added a commit that referenced this pull request Feb 11, 2019
Some of the string record fields have been left 0-ed, which is
problematic when their value is asked for. This commit inits them all to
the empty string, so that the transfer can take place.

(Their value would normally be provided by the data source, but this is
now not available with the current ES/SQL API.)

(cherry picked from commit f50959b)
bpintea added a commit that referenced this pull request Feb 11, 2019
Some of the string record fields have been left 0-ed, which is
problematic when their value is asked for. This commit inits them all to
the empty string, so that the transfer can take place.

(Their value would normally be provided by the data source, but this is
now not available with the current ES/SQL API.)

(cherry picked from commit f50959b)
bpintea added a commit that referenced this pull request Feb 11, 2019
Some of the string record fields have been left 0-ed, which is
problematic when their value is asked for. This commit inits them all to
the empty string, so that the transfer can take place.

(Their value would normally be provided by the data source, but this is
now not available with the current ES/SQL API.)

(cherry picked from commit f50959b)
@bpintea bpintea added >bug and removed fix labels May 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants