Re: master branch compilation errors shown in Eclipse

2017-08-04 Thread Muhammad Gelbana 
An error shows that the class *ExprLexer* cannot be resolved, The .java
file for that class is generated and found in *drill-logical* project
(module ?) int it's *target/generated-sources/antlr3/* folder, which I
configured, through Eclipse, to be a source folder and then *ALL*
compilation errors were gone.

Shouldn't that be configured in maven somewhere ?



Thanks,
Gelbana

On Wed, Aug 2, 2017 at 8:22 PM, Muhammad Gelbana 
wrote:

> The TSV file is ruined by the stacktraces in the maven exceptions, I
> deleted those and attached another one excluding them.
>
> Thanks,
> Gelbana
>
> On Wed, Aug 2, 2017 at 8:17 PM, Muhammad Gelbana 
> wrote:
>
>> I attached a TSV file showing the errors I have in Eclipse. I believe its
>> something that has to do with code generation because many errors are:
>>
>>- Compilation errors due to mismatching signatures for overridden
>>methods while the *@Override* annotation is applied
>>- Missing fields\methods such as the missing *INSTANCE* field in
>>*org.apache.calcite.rel.metadata.DefaultRelMetadataProvider* (Shown
>>in the screenshot)
>>
>>
>> Thanks,
>> Gelbana
>>
>> On Wed, Aug 2, 2017 at 6:16 PM, Paul Rogers  wrote:
>>
>>> Please pass along the detailed error: here or in the JIRA you filed
>>> earlier. That way, we can try to figure out what’s happening.
>>>
>>> Thanks,
>>>
>>> - Paul
>>>
>>> On Aug 2, 2017, at 6:45 AM, Muhammad Gelbana >> > wrote:
>>>
>>> I pulled the latest code from the master branch just today. Ran mvn
>>> clean install -DskipTests which finished successfully, updated all projects
>>> but the update filed due to a NullPointerException while updating the
>>> vector project. So I ran the update again but excluded the vector project
>>> this time.
>>>
>>> Now I'm left with the errors shown in the attached image.
>>>
>>> I'm used to developing a Drill plugin in Eclipse but using the 1.9
>>> branch with only errors only related to maven like lifecycles errors. And
>>> that didn't cause any issue for me.
>>>
>>> I was hoping to create a simple PR but this is blocking me. Would
>>> someone please help me get through this ?
>>>
>>> ​Thanks,
>>> Gelbana
>>>
>>>
>>
>

Re: master branch compilation errors shown in Eclipse

2017-08-02 Thread Muhammad Gelbana 
The TSV file is ruined by the stacktraces in the maven exceptions, I
deleted those and attached another one excluding them.

Thanks,
Gelbana

On Wed, Aug 2, 2017 at 8:17 PM, Muhammad Gelbana 
wrote:

> I attached a TSV file showing the errors I have in Eclipse. I believe its
> something that has to do with code generation because many errors are:
>
>- Compilation errors due to mismatching signatures for overridden
>methods while the *@Override* annotation is applied
>- Missing fields\methods such as the missing *INSTANCE* field in
>*org.apache.calcite.rel.metadata.DefaultRelMetadataProvider* (Shown in
>the screenshot)
>
>
> Thanks,
> Gelbana
>
> On Wed, Aug 2, 2017 at 6:16 PM, Paul Rogers  wrote:
>
>> Please pass along the detailed error: here or in the JIRA you filed
>> earlier. That way, we can try to figure out what’s happening.
>>
>> Thanks,
>>
>> - Paul
>>
>> On Aug 2, 2017, at 6:45 AM, Muhammad Gelbana  m.gelb...@gmail.com>> wrote:
>>
>> I pulled the latest code from the master branch just today. Ran mvn clean
>> install -DskipTests which finished successfully, updated all projects but
>> the update filed due to a NullPointerException while updating the vector
>> project. So I ran the update again but excluded the vector project this
>> time.
>>
>> Now I'm left with the errors shown in the attached image.
>>
>> I'm used to developing a Drill plugin in Eclipse but using the 1.9 branch
>> with only errors only related to maven like lifecycles errors. And that
>> didn't cause any issue for me.
>>
>> I was hoping to create a simple PR but this is blocking me. Would someone
>> please help me get through this ?
>>
>> ​Thanks,
>> Gelbana
>>
>>
>

