[GSoC] Interested in GSoC 2017 ideas

[Kai Jiang]

Hi All,

I am Kai, a master student majoring in CS from Portland State University,
highly interested in Big data and Distributed System. I have contributed to
Apache Spark as a GSoC project last year.

I've been contributing to Geode codebase. Some my Pull Requests are here.(
https://github.com/apache/geode/pulls?q=is%3Apr+author%3Avectorijk+is%3Aclosed
)
Also, I did some experiments on last year GSoC idea (GEODE-194
<https://issues.apache.org/jira/browse/GEODE-194> Geode Spark Connector
does not support Spark 2.0) on my branch (
https://github.com/vectorijk/geode/commits/spark2). I would like to extend
my work with Geode as a GSoC project this year and look forward to writing
something meaningful and impactful.

Is there any Geode Committer who's going to sign up as a mentor for GSoC
this year? Maybe you could tell me about the projects you are going to
mentor and give me some suggestions about what issues I could fix now to
get involved. If community has anything else in mind, I am very willing to
work on some issues before GSoC and get started with something new during
GSoC.

Looking forward!

Best,
Kai Jiang
github.com/vectorijk

Re: [GSoC] Interested in GSoC 2017 ideas

[Kai Jiang]

@Anthony,
Thanks! I really appreciate for your help and information!

@Hitesh,
Nice to e-meet you here! Do you have any idea about GSoC project with Geode
this year?
Looking forward!

Best,
Kai

On Tue, Mar 7, 2017 at 7:02 AM, Anthony Baker  wrote:

> Hi Kai,
>
> Welcome, and thanks for your interest!  We have one committer interested
> in mentoring so far (Hitesh Khamesra  hitesh...@yahoo.com>>).  Please feel free to reach out to the community
> for help or questions.  Best of luck to you!
>
> @Committers:  if you want to participate as a mentor in GSoC, now is the
> time to get involved.
>
> Anthony
>
> > On Mar 6, 2017, at 7:30 AM, Kai Jiang  wrote:
> >
> > Hi All,
> >
> > I am Kai, a master student majoring in CS from Portland State University,
> > highly interested in Big data and Distributed System. I have contributed
> to
> > Apache Spark as a GSoC project last year.
> >
> > I've been contributing to Geode codebase. Some my Pull Requests are
> here.(
> > https://github.com/apache/geode/pulls?q=is%3Apr+author%3Avec
> torijk+is%3Aclosed
> > )
> > Also, I did some experiments on last year GSoC idea (GEODE-194
> > <https://issues.apache.org/jira/browse/GEODE-194> Geode Spark Connector
> > does not support Spark 2.0) on my branch (
> > https://github.com/vectorijk/geode/commits/spark2). I would like to
> extend
> > my work with Geode as a GSoC project this year and look forward to
> writing
> > something meaningful and impactful.
> >
> > Is there any Geode Committer who's going to sign up as a mentor for GSoC
> > this year? Maybe you could tell me about the projects you are going to
> > mentor and give me some suggestions about what issues I could fix now to
> > get involved. If community has anything else in mind, I am very willing
> to
> > work on some issues before GSoC and get started with something new during
> > GSoC.
> >
> > Looking forward!
> >
> > Best,
> > Kai Jiang
> > github.com/vectorijk
>
>

Re: [GSoC] Interested in GSoC 2017 ideas

[Kai Jiang]

Hi Hitesh,

Thanks! I pretty like your ideas. Could I discuss more about the details of
your ideas offline?
I would like to write the proposal right away since the application of GSoC
will start very soon (Mar 20th).

Looking forward!

Best,
Kai

On Wed, Mar 8, 2017 at 6:14 PM, Hitesh Khamesra  wrote:

> Hi Kai:
>
> I have couple of ideas..
>
> 1. Reliable event processing on Geode.
> 2. New developer friendly apis on Geode.
>
> Let me know if you some query on this or you have some other idea.
>
> Thanks.
> Hitesh
>
>
> ------
> *From:* Kai Jiang 
> *To:* dev@geode.apache.org
> *Cc:* William Markito Oliveira ; Hitesh
> Khamesra 
> *Sent:* Tuesday, March 7, 2017 8:05 AM
> *Subject:* Re: [GSoC] Interested in GSoC 2017 ideas
>
> @Anthony,
> Thanks! I really appreciate for your help and information!
>
> @Hitesh,
> Nice to e-meet you here! Do you have any idea about GSoC project with
> Geode this year?
> Looking forward!
>
> Best,
> Kai
>
> On Tue, Mar 7, 2017 at 7:02 AM, Anthony Baker  wrote:
>
> Hi Kai,
>
> Welcome, and thanks for your interest!  We have one committer interested
> in mentoring so far (Hitesh Khamesra  hitesh...@yahoo.com>>) .  Please feel free to reach out to the community
> for help or questions.  Best of luck to you!
>
> @Committers:  if you want to participate as a mentor in GSoC, now is the
> time to get involved.
>
> Anthony
>
> > On Mar 6, 2017, at 7:30 AM, Kai Jiang  wrote:
> >
> > Hi All,
> >
> > I am Kai, a master student majoring in CS from Portland State University,
> > highly interested in Big data and Distributed System. I have contributed
> to
> > Apache Spark as a GSoC project last year.
> >
> > I've been contributing to Geode codebase. Some my Pull Requests are
> here.(
> > https://github.com/apache/geod e/pulls?q=is%3Apr+author%3Avec
> torijk+is%3Aclosed
> <https://github.com/apache/geode/pulls?q=is%3Apr+author%3Avectorijk+is%3Aclosed>
> > )
> > Also, I did some experiments on last year GSoC idea (GEODE-194
> > <https://issues.apache.org/jir a/browse/GEODE-194
> <https://issues.apache.org/jira/browse/GEODE-194>> Geode Spark Connector
> > does not support Spark 2.0) on my branch (
> > https://github.com/vectorijk/g eode/commits/spark2
> <https://github.com/vectorijk/geode/commits/spark2>). I would like to
> extend
> > my work with Geode as a GSoC project this year and look forward to
> writing
> > something meaningful and impactful.
> >
> > Is there any Geode Committer who's going to sign up as a mentor for GSoC
> > this year? Maybe you could tell me about the projects you are going to
> > mentor and give me some suggestions about what issues I could fix now to
> > get involved. If community has anything else in mind, I am very willing
> to
> > work on some issues before GSoC and get started with something new during
> > GSoC.
> >
> > Looking forward!
> >
> > Best,
> > Kai Jiang
> > github.com/vectorijk
>
>
>
>
>

Review Request 54586: GEODE-2172: CustomConfigWithCacheIntegrationTest fails with AssertionError on Windows

[Kai Jiang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54586/
---

Review request for geode and Kirk Lund.


Bugs: geode-2172
https://issues.apache.org/jira/browse/geode-2172


Repository: geode


Description
---

cacheLogWriterMessageShouldMatchCustomConfig fails with AssertionError.

The issues is related to incorrect regex pattern. The regex pattern used to 
match log string contains newline character. To fix this issue, I've replaced 
Unix newline character in regex pattern into `System.lineSeparator()`, a 
Platform-dependent newline character in Java.


Diffs
-

  
geode-core/src/test/java/org/apache/geode/internal/logging/log4j/custom/CustomConfiguration.java
 47515e6 

Diff: https://reviews.apache.org/r/54586/diff/


Testing
---

I've run this unit test both on Windows and MacOS. And it passes.


Thanks,

Kai Jiang

Re: Assigning Jira tickets to new contributors

[Kai Jiang]

Hi Kirk,

I am also a new contributor to GEODE project. Also, I am working on a few
issues(GEODE-2172 
GEODE-2167  GEODE-224
) . Maybe these issue
could be assigned to me.
Meanwhile, I will be appreciated if someone could review my pull requests.

JIRA id: vectorijk
Github id: vectorijk

Thanks,
Kai.



On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit 
wrote:

> Hello Kirk,
>
> I remember some apache help document mentioning need for user to be added
> to the project group.
> May be adding user to GEODE project group will help in enabling them to
> assign issues to themselves.
>
> Can you please grant similar permission to me (details are added below) so
> I can assign JIRA issue I am working on?
> I am currently working on GEODE-2109 and just finished with GEODE-734.
>
> Detail for apache id
> Email ID: deepakdixit2...@gmail.com
> apache id: deepakddixit
>
> Thanks,
>
> Deepak
>
>
> On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
>
> Does anyone know what needs to be done to enable assigning a Jira ticket to
> a new contributor? Alyssa Kim filed GEODE-2203 and would like to have the
> ticket assigned to her but Jira shows either "No Matches" or "User 'Alyssa
> Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.
>
> Thanks,
> Kirk
>

Re: Assigning Jira tickets to new contributors

[Kai Jiang]

Thanks William :)

Best,
Kai.

On Sun, Dec 11, 2016 at 8:08 PM, Deepak Dixit 
wrote:

> Thanks William :)
> I am able to assign JIRA on my apache id.
>
>
> On Mon, Dec 12, 2016 at 8:29 AM, William Markito Oliveira <
> william.mark...@gmail.com> wrote:
>
> > Great! So assigning people to the "contributors" role is good enough for
> > this, glad it worked!
> >
> > On Sun, Dec 11, 2016 at 6:51 PM Kirk Lund  wrote:
> >
> > > Thanks William!
> > >
> > > On Sun, Dec 11, 2016 at 6:30 PM William Markito Oliveira <
> > > william.mark...@gmail.com> wrote:
> > >
> > > > I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as
> > > "contributors"
> > > >
> > > > to the Geode JIRA project, but in the past we had problems with
> people
> > > not
> > > >
> > > > being able to "self-assign" JIRAs if they're not in the "committers"
> > > group.
> > > >
> > > >
> > > >
> > > > The workaround was to include them into the committers group on JIRA,
> > > which
> > > >
> > > > don't necessary give them commit privilege on the codebase, just on
> > JIRA.
> > > >
> > > > Alternatively now that we graduated we could try fixing the role
> > > >
> > > > "contributor" of JIRA to at least allow people to assign JIRAs to
> > > >
> > > > themselves.
> > > >
> > > >
> > > >
> > > > Please give it a try now and see if you can assign the tickets to
> you,
> > > >
> > > > otherwise let us know.   Thanks!
> > > >
> > > >
> > > >
> > > > On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang 
> wrote:
> > > >
> > > >
> > > >
> > > > > Hi Kirk,
> > > >
> > > > >
> > > >
> > > > > I am also a new contributor to GEODE project. Also, I am working
> on a
> > > few
> > > >
> > > > > issues(GEODE-2172 <https://issues.apache.org/
> jira/browse/GEODE-2172>
> > > >
> > > > > GEODE-2167 <https://issues.apache.org/jira/browse/GEODE-2167>
> > > GEODE-224
> > > >
> > > > > <https://issues.apache.org/jira/browse/GEODE-224>) . Maybe these
> > issue
> > > >
> > > > > could be assigned to me.
> > > >
> > > > > Meanwhile, I will be appreciated if someone could review my pull
> > > > requests.
> > > >
> > > > >
> > > >
> > > > > JIRA id: vectorijk
> > > >
> > > > > Github id: vectorijk
> > > >
> > > > >
> > > >
> > > > > Thanks,
> > > >
> > > > > Kai.
> > > >
> > > > >
> > > >
> > > > >
> > > >
> > > > >
> > > >
> > > > > On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit <
> > > > deepakdixit2...@gmail.com>
> > > >
> > > > > wrote:
> > > >
> > > > >
> > > >
> > > > > > Hello Kirk,
> > > >
> > > > > >
> > > >
> > > > > > I remember some apache help document mentioning need for user to
> be
> > > > added
> > > >
> > > > > > to the project group.
> > > >
> > > > > > May be adding user to GEODE project group will help in enabling
> > them
> > > to
> > > >
> > > > > > assign issues to themselves.
> > > >
> > > > > >
> > > >
> > > > > > Can you please grant similar permission to me (details are added
> > > below)
> > > >
> > > > > so
> > > >
> > > > > > I can assign JIRA issue I am working on?
> > > >
> > > > > > I am currently working on GEODE-2109 and just finished with
> > > GEODE-734.
> > > >
> > > > > >
> > > >
> > > > > > Detail for apache id
> > > >
> > > > > > Email ID: deepakdixit2...@gmail.com
> > > >
> > > > > > apache id: deepakddixit
> > > >
> > > > > >
> > > >
> > > > > > Thanks,
> > > >
> > > > > >
> > > >
> > > > > > Deepak
> > > >
> > > > > >
> > > >
> > > > > >
> > > >
> > > > > > On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:
> > > >
> > > > > >
> > > >
> > > > > > Does anyone know what needs to be done to enable assigning a Jira
> > > > ticket
> > > >
> > > > > to
> > > >
> > > > > > a new contributor? Alyssa Kim filed GEODE-2203 and would like to
> > have
> > > > the
> > > >
> > > > > > ticket assigned to her but Jira shows either "No Matches" or
> "User
> > > >
> > > > > 'Alyssa
> > > >
> > > > > > Kim' does not exist." -- her user id on the Apache Jira is
> > > dalyssakim.
> > > >
> > > > > >
> > > >
> > > > > > Thanks,
> > > >
> > > > > > Kirk
> > > >
> > > > > >
> > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > ~/William
> > > >
> > > >
> > >
> >
>
>
>
> --
> From:
>
> Deepak D Dixit
> deepakdixit2...@gmail.com
> +919028507537
>

Re: Review Request 54586: GEODE-2172: CustomConfigWithCacheIntegrationTest fails with AssertionError on Windows

[Kai Jiang]

> On Dec. 13, 2016, 3:33 p.m., Jinmei Liao wrote:
> > geode-core/src/test/java/org/apache/geode/internal/logging/log4j/custom/CustomConfiguration.java,
> >  line 53
> > <https://reviews.apache.org/r/54586/diff/1/?file=1580434#file1580434line53>
> >
> > Looks like this method is also used in 
> > CustomConfigWithLogServiceIntegrationTest. Did you also run that test on 
> > both platform as well?

Yes, I have tested this on both platforms(Windows 10 and macOS).


> On Dec. 13, 2016, 3:33 p.m., Jinmei Liao wrote:
> > geode-core/src/test/java/org/apache/geode/internal/logging/log4j/custom/CustomConfiguration.java,
> >  line 60
> > <https://reviews.apache.org/r/54586/diff/1/?file=1580434#file1580434line60>
> >
> > Looks like this method is never used in the project. We can either 
> > delete it or refactor the previous method to call this method.

Okay, got it.


- Kai


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54586/#review159075
---


On Dec. 13, 2016, 3:13 p.m., Kai Jiang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54586/
> ---
> 
> (Updated Dec. 13, 2016, 3:13 p.m.)
> 
> 
> Review request for geode, Jinmei Liao, Kirk Lund, and Dan Smith.
> 
> 
> Bugs: geode-2172
> https://issues.apache.org/jira/browse/geode-2172
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> cacheLogWriterMessageShouldMatchCustomConfig fails with AssertionError.
> 
> The issues is related to incorrect regex pattern. The regex pattern used to 
> match log string contains newline character. To fix this issue, I've replaced 
> Unix newline character in regex pattern into `System.lineSeparator()`, a 
> Platform-dependent newline character in Java.
> 
> 
> Diffs
> -
> 
>   
> geode-core/src/test/java/org/apache/geode/internal/logging/log4j/custom/CustomConfiguration.java
>  47515e6 
> 
> Diff: https://reviews.apache.org/r/54586/diff/
> 
> 
> Testing
> ---
> 
> I've run this unit test both on Windows and MacOS. And it passes.
> 
> 
> Thanks,
> 
> Kai Jiang
> 
>

Re: Review Request 54586: GEODE-2172: CustomConfigWithCacheIntegrationTest fails with AssertionError on Windows

[Kai Jiang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54586/
---

(Updated Dec. 19, 2016, 4:45 a.m.)


Review request for geode, Jinmei Liao, Kirk Lund, and Dan Smith.


Bugs: geode-2172
https://issues.apache.org/jira/browse/geode-2172


Repository: geode


Description
---

cacheLogWriterMessageShouldMatchCustomConfig fails with AssertionError.

The issues is related to incorrect regex pattern. The regex pattern used to 
match log string contains newline character. To fix this issue, I've replaced 
Unix newline character in regex pattern into `System.lineSeparator()`, a 
Platform-dependent newline character in Java.


Diffs (updated)
-

  
geode-core/src/test/java/org/apache/geode/internal/logging/log4j/custom/CustomConfiguration.java
 47515e6 

Diff: https://reviews.apache.org/r/54586/diff/


Testing
---

I've run this unit test both on Windows and MacOS. And it passes.


Thanks,

Kai Jiang

Re: Review Request 54586: GEODE-2172: CustomConfigWithCacheIntegrationTest fails with AssertionError on Windows

[Kai Jiang]

> On Dec. 13, 2016, 3:33 p.m., Jinmei Liao wrote:
> > geode-core/src/test/java/org/apache/geode/internal/logging/log4j/custom/CustomConfiguration.java,
> >  line 60
> > <https://reviews.apache.org/r/54586/diff/1/?file=1580434#file1580434line60>
> >
> > Looks like this method is never used in the project. We can either 
> > delete it or refactor the previous method to call this method.
> 
> Kai Jiang wrote:
> Okay, got it.

Deleted this.


- Kai


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54586/#review159075
-------


On Dec. 19, 2016, 4:45 a.m., Kai Jiang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54586/
> ---
> 
> (Updated Dec. 19, 2016, 4:45 a.m.)
> 
> 
> Review request for geode, Jinmei Liao, Kirk Lund, and Dan Smith.
> 
> 
> Bugs: geode-2172
> https://issues.apache.org/jira/browse/geode-2172
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> cacheLogWriterMessageShouldMatchCustomConfig fails with AssertionError.
> 
> The issues is related to incorrect regex pattern. The regex pattern used to 
> match log string contains newline character. To fix this issue, I've replaced 
> Unix newline character in regex pattern into `System.lineSeparator()`, a 
> Platform-dependent newline character in Java.
> 
> 
> Diffs
> -
> 
>   
> geode-core/src/test/java/org/apache/geode/internal/logging/log4j/custom/CustomConfiguration.java
>  47515e6 
> 
> Diff: https://reviews.apache.org/r/54586/diff/
> 
> 
> Testing
> ---
> 
> I've run this unit test both on Windows and MacOS. And it passes.
> 
> 
> Thanks,
> 
> Kai Jiang
> 
>

Re: OQLLexerTokenTypes - java: connot find symbol

[Kai Jiang]

I agreed with Jason. This happened in my environment several times. Clean
build could work.

Best,
Kai

On Thu, Jan 5, 2017 at 12:39 PM, Jason Huynh  wrote:

> I think a clean build and refreshing the intelij project should work.  I
> think the change removed those files and requires them to be generated from
> the build
>
> On Thu, Jan 5, 2017 at 12:36 PM Kirk Lund  wrote:
>
> > I rebased one of my feature branches on origin/develop, then refreshed
> > gradle in IntelliJ and then rebuilt my IntelliJ project but IntelliJ
> > insists that OQLLexerTokenTypes does not exist. My project is full of
> > errors like this:
> >
> > Error:(29, 51) java: cannot find symbol
> >   symbol:   class OQLLexerTokenTypes
> >   location: package org.apache.geode.cache.query.internal.parse
> >
> > Any ideas how to get my IntelliJ project working again without losing too
> > much time?
> >
> > Thanks,
> > Kirk
> >
>

[jira] [Assigned] (GEODE-2658) Provide Developer friendly api on Geode

[Kai Jiang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kai Jiang reassigned GEODE-2658:


Assignee: Kai Jiang

> Provide Developer friendly api on Geode
> ---
>
> Key: GEODE-2658
> URL: https://issues.apache.org/jira/browse/GEODE-2658
> Project: Geode
>  Issue Type: Bug
>Reporter: Hitesh Khamesra
>Assignee: Kai Jiang
>  Labels: GSoC2017
>
> Geode provides basic java concurrent map apis in distributed environment.
> These apis are not enough for application. Thus we need some utility api 
> based on Redis.
> 1. Update Counter Atomically.
> 2. Update object field atomically
> 3. Append new field to object
> 4. Fetch object field
> 5. Append new event to list (pop, push, range)
> 6. Append new member to set
> 7. Atomic Get and set
> 8. Atomic bit operations on value objects   
> 9. Set expiration on key
> 10. Merge objects  
> I will add more description later.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEODE-2658) Provide Developer friendly api on Geode

[Kai Jiang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kai Jiang reassigned GEODE-2658:


Assignee: (was: Kai Jiang)

> Provide Developer friendly api on Geode
> ---
>
> Key: GEODE-2658
> URL: https://issues.apache.org/jira/browse/GEODE-2658
> Project: Geode
>  Issue Type: Bug
>Reporter: Hitesh Khamesra
>  Labels: GSoC2017
>
> Geode provides basic java concurrent map apis in distributed environment.
> These apis are not enough for application. Thus we need some utility api 
> based on Redis.
> 1. Update Counter Atomically.
> 2. Update object field atomically
> 3. Append new field to object
> 4. Fetch object field
> 5. Append new event to list (pop, push, range)
> 6. Append new member to set
> 7. Atomic Get and set
> 8. Atomic bit operations on value objects   
> 9. Set expiration on key
> 10. Merge objects  
> I will add more description later.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEODE-224) Geode Spark connector parser is not processing type casting properly

[Kai Jiang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kai Jiang reassigned GEODE-224:
---

Assignee: Kai Jiang

> Geode Spark connector parser is not processing type casting properly
> 
>
> Key: GEODE-224
> URL: https://issues.apache.org/jira/browse/GEODE-224
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: William Markito Oliveira
>    Assignee: Kai Jiang
>Priority: Minor
>  Labels: gsoc2016
>
> Using GFSH a user can execute queries casting the data types but that's not 
> working using the geode-spark-connector. 
> {code}
> scala> sqlContext.gemfireOQL("SELECT (Double)t.ema, (Double)t.future_ema, 
> (Double)t.close, t.entryTimestamp FROM /TechIndicators t ");
> java.lang.RuntimeException: No result when parsing failed
> at scala.sys.package$.error(package.scala:27)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:181)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:167)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getRegionPathFromQuery(QueryRDD.scala:56)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getPartitions(QueryRDD.scala:24)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:219)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:217)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.spark.rdd.RDD.partitions(RDD.scala:217)
> at org.apache.spark.rdd.RDD.take(RDD.scala:1156)
> at org.apache.spark.rdd.RDD.first(RDD.scala:1189)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.SchemaBuilder.toSparkSchema(SchemaBuilder.scala:30)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.OQLRelation.schema(RDDConverter.scala:13)
> at 
> org.apache.spark.sql.sources.LogicalRelation.(LogicalRelation.scala:30)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-224) Geode Spark connector parser is not processing type casting properly

[Kai Jiang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kai Jiang updated GEODE-224:

Fix Version/s: 1.1.0

> Geode Spark connector parser is not processing type casting properly
> 
>
> Key: GEODE-224
> URL: https://issues.apache.org/jira/browse/GEODE-224
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: William Markito Oliveira
>    Assignee: Kai Jiang
>Priority: Minor
>  Labels: gsoc2016
> Fix For: 1.1.0
>
>
> Using GFSH a user can execute queries casting the data types but that's not 
> working using the geode-spark-connector. 
> {code}
> scala> sqlContext.gemfireOQL("SELECT (Double)t.ema, (Double)t.future_ema, 
> (Double)t.close, t.entryTimestamp FROM /TechIndicators t ");
> java.lang.RuntimeException: No result when parsing failed
> at scala.sys.package$.error(package.scala:27)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:181)
> at scala.util.parsing.combinator.Parsers$NoSuccess.get(Parsers.scala:167)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getRegionPathFromQuery(QueryRDD.scala:56)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.QueryRDD.getPartitions(QueryRDD.scala:24)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:219)
> at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:217)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.spark.rdd.RDD.partitions(RDD.scala:217)
> at org.apache.spark.rdd.RDD.take(RDD.scala:1156)
> at org.apache.spark.rdd.RDD.first(RDD.scala:1189)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.SchemaBuilder.toSparkSchema(SchemaBuilder.scala:30)
> at 
> io.pivotal.gemfire.spark.connector.internal.oql.OQLRelation.schema(RDDConverter.scala:13)
> at 
> org.apache.spark.sql.sources.LogicalRelation.(LogicalRelation.scala:30)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-2219) CustomConfigWithLogServiceIntegrationTest.logEventShouldMatchCustomConfig fails with AssertionError on Windows

