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

SPARK-1478.2 Fix incorrect NioServerSocketChannelFactory constructor call #1466

Closed
wants to merge 1 commit into from

Conversation

srowen
Copy link
Member

@srowen srowen commented Jul 17, 2014

The line break inadvertently means this was interpreted as a call to the no-arg constructor. This doesn't exist in older Netty even. (Also fixed a val name typo.)

…nstructor as the no-arg version, which is not even present in some versions of Netty
@SparkQA
Copy link

SparkQA commented Jul 17, 2014

QA tests have started for PR 1466. This patch merges cleanly.
View progress: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16783/consoleFull

channelFactory,
channelPipelieFactory,
channelFactory,
channelPipelineFactory,
Copy link
Contributor

Choose a reason for hiding this comment

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

What changed here? Was there a formatting issue?

Copy link
Member Author

Choose a reason for hiding this comment

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

There was a typo in the variable name. The other line was just the IDE
stripping a trailing space I think.
On Jul 17, 2014 7:52 PM, "Tathagata Das" [email protected] wrote:

In
external/flume/src/main/scala/org/apache/spark/streaming/flume/FlumeInputDStream.scala:

   new NettyServer(
     responder,
     new InetSocketAddress(host, port),
  •    channelFactory,
    
  •    channelPipelieFactory,
    
  •    channelFactory,
    
  •    channelPipelineFactory,
    

What changed here? Was there a formatting issue?


Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/1466/files#r15076612.

@SparkQA
Copy link

SparkQA commented Jul 17, 2014

QA results for PR 1466:
- This patch PASSES unit tests.
- This patch merges cleanly
- This patch adds no public classes

For more information see test ouptut:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16783/consoleFull

@tdas
Copy link
Contributor

tdas commented Jul 17, 2014

Merging this, thanks Sean for the good catch and the fix.

@asfgit asfgit closed this in 1fcd5dc Jul 17, 2014
@pwendell
Copy link
Contributor

@tdas should this be back-ported into 1.0?

@pwendell
Copy link
Contributor

@tdas nvm - I think this just doesn't exist in 1.0 :)

@srowen srowen deleted the SPARK-1478.2 branch July 18, 2014 11:23
xiliu82 pushed a commit to xiliu82/spark that referenced this pull request Sep 4, 2014
…call

The line break inadvertently means this was interpreted as a call to the no-arg constructor. This doesn't exist in older Netty even. (Also fixed a val name typo.)

Author: Sean Owen <[email protected]>

Closes apache#1466 from srowen/SPARK-1478.2 and squashes the following commits:

59c3501 [Sean Owen] Line break caused Scala to interpret NioServerSocketChannelFactory constructor as the no-arg version, which is not even present in some versions of Netty
viirya pushed a commit to viirya/spark-1 that referenced this pull request Oct 19, 2023
… to 3.4) (apache#1808)

* rdar://111235765 ALTER TABLE ... WRITE command (apache#1231) (apache#1466)

This PR cherry-picks the command to set write distribution and ordering in a table.

These changes are needed to allow customers to control the required distribution and ordering in Iceberg.

It adds a new command that will be only supported by the Iceberg data source.

This PR comes with tests.

* rdar://84102488 Support ordering and distribution during table creation (apache#1485)

This PR cherry-picks the ordering and distribution during table creation to 3.2. The same syntax is supported in 3.0 and 3.1.

These changes are needed to define a sort key and distribution in Iceberg tables.

Yes but the changes won't affect anyone except Iceberg users.

This PR comes with tests.

Co-authored-by: Russell Spitzer <[email protected]>
Co-authored-by: Anton Okolnychyi <[email protected]>
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.

4 participants