DescriptionResourcePathLocationType
INSTANCE cannot be resolved or is not a fieldDrillDefaultRelMetadataProvider.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/costline 32Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillAggregateRel must override or implement a supertype methodDrillAggregateRel.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/logicalline 88Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillFilterRelBase must override or implement a supertype methodDrillFilterRelBase.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/commonline 67Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillJoinRelBase must override or implement a supertype methodDrillJoinRelBase.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/commonline 64Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillLimitRelBase must override or implement a supertype methodDrillLimitRelBase.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/commonline 66Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillProjectRelBase must override or implement a supertype methodDrillProjectRelBase.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/commonline 73Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillScanRel must override or implement a supertype methodDrillScanRel.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/logicalline 159Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillScreenRelBase must override or implement a supertype methodDrillScreenRelBase.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/commonline 42Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type DrillUnionRel must override or implement a supertype methodDrillUnionRel.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/logicalline 58Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type HashAggPrel must override or implement a supertype methodHashAggPrel.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/physicalline 68Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type HashToMergeExchangePrel must override or implement a supertype methodHashToMergeExchangePrel.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/physicalline 55Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type HashToRandomExchangePrel must override or implement a supertype methodHashToRandomExchangePrel.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/physicalline 66Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type OrderedPartitionExchangePrel must override or implement a supertype methodOrderedPartitionExchangePrel.java/drill-java-exec/src/main/java/org/apache/drill/exec/planner/physicalline 42Java Problem
The method computeSelfCost(RelOptPlanner, RelMetadataQuery) of type ScanPrel must override or implement a supertype

Re: master branch compilation errors shown in Eclipse

2017-08-02 Thread Muhammad Gelbana 
I attached a TSV file showing the errors I have in Eclipse. I believe its
something that has to do with code generation because many errors are:

   - Compilation errors due to mismatching signatures for overridden
   methods while the *@Override* annotation is applied
   - Missing fields\methods such as the missing *INSTANCE* field in
   *org.apache.calcite.rel.metadata.DefaultRelMetadataProvider* (Shown in
   the screenshot)


Thanks,
Gelbana

On Wed, Aug 2, 2017 at 6:16 PM, Paul Rogers  wrote:

> Please pass along the detailed error: here or in the JIRA you filed
> earlier. That way, we can try to figure out what’s happening.
>
> Thanks,
>
> - Paul
>
> On Aug 2, 2017, at 6:45 AM, Muhammad Gelbana > wrote:
>
> I pulled the latest code from the master branch just today. Ran mvn clean
> install -DskipTests which finished successfully, updated all projects but
> the update filed due to a NullPointerException while updating the vector
> project. So I ran the update again but excluded the vector project this
> time.
>
> Now I'm left with the errors shown in the attached image.
>
> I'm used to developing a Drill plugin in Eclipse but using the 1.9 branch
> with only errors only related to maven like lifecycles errors. And that
> didn't cause any issue for me.
>
> I was hoping to create a simple PR but this is blocking me. Would someone
> please help me get through this ?
>
> ​Thanks,
> Gelbana
>
>

DescriptionResourcePathLocationType
Artifact has not been packaged yet. When used on reactor artifact, unpack should be executed after packaging: see MDEP-98. (org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack:unpack-vector-types:initialize)

org.apache.maven.plugin.MojoExecutionException: Artifact has not been packaged yet. When used on reactor artifact, unpack should be executed after packaging: see MDEP-98.
at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:265)
at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:128)
at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.doExecute(UnpackMojo.java:106)
at org.apache.maven.plugin.dependency.AbstractDependencyMojo.execute(AbstractDependencyMojo.java:167)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
at com.ianbrandt.tools.m2e.mdp.core.MdpBuildParticipant.executeMojo(MdpBuildParticipant.java:133)
at com.ianbrandt.tools.m2e.mdp.core.MdpBuildParticipant.build(MdpBuildParticipant.java:67)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
at

Re: master branch compilation errors shown in Eclipse

2017-08-02 Thread Paul Rogers 
Please pass along the detailed error: here or in the JIRA you filed earlier. 
That way, we can try to figure out what’s happening.

Thanks,

- Paul

On Aug 2, 2017, at 6:45 AM, Muhammad Gelbana 
> wrote:

I pulled the latest code from the master branch just today. Ran mvn clean 
install -DskipTests which finished successfully, updated all projects but the 
update filed due to a NullPointerException while updating the vector project. 
So I ran the update again but excluded the vector project this time.

Now I'm left with the errors shown in the attached image.

I'm used to developing a Drill plugin in Eclipse but using the 1.9 branch with 
only errors only related to maven like lifecycles errors. And that didn't cause 
any issue for me.

I was hoping to create a simple PR but this is blocking me. Would someone 
please help me get through this ?

​Thanks,
Gelbana

master branch compilation errors shown in Eclipse

2017-08-02 Thread Muhammad Gelbana 
I pulled the latest code from the master branch just today. Ran *mvn clean
install -DskipTests* which finished successfully, updated all projects but
the update filed due to a *NullPointerException* while updating the *vector*
project. So I ran the update again but excluded the *vector* project this
time.

Now I'm left with the errors shown in the attached image.

I'm used to developing a Drill plugin in Eclipse but using the *1.9* branch
with only errors only related to maven like lifecycles errors. And that
didn't cause any issue for me.

I was hoping to create a simple PR but this is blocking me. Would someone
please help me get through this ?

​Thanks,
Gelbana