Re: Weekly status

Did you mean to send this to asterixresea...@ics.uci.edu? Cheers, Till On 27 Oct 2017, at 9:24, abdullah alamoudi wrote: Hi Everyone, I will not be able to attend this week's meeting. Here is my status: 1. Make Active job resume attempt on the same suspend/resume thread This prevents

Weekly status

Hi Everyone, I will not be able to attend this week's meeting. Here is my status: 1. Make Active job resume attempt on the same suspend/resume thread This prevents Metadata locking issue explained in the commit message. 2. Set Default dataverse in MetadataProvider and prevents null values

Re: Status update for GSoC 2017 on GeoAsterixDB [ASTERIXDB-1371]

Nice!! On 7/3/17 7:56 PM, Riyafa Abdul Hameed wrote: Dear all, After familiarizing myself with AQL and SQLPP I have defined a new datatype which is 'geometry' and have implemented the parse_geojson() which would take as input a record (object) and return a 'geometry'. I have also implemented

Status update for GSoC 2017 on GeoAsterixDB [ASTERIXDB-1371]

Dear all, After familiarizing myself with AQL and SQLPP I have defined a new datatype which is 'geometry' and have implemented the parse_geojson() which would take as input a record (object) and return a 'geometry'. I have also implemented a printer for the 'geometry' datatype. Further I have

Re: What is the new path to check Hyracks jobs status in AsterixDB?

JSON: What's not to love? :-) On 4/7/17 5:27 PM, Jianfeng Jia wrote: That’s a good idea. I haven’t think about the browser plugin. Now it looks better! On Apr 7, 2017, at 4:34 PM, Till Westmann wrote: Since the endpoints return JSON, using a JSON formatter plugin for

Re: What is the new path to check Hyracks jobs status in AsterixDB?

That’s a good idea. I haven’t think about the browser plugin. Now it looks better! > On Apr 7, 2017, at 4:34 PM, Till Westmann wrote: > > Since the endpoints return JSON, using a JSON formatter plugin for the > browser seems easier. > Otherwise I think that we’ll need to

Re: What is the new path to check Hyracks jobs status in AsterixDB?

Since the endpoints return JSON, using a JSON formatter plugin for the browser seems easier. Otherwise I think that we’ll need to create a page around it (which is clearly feasible as well). On 7 Apr 2017, at 16:21, Mike Carey wrote: Could we use the same library that Xikui used for JSON

Re: What is the new path to check Hyracks jobs status in AsterixDB?

Could we use the same library that Xikui used for JSON (formatted) as a baby step? On 4/7/17 10:04 AM, Jianfeng Jia wrote: Got it. (do we have any plan to beautify the UI? :-) Thanks! On Apr 7, 2017, at 9:46 AM, Yingyi Bu wrote: Hi Jianfeng, The admin console has

Re: What is the new path to check Hyracks jobs status in AsterixDB?

Got it. (do we have any plan to beautify the UI? :-) Thanks! > On Apr 7, 2017, at 9:46 AM, Yingyi Bu wrote: > > Hi Jianfeng, > > The admin console has been removed but the REST APIs which return JSON > results are still there. > > Let's take the sample cluster as

Re: What is the new path to check Hyracks jobs status in AsterixDB?

Hi Jianfeng, The admin console has been removed but the REST APIs which return JSON results are still there. Let's take the sample cluster as an example. To check nodes: http://localhost:16001/rest/nodes/ http://localhost:16001/rest/nodes/red

What is the new path to check Hyracks jobs status in AsterixDB?

Dear Devs, We used to have a Hyracks adminconsole web page xxx:/adminconsole (or on 16001 port if not using managix) which can watch the details of the recent jobs. By click into each job we can know Activity Cluster Graph/Job Timeline etc. It’s very useful to have a overview of the

Re: Gerrit Status

Alright, I will take Gerrit down for upgrade pt.2 in a hour or so unless anyone objects. On Mon, Jan 30, 2017 at 11:00 AM, Ian Maxon wrote: > Hey guys, > Just as a heads up, I will probably take Gerrit down again sometime tonight > to retry the upgrade. I'll send an email a few

Status

Hi all, Unfortunately I won't be able to attend this meeting. And here's my status: - I was mainly working on the Tuple-Level compaction. - helped MIT folks on exporting and query the data. - Finally, there is an initial plan to incorporate Cloudberry in one of our project (It's targeted

Status

I will not be able to attend the Weekly meeting. So, I have attached my status here: [Paper] - Conducting a preliminary experiment on similarity search paper (preparing similar search queries and sending them to a small dataset) [Individual] - Addressed Ian's comments on the full-text

Status

I will be unable to join the meeting tomorrow, so I'm sending my status. This week I: Got the three-node BAD nuclear cluster running Added test cases and addressed Yingyi's comments and Preston's Jira issue for nonPures. Refactored BAD as an extension, and am now trying to get the testing

Re: Status

It's been a busy week for me. I just worked a little bit more on AqlMetadataProvider refactoring. -Murtadha > On Jul 15, 2016, at 2:10 PM, Chris Hillery wrote: > > - Discussions inside Couchbase regarding perf testing (meeting with perf > team member later today) > -

Status

- Discussions inside Couchbase regarding perf testing (meeting with perf team member later today) - Worked with Mike B a bit on improvements to current functional testing Ceej aka Chris Hillery