[Kai Jiang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761322#comment-15761322
 ] 

Kai Jiang commented on GEODE-2219:
--

GEODE-2172 also fails with same AssertionError. I have submitted the 
review.[https://reviews.apache.org/r/54586/] Once the code merged, this issue 
could also be addressed.

> CustomConfigWithLogServiceIntegrationTest.logEventShouldMatchCustomConfig 
> fails with AssertionError on Windows
> --
>
> Key: GEODE-2219
> URL: https://issues.apache.org/jira/browse/GEODE-2219
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.0.0-incubating
> Environment: Windows
>Reporter: Kirk Lund
>Assignee: Mark Bretl
>  Labels: IntegrationTest, Windows
>
> {noformat}
> java.lang.AssertionError: 
> Expecting:
>  "CUSTOM: level=DEBUG time=2016/11/30 13:49:27.354 PST message=this is a log 
> statement
> throwable=
> "
> to match pattern:
>  "CUSTOM: level=DEBUG time=.* message=this is a log statement
> throwable=
> "
>   at 
> org.apache.geode.internal.logging.log4j.custom.CustomConfigWithLogServiceIntegrationTest.logEventShouldMatchCustomConfig(CustomConfigWithLogServiceIntegrationTest.java:119)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at 
> org.junit.contrib.java.lang.system.internal.LogPrintStream$1$1.evaluate(LogPrintStream.java:30)
>   at 
> org.junit.contrib.java.lang.system.internal.PrintStreamHandler$3.evaluate(PrintStreamHandler.java:48)
>   at 
> org.junit.contrib.java.lang.system.internal.LogPrintStream$1.evaluate(LogPrintStream.java:26)
>   at 
> org.junit.contrib.java.lang.system.internal.LogPrintStream$1$1.evaluate(LogPrintStream.java:30)
>   at 
> org.junit.contrib.java.lang.system.internal.PrintStreamHandler$3.evaluate(PrintStreamHandler.java:48)
>   at 
> org.junit.contrib.java.lang.system.internal.LogPrintStream$1.evaluate(LogPrintStream.java:26)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.j

[jira] [Assigned] (GEODE-2227) AutoSerializableJUnitTest.testMultipleClassLoaders fails with AssertionError on Windows

[Kai Jiang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kai Jiang reassigned GEODE-2227:


Assignee: Kai Jiang

> AutoSerializableJUnitTest.testMultipleClassLoaders fails with AssertionError 
> on Windows
> ---
>
> Key: GEODE-2227
> URL: https://issues.apache.org/jira/browse/GEODE-2227
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.0.0-incubating
> Environment: Windows
>Reporter: Kirk Lund
>Assignee: Kai Jiang
>  Labels: IntegrationTest, Windows
>
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> org.apache.geode.pdx.AutoSerializableJUnitTest.testMultipleClassLoaders(AutoSerializableJUnitTest.java:1275)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.d